Deploying a Centralized GWLB Security VPC

This section describes the steps to deploy a CloudGuard Network Security VPC with the Gateway Load Balancer.

The Security VPC CloudFormation Template deploys a CloudGuard Network Auto Scaling Group, a Gateway Load Balancer, and an optional Security Management ServerClosed Dedicated Check Point server that runs Check Point software to manage the objects and policies in a Check Point environment within a single management Domain. Synonym: Single-Domain Security Management Server..

Step 1: Prepare your AWS Account

To prepare your AWS account:

  1. If you do not have an AWSClosed Amazon® Web Services. Public cloud platform that offers global compute, storage, database, application and other cloud services. account, create one.

  2. Use the region selector in the navigation bar to select the AWS region where you want to deploy Check Point CloudGuard Network Auto Scaling on AWS.

  3. Create a key pair in your preferred region.

  4. Request a service limit increase for the AWS resources you plan to use, if necessary.

    By default, this Deployment Guide uses:

Minimum Permissions for Deployment

Configure the relevant IAM policy with the minimum permissions for a successful deployment, as shown below.

In the AWS VPCClosed AWS Virtual Private Cloud. A private cloud that exists in the public cloud of Amazon. It is isolated from other Virtual Networks in the AWS cloud. Console, navigate to the IAM service, select the relevant IAM policy, copy the required permissions from this guide (see below) and paste them into the policy:

Step 2: Subscribe to Check Point CloudGuard Network Security

To deploy a CloudGuard Network Security for Gateway Load Balancer, do these steps:

  1. Log in to the AWS Marketplace.

  2. Search for "CloudGuard Network Security".

  3. Select one of these licensing options for the CloudGuard Network Security for Gateway Load Balancer:

    Or one of these licensing options for a Check Point CloudGuard Security Management Server:

  4. Select Continue to subscribe.

  5. Select Accept Terms to confirm that you accept the AWS Marketplace license agreement.

Step 3: Deploy the Check Point Security Management Server

Use one of these options to deploy the Check Point Security Management Server:

Step 4: Deploy the Centralized Security VPC

This step details a procedure for deploying the Check Point CloudGuard Network Security Gateway Auto Scaling Group configured for AWS Gateway Load Balancer (GWLB) in a Centralized Security VPC.

CloudFormation (CFT) Template

Description

Auto-Scaling group for Gateway Load Balancer with a new VPC

Creates a new VPC and deploys a Gateway Load Balancer, Check Point CloudGuard Security Gateway Auto Scaling Group, and an optional Security Management Server to the new VPC.

Auto-Scaling group for Gateway Load Balancer into existing VPC

Deploys a Gateway Load Balancer, Check Point CloudGuard Security Gateway Auto Scaling Group, and an optional Security Management Server to the existing VPC.

Parameters for Deploying an Auto Scaling Group with a GWLB to a New VPC

Network Configuration:

Parameter Name

Default Value

Description

Availability Zones

Requires input

Select, at minimum, two Availability Zones (AZs) for the VPC subnets.

Number of AZs

2

Specify the number of AZs to use in the VPC. This must align with the number of AZs selected for the Availability Zones parameter.

VPC CIDR

10.0.0.0/16

Configure the CIDR block for the VPC.

Auto Scaling Group Public Subnet 1

10.0.10.0/24

Specify a CIDR block for the public subnet. Use this format: x.x.x.x/16-28.

Auto Scaling Group Public Subnet 2

10.0.20.0/24

Specify a CIDR block for the public subnet. Use this format: x.x.x.x/16-28.

Auto Scaling Group Public Subnet 3

10.0.30.0/24

Specify a CIDR block for the public subnet. Use this format: x.x.x.x/16-28.

Auto Scaling Group Public Subnet 4

10.0.40.0/24

Specify a CIDR block for the public subnet. Use this format x.x.x.x/16-28.

General Settings:

Parameter Name

Default Value

Description

Key name

Requires input

Specify an EC2 key pair to enable SSH access to the instances created by this stack.

Enable Environment Volume Encryption

True

Enable or disable instance volume encryption with the default AWS Key Management Service (KMS) key.

Root volume size

100

Set the root volume size in GB.

Volume Type

gp3

Select the General Purpose SSD volume type.

Termination Protection

False

Enable or disable protection against accidental instance termination.

Enable AWS Instance Connect

False

Enable or disable establishing SSH connections through the AWS web console.

Allow Upload & Download

True

Enable or disable automatic download of Software BladeClosed Specific security solution (module): (1) On a Security Gateway, each Software Blade inspects specific characteristics of the traffic (2) On a Management Server, each Software Blade enables different management capabilities. Contracts and data sharing with Check Point for a better product experience.

Management Server

gwlb-management server

Provide a name for the Security Management Server in the automatic provisioning configuration.

Configuration template

gwlb-ASG-configuration

Specify a name for a Security Gateway configuration template in the automatic provisioning configuration.

Email Address

Optional

(Optional) Provide an email address to receive AWS notifications about scaling events.

Admin Shell

/etc/cli.sh

Select the admin shell to enable advanced command line configuration for Security Gateways and Security Management Server.

Gateway Load Balancer Configuration:

Parameter Name

Default Value

Description

Gateway Load Balancer Name

gwlb1

Provide a unique name for the Gateway Load Balancer. The name can have a maximum of 32 alphanumeric characters and hyphens.

Important - The name cannot start or end with a hyphen.

Target Group Name

tg1

Specify a unique name for the target group. The name can have a maximum of 32 alphanumeric characters and hyphens.

Important - The name cannot start or end with a hyphen.

Connection Acceptance Required

False

Specify if requests from Service Consumers to create endpoints on your service require acceptance. The default value is set to False ("acceptance" is not required).

Enable Cross Zone Load Balancing

True

Enable or disable Cross-AZ Load Balancing.

Important - If you enable this parameter, this can increase Cross-AZ charges.

Check Point CloudGuard Network Security Gateways Auto Scaling Group Configuration:

Parameter Name

Default Value

Description

Gateways Instance Name

Check Point Gateway

Provide a name tag for the Security Gateway instances.

Gateways Instance Type

c5.xlarge

Select the EC2 instance type for Security Gateways.

Minimum Group Size

2

Set the minimum number of Security Gateways in the Auto Scaling Group.

Maximum Group Size

10

Set the maximum number of Security Gateways in the Auto Scaling Group.

Gateways Version & License

R81.20-BYOL

Select the version and license type for Security Gateways.

Gateways Password Hash

Optional

(Optional) Provide the admin user's password hash (use the command "openssl passwd -6 PASSWORD" to get the password's hash).

Gateway Maintenance Password hash

Optional

(Optional) Check Point recommends to set the admin user's password and maintenance-mode password for recovery purposes (use command grub2-mkpasswd-pbkdf2 to get the password's hash). For R81.10 and lower versions, the admin user's password is also used as a maintenance-mode password.

Gateways SIC Key

Requires input

Enter a SICClosed Secure Internal Communication. The Check Point proprietary mechanism with which Check Point computers that run Check Point software authenticate each other over SSL, for secure communication. This authentication is based on the certificates issued by the ICA on a Check Point Management Server. key to create trusted connections between Check Point components. Provide a random string that has a minimum of 8 alphanumeric characters.

Gateways addresses

Private

Select if provisioned Security Gateways use private or public addresses.

Allocate Public IPs

False

Enable or disable allocation of public IP addresses for Security Gateways.

Add support for IPv6 traffic inspection

False

Enable or disable support for IPv6 traffic inspection.

CloudWatch Metrics

False

Enable or disable reporting of Check Point-specific CloudWatch metrics.

Gateways bootstrap script

Optional

Provide an optional script with semicolon-separated commands to run on initial boot.


Note - For more information on how to use Check Point metrics to trigger AWS Auto-Scaling events, refer to sk162592.

Check Point CloudGuard Network Security Configuration:

Parameter Name

Default Value

Description

Deploy Management Server

True

Specify False to use an existing Security Management Server, or True to deploy a new Security Management Server. If you select False, ignore the other parameters in this section.

Management Instance Type

m5.xlarge

Select the EC2 instance type for the Security Management Server.

Management Version & License

R81.20-BYOL

Select the version and license type for the Security Management Server.

Management Password Hash

Optional

(Optional) Provide the admin user's password hash (use the command "openssl passwd -6 PASSWORD" to get the password's hash).

Management Maintenance Password hash

Optional

(Optional) Check Point recommends to set the admin user's password and maintenance-mode password for recovery purposes (use the command grub2-mkpasswd-pbkdf2 to get the password's hash). For R81.10 and lower versions, the Admin user's password is also used as a maintenance-mode password.

Security Policy

Standard

Specify the name of the Security PolicyClosed Collection of rules that control network traffic and enforce organization guidelines for data protection and access to resources with packet inspection. package to install on the Security Gateways in the Security Auto Scaling Group.

Administrator Addresses

Requires input

Specify the network allowed to connect to the Security Management Server through web, SSH, and graphical clients.

Manage Gateways

Locally managed

Select between local management or management over the Internet based on Security Gateway accessibility. If, at minimum, one of the Security Gateways that you want to manage is not directly accessed through its private IP address, select Over the internet.

Gateways Addresses

Requires input

Specify the network allowed for communication of Security Gateways with the Security Management Server.


Note - Interfaces of Auto Scaling Group instances are automatically configured with Internal Topology. This is not defined in SmartConsoleClosed Check Point GUI application used to manage a Check Point environment - configure Security Policies, configure devices, monitor products and events, install updates, and so on..

Important - The External Load Balancer sends health probes to TCP port 8117 to determine the health of the CloudGuard Network Security Gateways, so port 8117 must be open on the Security Gateways.

Step 5: Configure the Check Point Security Management Server

Install and Configure Cloud Management Extension

Follow these steps to set up the Cloud Management Extension (CME), which manages CloudGuard Network's integration with AWS GWLB and seamlessly operates the GWLB solution.

  1. Install CME on the Security Management Server.

    Install the latest CME tool on your Security Management Server. See sk157492.

    For more details, see the "Structure and Configuration" section in the Cloud Management Extension Administration Guide.

  2. Configure the Security Management Server using the "autoprov_cfg" tool.

    Important - If you have existing configurations for other Check PointCloudGuard Network solutions, do not initialize your configuration. Instead, add the Controller or Template for the GWLB solution with the applicable configuration

    The autoprov_cfg tool configures the Security Management Server with all the settings needed for GWLB.

    Follow these steps:

    1. Connect to the CLI on the Security Management Server.

    2. Log in to the Expert mode.

    3. Run each of the commands below.

    Commands and their options:

    1. To initialize the autoprov_cfg configuration with IAM credentials, run:

      autoprov_cfg init AWS -mn "<MANAGEMENT-NAME>" -tn "<TEMPLATE-NAME>" -otp "<SIC-KEY>" -ver R81.20 -po "<POLICY-NAME>" -cn "<CONTROLLER-NAME>" -r "<REGIONS>" -iam

      Options:

      • -mn - Security Management Server name

      • -tn - Template name

      • -otp - One-time SIC password

      • -ver - Security Gateway version

      • -po - Policy package name

      • -cn - Controller name

      • -r - Comma-separated list of regions

      • -iam - Use IAM to connect to AWS

    2. To configure auto provisioning controller for GWLB Scan Subnets mode, run:

      autoprov_cfg set controller AWS -cn "<CONTROLLER-NAME>" –ss

      Options:

      • -ss - Enables GWLB Scan Subnets mode

    3. To display autoprov_cfg configuration and make sure all the configurations are correct, run:

      autoprov_cfg show all

    4. To test the configuration and make sure it is correct, run:

      service cme test

      Important - Make sure there are no errors in the test results.

Step 6: Post Deployment - Manually Deploying the Gateway Load Balancer Endpoint

Use the AWS Management Console or the latest version of the AWS CLI tool to manually deploy a Gateway Load Balancer Endpoint to the service consumer's VPC.

Follow these steps:

  1. Create a dedicated subnet for the Gateway Load Balancer Endpoint (GWLBe) in the Servers VPC and set the default route through the AWS Internet Gateway (IGW).

  2. Create the GWLBe in the newly created subnet with the command below.

AWS CLI Command:

aws ec2 create-vpc-endpoint --vpc-endpoint-type GatewayLoadBalancer --service-name com.amazonaws.vpce.us-east-2.vpce-svc-12345678901234567 --vpc-id consumer-vpc-id --subnet-ids consumer-subnet-id


Note - Find the Service Name in the CloudFormation outputs ‘GWLBServiceName' parameter.

For more information about Gateway Load Balancer Endpoints, see the AWS VPC Gateway Load Balancer documentation.

Step 7: Post Deployment - Tag Subnets for Inspection

Note - This section applies only to Solution 1 without a Transit Gateway. Solution 2 with a Transit Gateway does not support spoke subnet tagging.

To enforce GWLB inspection, manually tag subnets. For that:

  1. Go to VPC > Subnets.

  2. Choose Servers subnets from the Server VPC.

  3. Specify tags:

    Tag key

    Tag value

    Tag value example

    x-chkp-gwlb-inbound

    <CIDR_a,CIDR_b,CIDR_c,...>

    1.1.0.0/16, 1.2.3.4/32

    x-chkp-gwlb-outbound

    <CIDR_a,CIDR_b,CIDR_c,...>

    0.0.0.0/0


Notes:

  • Untagged subnets are not inspected.

  • Tagging one subnet in a shared route table affects all subnets using that table.

When a subnet is GWLB-tagged, CME automatically:

  1. Configures ingress routing through the GWLBe.

  2. Creates Check Point policy rules in the Security Policy rule baseClosed All rules configured in a given Security Policy. Synonym: Rulebase. according to tag value to allow traffic to and from the tagged subnet.

    The GWLB-value on a subnet represents a list of CIDRs to allow traffic:

    • to – for outbound tag

    • from - for inbound tag

These policy rules are added for a tagged subnet in the Security Management Server ruleClosed Set of traffic parameters and other conditions in a Rule Base (Security Policy) that cause specified actions to be taken for a communication session. base:

Inbound:

Source

Destination

Action

gwlb-inbound-tag-value CIDRs

subnetCIDR

Accept

Outbound:

Source

Destination

Action

subnetCIDR

gwlb-outbound-tag-value CIDRs

Accept

When a subnet is untagged, CME:

1. Disables ingress routing for that subnet.

2. Removes related security rules from the rule base.

Note - Do not manually change these rules. CME restores any changes to align with the subnet tags.

Termination

To stop the environment:

  1. Untag all subnets in the Servers VPC(s) (remove x-chkp-gwlb-X tags).

  2. Disable Scan Subnets flag on your CME controller with this command:

    autoprov_cfg delete controller AWS -cn "<CONTROLLER-NAME>" –ss

  3. Remove all related resources from your AWS environment.

  4. Remove the Security VPC CFT Stack from your AWS account.