Deployment with AWS Control Tower
Customers who use AWS Control Tower and Alert Logic can get automatic protection of existing and newly enrolled accounts through a series of automations.
The Alert Logic Control Tower Automation uses the following AWS Services to enable automatic protection of newly added AWS Accounts:
- Amazon EventBridge
- AWS CloudFormation
- AWS Lambda
- Cross-account IAM Roles
- AWS Secrets Manager
- Amazon SNS
- Amazon SQS
Accounts shown in the architecture diagram:
- Control Tower Account—Master account on which AWS Control Tower was enabled
- Log Archive Account—Account for centralized repository of logs, including CloudTrail logs
- Audit Account—Restricted account with read/write access to all accounts. A centralized CloudTrail SNS Topic for security and CloudTrail notification islocated here.
- Security Account—An account where Alert Logic Control Tower Automation Orchestration is deployed
- Linked Account—One or more AWS accounts protected by Alert Logic. Alert Logic deploys appliances and agents into this account.
The following steps are associated with the numbers indicated in the architecture diagram.
- When a new Linked account is enrolled into AWS Control Tower, the LifeCycle lambda function receives a notification from AWS Control Tower and deploys an AlertLogic-CT StackSet Instance to the new Linked account.
- In the new Linked account, AlertLogic-CT StackSet Instance creates an IAM Role to enable Alert Logic Asset Discovery. Upon completion, the StackSet Instance sends an SNS event via Custom Resource to the Security account to notify that a new deployment must be registered with Alert Logic.
- In the Security account, a lambda function named Register is subscribed to the ALHubTopic SNS topic to receive new deployment registration requests from the new Linked account. Once the function receives a notification request, it registers a new linked account deployment with Alert Logic.
- When a user in the new Linked account tags or untags any VPCs with the "al," "alertlogic," "tm," or "threatmanager" keys, an event is published to Amazon EventBridge.
- A lambda function named Deploy receives the event and updates deployment protection scope in the Alert Logic console accordingly.
- If you specified Automatic mode during the initial setup, Alert Logic creates a security subnet in a newly protected VPC and deploys Alert Logic appliances. If you chose Manual mode, you must deploy the appliances to protect newly added VPCs. To learn more about deployment modes, see About Deployment Types.
Deployment begins with a CloudFormation stack deployed in the AWS Control Tower Master account. The stack creates two AWS Lambda Functions, two AWS CloudFormation StackSets, and an AWS CloudWatch Event Rule for AWS Control Tower Lifecycle. Onboarding Lambdas are used during initial deployment to orchestrate an AlertLogic-CT StackSet Instance, create an SQS in the Log archive account, and SQS to SNS subscription in the Audit account. Onboarding Lambda also orchestrates AlertLogic-CT-Central-IAM-Role stackset (not shown in the diagram) to create a StackSet Instance in the Log Archive account for CloudTrail ingestion. The CloudWatch Event Rule triggers the Lifecycle Lambda during new AWS account setup. This Lambda deploys AlertLogic-CT StackSets to the new AWS account.
The AlertLogic-CT StackSet launches stackset instances in all AWS accounts included in the scope of deployment. In each account, this stackset creates an IAM role for Alert Logic and a CloudWatch Event rule for detecting tag changes on VPC. The AlertLogic-CT stackset create additional resources in the Security Account, including an Amazon SNS Topic, two AWS Lambda Functions, and an Amazon EventBridge Event bus.
You do not need to enable any additional resources other than the ones enabled by AWS Control Tower.
You do not need to increase any limits, but note that the automation solution creates an EventBridge in a security account to capture tag updates in linked accounts.
Before you implement this solution, Alert Logic recommends that you become familiar with AWS CloudFormation, AWS Lambda, AWS CloudTrail, and Amazon EventBridge services:
- If you are new to AWS, see Getting Started with AWS.
- For additional information on AWSMarketplace, see this documentation on AWS Marketplace.
- To get started with Control Tower, see the AWS documentation on Control Tower.
Deployment and Configuration
Subscribe to Alert Logic Managed Detection and Response on the AWS Marketplace
Locate Alert Logic Managed Detection and Response in the AWS Marketplace
- Click Continue to Subscribe.
- Next, configure your contract. You can set the Contract Duration and Renewal Settings.
- Select the Contract Options to be activated with your contract.
- When you configure your contract, click Create contract.
- You will be prompted to confirm the contract. If you agree to the pricing, click Pay Now.
- Check your email for the validation email from Alert Logic. After you confirm receipt, Alert Logic sends another email to enable password reset and grant you access to the Alert Logic console.
- Log into the Alert Logic console.
Log into the Partner UI
- Create an access key and a secret key in the Alert Logic console. For more information about how to create an access key and secret key, see Create and Manage Alert Logic Access Keys.
- Download the code from <partner-github-repository>.
- Log into the <MASTER|LOG|XXX> account in AWS Control Tower as <Permissions>.
- To deploy the solution, create a new CloudFormation Stack using this template.
Provide the following information to deploy the CloudFormation Stack:
- Alert Logic API Access Key and Alert Logic API Secret Key
- Alert Logic Customer ID – On the Support page in the Alert Logic console
- Control Tower Audit Account ID – Control Tower AWS audit account
- LogArchiveAccount Control Tower account
- SecurityAccount – Designated AWS security account
- TargetRegion – List of regions to enable Alert Logic Managed Detection and Response deployment into
Verify linked accounts
After you complete the CloudFormation deployment, you can see your linked accounts listed as deployments in the Alert Logic console.
Validate that the solution is properly deployed
The Alert Logic appliance deploys automatically within 15 minutes to the linked accounts.
Next, you must install Alert Logic Managed Detection and Response Agents on the protected hosts. Follow these instructions to deploy Alert Logic Managed Detection and Response Agents for Linux or Windows.
Alert Logic automatically claims the agents and assigns them to the appliances.