Data Center Deployment Configuration for Google Cloud Platform (Essentials Subscription) 

The documentation below describes the new version of the Alert Logic console, which was recently updated. This version will become the default in early 2020. For more information about the new navigation, see Managed Detection and Response Navigation Menu Updates.

Alert Logic allows you to use a Data Center deployment to monitor your assets on the Google Cloud Platform. Before your deployment can monitor your assets, you must install an Alert Logic appliance and agents to your Google Cloud environment.

Before you begin

Before you create your first Data Center deployment for Google Cloud Platform, you must:

  • Install the gcloud command line tool for use with your GCP account. For more information about the gcloud CLI, see this Google Cloud Platform document.
  • Configure your system to launch and use Jinja templates.

Overview

The basic workflow to create a Data Center deployment to monitor your assets on the Google Cloud Platform is as follows:

  1. Create a Data Center deployment in the Alert Logic console.
  2. Create one or more appliance virtual machines (VM) in the Google Cloud Platform projects that are in the Data Center deployment scope of protection.
  3. Claim the appliances.
  4. Create one or more appliance virtual machines in the Google Cloud Platform projects that are in the deployment scope of protection.
  5. Claim the appliance(s).
  6. Install the Alert Logic agent on the hosts in the deployment scope of protection.

Create a Data Center deployment for your Google Cloud Platform assets

You must create the Data Center deployment prior to creating and claiming the appliance VMs. The appliance claim process requires information from your Alert Logic account.

You can access the Deployments page from the Configure menu item in the Alert Logic console. To add a Data Center deployment, click the add icon (), and then click Data Center.

Name your deployment

In the Deployment Name field, type a descriptive name for the deployment you want to create, and then click SAVE AND CONTINUE.

Add assets

For Data Center deployments, Alert Logic suggests you add your assets using discovery scans. While you can add your assets manually, weekly discovery scans ensure your Data Center deployments are configured with the right ranges.

You can manually add your assets by network, subnet, domain name, or IP address to be scanned. Add the requested information for every virtual network and subnet you want to monitor.

To add a network:

  1. In the Networks tab, click the add icon (), and then select Network.
  2. Type a name for the network, add the Private CIDR(s) and the Public CIDR(s).
  3. Select Do not use agents for IDS traffic. My network automatically forwards traffic to my appliances through a port mirroring feature. if your network equipment is configured to SPAN or another port mirroring feature.
  4. A SPAN configured network forwards your Network IDS traffic to Alert Logic appliances, which allows Alert Logic to analyze that traffic.

  5. Click SAVE.

To add a subnet:

  1. In the Networks tab, click the add icon (), and then select Subnet.
  2. Name the subnet, select the network, add the Private CIDR, and then click SAVE.

To add a domain name:

  1. In the DNS Names and Public IPs tab, click the add icon (), and then select DNS Name.
  2. Add the domain name, and then click SAVE.

To add an IP address:

  1. In the DNS Names and Public IPs tab, click the add icon (), and then select Public IP.
  2. Name the IP address, add the CIDR, and then click SAVE.

When you are finished, click NEXT.

Scope of protection

Alert Logic discovers and organizes deployments into a visual topology where you can select the desired levels of protection for your assets.

You can define the scope of your protection per network or per region. Each network appears within its protected region. Click a region or individual network to set the service level or leave it unprotected, and then click SAVE. You must choose one of the following levels of coverage:

  • Unprotected
  • Alert Logic Essentials coverage

Choices available for scope of protection correspond directly with your entitlement. Although a Professional subscription includes all the features of Essentials, a Professional customer cannot set the protection scope to Essentials unless the account has a separate billing line for an Essentials subscription.

You can change the protection level later as needed.

Exclusions

You also have the option to exclude assets or tags from external scanning, internal scanning, and Network IDS.

External scanning

To exclude assets from external scanning:

  1. Click EXCLUSIONS.
  2. Select the External Scanning tab to view assets available to exclude.
  3. Click EXCLUDE for the asset you want to exclude.
    You can remove an asset from the exclusion list at any time to include the asset in scanning. To remove an asset from the exclusion list, click CANCEL.
  4. After you apply your exclusions, close the Exclusions window.
  5. On the Scope of Protection page, click SAVE.

Internal scanning

To exclude assets or tags for internal scanning:

  1. Select the Internal Scanning tab, and then click ASSETS or TAGS to search for assets or tags available to exclude.
  2. Click EXCLUDE for the asset or tag you want to exclude.
    You can remove an asset from the exclusion list at any time to include the asset in scanning. To remove an asset from the exclusion list, click CANCEL.
  3. After you apply your exclusions, close the Exclusions window.
  4. On the Scope of Protection page, click SAVE.

Scheduling

Alert Logic automatically performs certain scans. You can schedule how often and when you want Alert Logic to scan for new assets from the Discovery Scans tab and to scan for vulnerabilities from the Internal Scans and External Scans tabs.

Discovery scans

To schedule how often you want Alert Logic to scan for new assets, choose one of the following options:

  • Scan as often as necessary—Select this option if you want Alert Logic to scan for new assets twice a day or when significant changes are detected.
  • Scan once a day
  • Scan twice a day
  • Scan three times a day

To schedule when you want Alert Logic to scan for new assets, choose one of the following options:

  • Scan whenever necessary—Select this option if you do not want to limit Alert Logic scans to particular days or times.
  • Scan only during certain times

Click SAVE, and then click NEXT.

Internal scans and External scans

To schedule how often you want Alert Logic to scan for vulnerabilities, choose one of the following options:

  • Scan as often as necessary—Select this option if you want Alert Logic to scan known assets for vulnerabilities once a day or, if significant changes to an asset are detected, twice a day.
  • Scan once a day
  • Scan once a week
  • Scan once a month

To schedule when you want Alert Logic to scan for vulnerabilities, choose one of the following options:

  • Scan whenever necessary—Select this option if you do not want to limit Alert Logic scans to particular days or times.
  • Scan only during certain times on certain days
  • Scan only on a certain day (AWS and Azure deployments only)

Click SAVE, and then click NEXT.

Options

Configure Cross-Network Protection

You have the option to set up Cross-Network Protection to create connections across networks, in the same or different deployment, but within the same account. Cross-Network Protection allows other networks to use resources from a protecting network with an assigned network appliance. The common places for Cross-Network Protection use are Amazon Web Services (AWS) VPC Peering, AWS Transit Gateway, and Microsoft Azure VNet Peering.

A protecting network hosts the appliance. The network protected by the protecting network is the protected network. For more information on Cross-Network Protection, see Cross-Network Protection.

To configure Cross-Network Protection:

  1. On the side navigation, click Options under Protection.
  2. On the Cross-Network Protection tab, click the network or region you want to protect in the topology diagram, or in the Search Assets field, search for the network or region you want to protect.
  3. Click the search field to search or type the name of a protecting network, and then select one.
  4. Click SAVE.

The protecting network and protected network are now visible in the topology diagram with distinguishing icons. The Cross-Network Protection Breakdown, on the top left of the topology graph, provides an overview of your Cross-Network Protection connections.

View protected networks

To view protected networks:

  1. Click the protecting network icon () to see the number of protected networks currently connected.
  2. Click the details icon () to see a slideout panel that contains protected network names.

View protecting networks

To view protecting networks, click the protected network icon ().

Configuration Topology

This topology diagram provides an overview of your scope of protection. You can see which assets are unprotected, or being scanned at the Essentials, Professional, or Enterprise levels.

The protection breakdown displays how many assets are unprotected, excluded, and protected, along with the number of protected assets in each level.

You can search for specific assets. The protection breakdown updates as it finds specific assets.

Installation Instructions

Do not follow the appliance or agent installation instructions on this screen. However, you do need the Unique Registration Key, located on the Appliances tab, when you claim your appliance and register your agents.

Copy, deploy, and claim the appliance VM

To perform these tasks, you must use the gcloud command-line tool to log into your GCP account.

You must also be prepared to configure the appliance firewall rules.

Copy the appliance VM image to your GCP project

At the command line type the following commands:

gcloud config set project <project name>

gcloud compute images create al-threat-appliance --source-uri=https://storage.googleapis.com/threat/al-threat-appliance.tar.gz

Deploy the appliance

Alert Logic provides a Jinja template for GCP appliance deployment. You can download the template from this location.

The Jinja template uses the parameters described below:

  • region: The region to deploy this appliance (us-central1)
  • zone: The zone for the appliance (us-central1-a)
  • network: The network name for the appliance
  • sub_network: The name of the subnet inside the network
  • firewall_tag: The target tag to be assigned for firewall rules
  • claim_cidr: The source IP CIDR that is allowed to perform web claim on port 80, i.e. 0.0.0.0/0 or specific subnet range
  • network_cidr: The network CIDR for the appliance (not subnet / sub network CIDR)
  • machine_image: The image name for the appliance
  • machine_type: The minimum recommendation is n1-standard-4

Use the gcloud command-line tool to deploy the appliance with the Jinja template. The following example CLI command illustrates usage of the template and its parameters:

gcloud deployment-manager deployments create deployment-name --template ./al_tm_deploy.jinja --properties region:us-central1,zone:us-central1-a,network:default,sub_network:default,firewall_tag:al-tmc,claim_cidr:0.0.0.0/0,network_cidr:10.5.0.0/16,machine_image:al-threat-appliance,machine_type:n1-standard-4

Claim the appliance

You must claim the appliance VM after it spins up. Appliance claim registers the appliance with the Alert Logic backend and links the appliance with your Alert Logic account. To claim your appliance, you will need the Unique Registration Key for every network you configured in the Data Center deployment. You can find the keys on the Installation Instructions page of your Data Center deployment in the Alert Logic console.

To claim your appliance:

  1. Open a web browser and enter the public IP address for the appliance as the URL.
  2. When prompted, provide the Unique Registration Key associated with the network where the appliance resides.

As part of the provisioning process the appliance updates itself to the latest version of all its components and security content. This process can take 20-30 minutes. When the claiming process is complete, the appliance appears on the Health page in the Alert Logic console and is ready for use.

Verify the health of your deployment

After you create your deployment, access the Health console in the Alert Logic console to determine the health of your networks, appliances, and agents, and then make any necessary changes.