Amazon Web Services (AWS) Deployment Configuration—Manual Mode (Professional Subscription)

Alert Logic allows for an optional, manual deployment mode for AWS deployments. Alert Logic recommends Manual Mode for AWS deployment creation only if you want to deploy and maintain scanning instances in your deployments.

Deployment creation requires that you be logged into your Alert Logic account and the AWS account you want this deployment to monitor and protect.

If you manage more than one Alert Logic account, be sure you are logged into the correct account.

To start creating your AWS deployment:

  1. In the Alert Logic console, click the Configure menu item, and then click Deployments.
  2. Click the add icon (), and then select Amazon Web Services (AWS).
  3. Type a name for your deployment, and then click SAVE AND CONTINUE.
  4. Select Manual Mode, and then click SAVE & CONTINUE.

IAM policy and role creation

To protect your AWS deployment, you must set up an AWS IAM policy and role to allow Alert Logic access to your AWS account. Alert Logic provides an AWS CloudFormation template to automate creation of the correct policy and role for the deployment. You can also choose to manually set up the IAM policy and role.

Cross-account roles allow Alert Logic to access your AWS account. AWS role creation requires that you provide an AWS policy, a document that specifies the permissions assigned to the AWS role you create for Alert Logic to access to your AWS account.

The IAM policy document used for a Manual Deployment provides minimal permissions for third-party access and requires that you manually perform the following additional configuration steps in the AWS console:

  • Set up a CloudTrail log source
  • Create or configure S3 bucket
  • Create or configure an existing SNS topic
  • Create or configure an existing SQS queue

You can choose to create an IAM policy with minimal permissions. For more information, see Configure AWS Minimal Permission Deployment.

IAM policy and role setup using AWS CloudFormation

Alert Logic recommends you use the Alert Logic CloudFormation template for quick, convenient IAM policy and role creation. The CloudFormation template creates the appropriate IAM role that allows your deployment access to your AWS assets.

Click CLOUDFORMATION SETUP, and then follow the instructions in the Alert Logic console and the AWS console.

IAM policy and role setup using manual IAM setup

Select manual IAM set up if your AWS account permissions allow you to create an IAM policy, but does not have the permissions to run CloudFormation.

Click MANUAL IAM SETUP, and then follow the instructions on the screen.

Enter your Role ARN

In the Alert Logic console, enter the ARN you copied from the AWS console after you created the IAM role.

If you want to configure cross-account access for centralized CloudTrail log collection, click the I want to configure centralized CloudTrail log collection for this deployment slide bar, and enter a second Role ARN you created for this purpose. For more information about centralized log collection, see Should you centralize CloudTrail log collection?.

Asset Discovery

Allow Alert Logic a moment to discover your assets. When discovery is complete, click CONTINUE. Alert Logic displays the assets discovered in your account in topology diagrams. To learn more about topology, click Topology.

Add external assets

You can add external assets by domain name or IP address. Alert Logic will scan these external assets that you define.

External assets are also used for non-PCI external scans.

To add external assets:

  1. Click the External Assets tab, click the add icon (), and then choose DNS Name or External IP.
    • If you chose DNS Name, enter your fully qualified domain name in the field.
    • If you chose External IP, name your external IP address, and then enter the IP address in the field.
  2. Click SAVE.

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 region or network. 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 SCOPE. You must choose one of the following levels of coverage:

  • Unprotected
  • Alert Logic Essentials coverage
  • Alert Logic Professional coverage

The 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 Essentials subscription.

You can change the protection level later as needed.

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.

Only manual mode deployments have the Cross-Network Protection option.

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 ().

Network IDS Exclusions

Network IDS monitors network traffic and triggers incidents when it detects suspicious activity or threats on your networks. You can exclude assets from Network IDS.

To exclude assets from Network IDS:

  1. In the left panel, click Network IDS Exclusions.
  2. Click the drop-down menu to select a network or leave All networks selected.
  3. In the Protocol field, click the drop-down menu to select a protocol. Select TCP, UDP, or ICMP, or select * to select all IP protocols.
  4. In the CIDR field, enter a range of network addresses in CIDR format that you want to exclude.

    Enter 10.0.0.0/24 to exclude IP addresses in the range 10.0.0.0-10.0.0.255.

  5. Click the drop-down menu to select the port. You can enter a single port, a port range, or * to select all ports.

    Enter 443 for a single port. Enter 1:1024 for a port range.

  6. In the Justification/Note field, enter the reason for excluding the assets from Network IDS.
  7. Click EXCLUDE AND ADD ANOTHER. Repeat the steps to add more CIDRs.
    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 REMOVE.
  8. After you apply all the necessary exclusions, click SAVE EXCLUSIONS.

Agent-Based Scanning

You have the option to enable agent-based scanning. Agent-based scanning improves the efficiency, accuracy, and usability of Alert Logic vulnerability scanning features. Agent-based scanning provides the vulnerability assessment coverage of authenticated network scanning without the need to manage credentials and with a reduction in network traffic and impact. To learn more about agent-based scanning, see Agent-Based Scanning.

Vulnerability Scanning

The next step is to configure vulnerability scans to protect your deployment.

Scan Schedules

When you create a new deployment, Alert Logic automatically creates default scan schedules to perform external and internal vulnerability scans on all non-excluded assets and ports in your AWS security groups. If agent-based scanning is enabled, the default agent-based scan schedule performs scans for vulnerabilities and missing patches on all non-excluded hosts with an Alert Logic agent installed. You can schedule when you want to perform specific scans for all or selected assets and ports from the Agent-Based Scans, Internal Network Scans, and External Network Scans tabs. For more information, see Manage Vulnerability Scan Schedules.

Port selection does not apply to agent-based scan schedules.

To initiate vulnerability scanning, review the schedules, make any changes, and then activate the schedules you want to use. Click NEXT.

Scan Exclusions

You can exclude assets from each type of vulnerability scan. You can exclude ports from internal and external network scans. You can also use AWS tags to exclude assets, including subnets, from internal network scans and agent-based scans.

Agent-based scans

To exclude assets or AWS tags from agent-based scans:

  1. On the Scan Exclusions page, click the Agent-Based Scans tab.
  2. To exclude assets, click ASSETS to search for available assets to exclude, and then 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.
  3. To exclude assets by using AWS tags, click TAGS to search for available tags to exclude, and then click EXCLUDE for the tag you want to exclude.
    4. You can remove a tag from the exclusion list at any time to include the tag in scanning. To remove a tag from the exclusion list, click CANCEL.
  4. After you apply your exclusions, click SAVE EXCLUSIONS.
If you exclude assets or tags that are selected in an active scan schedule in the Scope tab, the items remain selected but are not included in future scans.

Internal network scans

To exclude assets, ports, or AWS tags from internal network scans:

  1. On the Scan Exclusions page, click the Internal Network Scans tab.
  2. To exclude assets, click ASSETS to search for available assets to exclude, and then 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.
  3. To exclude ports, click PORTS, and then do the following:
    1. Search for the host, subnet, or network that has the ports you want to exclude from internal scanning.
    2. In the Protocol field, select the port protocol UDP, TCP, ICMP, or select * to select all IP protocols.
    3. Enter one or more ports that you want to exclude. Use a dash or colon to indicate a range (for example, 1-10001). Separate multiple ports or port ranges with a comma (for example, 11234, 11311, 12000-12010).
    4. Click EXCLUDE AND ADD ANOTHER.
    4. You can remove ports from the exclusion list at any time to include the ports in scanning. To remove ports from the exclusion list, click REMOVE.
  4. To exclude assets by using AWS tags, click TAGS to search for available tags to exclude, and then click EXCLUDE for the tag you want to exclude.
    5. You can remove a tag from the exclusion list at any time to include the tag in scanning. To remove a tag from the exclusion list, click CANCEL.
  5. After you apply your exclusions, click SAVE EXCLUSIONS.
If you exclude assets, tags, or ports that are selected in an active scan schedule in the Scope or Ports tab, the items remain selected but are not included in future scans.

External network scans

To exclude assets or ports from external network scans:

  1. On the Scan Exclusions page, click the External Network Scans tab.
  2. To exclude assets, click ASSETS to search for available assets to exclude, and then 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.
  3. To exclude ports, click PORTS, and then do the following:
    1. Search for the host, subnet, or network that has the ports you want to exclude from external scanning.
    2. In the Protocol field, select the port protocol UDP, TCP, ICMP, or select * to select all IP protocols.
    3. Enter one or more ports that you want to exclude. Use a dash or colon to indicate a range (for example, 1-10001). Separate multiple ports or port ranges with a comma (for example, 11234, 11311, 12000-12010).
    4. Click EXCLUDE AND ADD ANOTHER.
    4. You can remove ports from the exclusion list at any time to include the ports in scanning. To remove ports from the exclusion list, click REMOVE.
  4. After you apply your exclusions, click SAVE EXCLUSIONS.
If you exclude assets or ports that are selected in the Scope or Ports tab in an active scan schedule, the assets or ports remain selected but are not included in future scans.

Scan Credentials

You can add credentials to your regions or assets to use with internal network scans. You can add multiple credential types, but only one credential of each type. If you provide credentials, Alert Logic performs comprehensive authenticated vulnerability checks for missing patches and misconfigurations using package information and other local sources of data. For hosts on which Alert Logic performs agent-based scanning, you do not need to provide credentials. If you do not provide credentials or enable agent-based scanning, scans on your assets occur using only methods available to unauthenticated users.

To add your credentials:

  1. In the left panel, click Scan Credentials.
  2. In the list of assets, click the asset for which you want to add credentials, and then click the Credentials tab in the panel that opens.

    To filter the list, you can search for characters in your asset names.

  3. Click ADD CREDENTIAL, and then enter the required fields.
  4. Click SAVE.

The credential icon () appears in the list next to assets with credentials provided.

To delete a credential, click the asset that has credentials, click the Credentials tab in the panel that opens, and then click the X next to the name.

Scan Performance

For internal and external vulnerability scans, the maximum number of IPs scanned concurrently is ten by default.

You can choose fewer concurrent scans to reduce scan traffic. A lower number results in slower scans and a longer scan duration. For faster scans and a shorter scan duration, choose a higher number of concurrent scans. The number you choose is a maximum limit. The actual number of concurrent scans does not exceed the selected amount and depends on factors such as appliance resource availability and network bandwidth during the scan window.

To adjust scan performance:

  1. In the left panel, click Scan Performance.
  2. In the list of assets, click the region or network for which you want to adjust scan performance, and then click the Scan Settings tab in the panel that opens.
  3. In the Vulnerability area, enter a number from 1 (slower scans) through 20 (faster scans). The default is 10 maximum concurrent IPs scanned.
  4. Click SAVE to save your selections.

File Integrity Monitoring (FIM)

FIM allows you to monitor changes to files and directories of assets in your deployments. You can configure monitoring or exclusions for specific file paths or entire directories in your Windows and Linux systems.

FIM is composed of two subsections: Monitoring and Exclusions. On the Monitoring page, you can set up files and directories for monitoring from the default file types listed on the page. In the Exclusions page, you can exclude files and directories from monitoring, which will override a previously configured file monitoring setup. For more information, see File Integrity Monitoring .

After creating FIM or exclusion setups, click NEXT.

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.

Manual AWS configuration

Manual Mode deployments require you to log into the AWS console and configure the following AWS services:

  • Set up a CloudTrail log source.
    • Create a CloudTrail and SNS topic, or
    • Use an existing CloudTrail and SNS topic
  • Configure Amazon S3 bucket policy
  • Deploy an IDS appliance
  • Deploy a scanning appliance

Set up AWS CloudTrail

The process to set up AWS CloudTrail depends on whether you need to create a SNS topic, or edit an existing SNS topic for CloudTrail.

Create a CloudTrail and SNS topic

If AWS CloudTrail is not yet enabled for your account, you must create a new trail, with an S3 bucket and SNS topic, and configure it for use with Alert Logic.

To set up CloudTrail with a new SNS topic:

  1. Log into the AWS account you want to protect.
  2. Click CloudTrail >Trails.
  3. Click Create trail.
  4. In Trail name, type a name for your trail.
  5. For Apply trail to all regions, click Yes.
  6. For Create a new S3 bucket, select Yes.
  7. In S3 bucket, type the name of the S3 bucket in which to store your CloudTrail logs in your account.
  8. Click Advanced.
  9. For Send SNS notification for every log file delivery, select Yes.
  10. For Create a new SNS topic, select Yes.
  11. Click Save.
  12. Click Create.

Use an existing CloudTrail and SNS topic

If you already enabled AWS CloudTrail for your account, Alert Logic uses the existing trail with the "multi-region" flag enabled. If you set up more than one trail with this flag enabled, Alert Logic selects the trail that appears first in alphabetical order. The existing trail you use must be configured with SNS delivery enabled, as described in the steps below.

To configure an existing SNS Topic:

  1. From the AWS CloudTrail console, click Trails and then select your existing trail.
  2. Ensure that Apply trail to all regions is set to Yes; if not, click the pencil icon (), and then change the value to Yes.
  3. In the S3 section, ensure that Publish to SNS is set to Yes, and that a valid SNS topic is set. If your current configuration is not set up to publish to SNS, then click the pencil icon () to change the settings and create a new SNS topic to receive notifications. Note the ARN of the SNS topic; you will need it when defining the IAM policy.

Configure Amazon S3 bucket policies for log collection

For Alert Logic to collect CloudTrail and other logs from your S3 buckets, you must allow permission for the IAM role you created above to access the ListObjects and GetObject APIs for the bucket and prefix where you store the logs.

The process to configure the S3 bucket policy depends on your current configuration. Use one of the following procedures to either create an Amazon S3 bucket policy or edit an existing Amazon S3 bucket policy.

Create an Amazon S3 bucket policy

You must create an S3 bucket policy if your CloudTrail does not have that policy set up.

To create an Amazon S3 bucket policy:

  1. From the IAM Console click Roles, select the role you created above, and then note the IAM Role ARN value to ensure that the correct policy is applied to your bucket.
  2. From the Amazon S3 console, find the bucket that stores the logs to be collected.

    If the logs are stored under one or more prefixes (which appear as folders in the console), note the prefix but stop at the top-level bucket, because bucket policies can only be edited from this level.

  3. Click Properties, and then expand the Permissions section and click Add Bucket Policy.
  4. Define the policy as follows:
    1. Download and open this policy document and paste the contents into the bucket policy window.
    2. Where indicated, replace BUCKET_NAME/PREFIX with the name of your bucket.
    3. Where indicated, replace YOUR_IAM_ROLE_ARN with the IAM role you created above.
  5. Click Save.

Edit an existing Amazon S3 bucket policy

If the Amazon S3 bucket where you store logs has an existing bucket policy, you must make the following changes to your policy to allow the IAM role created for Alert Logic to collect logs.

To update an existing Amazon S3 bucket policy:

  1. From the Amazon S3 console, find the bucket that stores collected logs.

    If the logs are stored under one or more prefixes (which appear as folders in the console), note the prefix but stop at the top-level bucket, because bucket policies can only be edited from this level.

  2. Click Properties, expand the Permissions section, and then click Edit Bucket Policy.
  3. Make the following changes to your policy:
    1. Download the bucket policy block (.txt) and copy the contents.
    2. After the last permissions statement in the bucket policy window, paste the bucket policy block contents.
  4. Where indicated, replace BUCKET_NAME/PREFIX with the name of your bucket.
  5. Where indicated, replace YOUR_IAM_ROLE_ARN with the account number of the protected account.
  6. Click Save.

Deploy IDS appliances and scanning appliances

Manual deployments require that you deploy IDS and scanning appliances into each VPC you specified as protected by the Professional level of service in your scope of protection. Alert Logic provides three AWS CloudFormation templates to help you deploy an IDS appliance, a scanning appliance, or both to the AWS deployment. Right-click and copy the link to the template you require.

The CloudFormation template to deploy both an IDS and a scanning appliance can also be used to only deploy either appliance. If you then need to deploy either an IDS or scanning appliance in the future, you can change the parameters to include it using the instructions below.

To use the CloudFormation templates, you need information about the VPCs and subnets in your account. To find your AWS VPC and subnet information, log into the AWS console, and access the VPC Management Console. For more information, see the AWS documentation, VPCs and Subnets.

Perform the following steps to use the CloudFormation template to deploy an IDS and scanning appliances:

  1. Log into the AWS console.
  2. Access the CloudFormation service.
  3. On the Stacks page, click Create stack, and then in the drop-down options, select With new resources (standard).
  4. On the Create stack page, under Specify template, select Amazon S3 URL as the Template source, and then paste the CloudFormation template link provided above into the Amazon S3 URL field.
  5. Click Next.
  6. On the Specify stack details page, enter the required information below:

    1. In the Target VPC field, select the target VPC you want to protect from the drop-down options.

    2. In the Target VPC CIDR field, enter the VPC CIDR range. You can get this from the Target VPC drop-down option selected in the previous step.

    3. In the Target Subnet ID field, select the target subnets you want to protect. Alert Logic recommends you select all subnets under the VPC you want the appliance to be able to deploy in.

    4. Set the Assign Public IP field as true if the subnets are public or as false if they are private.

    5. Under the IDS configuration section, enter the Number of IDS instances to deploy (as an integer value between 1 and 10), and select the AWS instance type. By default it is configured to deploy 1 instance of type c5.xlarge.

      This section is not present for the scanning appliance only template. If it is available but you do not want to deploy an IDS appliance at this time, set the Number of IDS instances to deploy to 0. You can then change this setting in the future when you are ready to deploy an IDS appliance.

    6. Under the Scan configuration section, enter the Number of Scan instances to deploy (as an integer value between 1 and 10), and select the AWS instance type. By default it is configured to deploy 1 instance of type c5.large.

      This section is not present for the IDS appliance only template. If it is available but you do not want to deploy a scanning appliance at this time, set the Number of Scan instances to deploy to 0. You can then change this setting in the future when you are ready to deploy a scanning appliance.

  7. Click Next.
  8. On the Configure Stack Options page, click Next.
The parameters on the Configure Stack Options page are optional, and you do not need to set them.
  1. On the review page, select the three check boxes acknowledging the capabilities and transforms, and then click Create stack.
  2. From the CloudFormation stacks page, ensure that this stack appears with the status CREATE_COMPLETE.

Repeat this procedure for each VPC where you need to deploy an IDS and/or a scanning appliance.

Install the Alert Logic agent

Alert Logic provides a single agent that collects data used for analysis, such as log messages and network traffic, metadata, and host identification information. Click the links below for more information and to download the appropriate agent:

Update the Alert Logic agent firewall rules

Ensure the proper outbound firewall rules are in place for the node where you installed the agent. For information about firewall rules, see Alert Logic firewall rules for the US or UK/EU.

Update the Alert Logic appliance firewall rules

If you used a CloudFormation template or a Terraform template provided by Alert Logic for your appliance installation, you do not need to perform this step.

Ensure the proper inbound and outbound firewall rules are in place for the appliance. For information about firewall rules, see Alert Logic firewall rules for the US or UK/EU.

Configure log sources

If you have a Professional subscription, you can set up log collection. To add log sources for data you want to collect, see Log Sources.

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.