The documentation below describes the current Alert Logic console, which was recently updated. This version will be phased out in early 2020. For more information about the new Dashboards navigation, see Managed Detection and Response Navigation Menu Updates.
An Alert Logic deployment allows you to specify the assets—such as appliances, agents, hosts, and collectors—in your environments to monitor and protect. You must create a deployment, regardless of your subscription level, or your assets will not be monitored or protected. You can create deployments for assets found in your Amazon Web Services (AWS) and Microsoft Azure cloud platforms, and from other cloud-based or physical data centers.
Alert Logic discovers and organizes deployment assets into a visual topology where you can select the desired levels of protection, based on your Alert Logic subscription level, for the assets. Choose one of the following levels of coverage for each asset:
- Alert Logic Essentials coverage
- Alert Logic Professional coverage (if you have a Professional or Enterprise subscription)
When you create a deployment, the Alert Logic console prompts you through the following steps:
- Configure third-party access to cloud-based assets (AWS and Azure deployments only)
- Discover assets (AWS and Azure deployments)
- Add assets (Data Center deployments)
- Define the scope of your protection
- Schedule scans
- Install appliances
- Update firewall rules and configure ports for scanning
- Set up log sources and remote collectors
This is the general workflow for all deployments. For more detailed information and deployment creation instructions, see:
When you create an AWS or Azure deployment, you must grant Alert Logic access to your cloud environments for asset discovery and scanning. The access granted to Alert Logic provides only the amount of access required to monitor the assets in your cloud environments.
After you grant Alert Logic access to your cloud account or subscription, Alert Logic automatically discovers its assets. Alert Logic displays the assets discovered in your account in a visual topology diagram. To learn more about topology, see Topology.
If Alert Logic does not discover all your assets, you can add external assets by domain name or IP address.
For Data Center deployments, Alert Logic suggests you add your assets by using discovery scans. Although you can add your assets manually, weekly discovery scans ensure your Data Center deployments are configured with the right ranges.
You can define the scope of your protection per network basis. Each network appears within its protected region. Click a region or individual network to set the scan level or leave it unprotected. You also have the option to exclude assets or tags from external scanning, internal scanning, and Network IDS.
Alert Logic automatically performs certain scans. You can schedule when and how often you want Alert Logic to scan for new assets or perform vulnerability scans.
The topology diagram provides an overview of your scope of protection. You can see which assets are unprotected, or are scanned at the Essentials or Professional levels.
Regardless of deployment type you create, you must configure appliances for scanning and network IDS. Your deployment type and subscription determine the appliances you need to set up.
If you have a Professional subscription, you must install an 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. For more information about installing agents, see Install the Alert Logic Agent for Linux or Install the Alert Logic Agent for Windows.
Update the Alert Logic agent firewall rules
If you installed the Alert Logic agent, 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.
Configure ports for scanning
For internal scanning, Alert Logic recommends that the appliance IP should be able to communicate with target assets for scanning over ports 1-65535 to validate any open service running on any port on the assets. This configuration also allows Alert Logic to test for vulnerabilities that may exist for those services.
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 for more information.