keyboard_arrow_down
  • 12.0
  • 20.0

Integrate Deep Security with AWS Services

Use the Deep Security API along with the AWS APIs to integrate Deep Security with various AWS services. The workflow examples presented here describe how to integrate with the following AWS services:

  • Amazon GuardDuty
  • Amazon Macie
  • Amazon Inspector
  • AWS WAF
  • AWS Config
These examples replace the code samples that were hosted on GitHub that integrated Deep Security with each of these security services.

The AWS Cloud works on a shared responsibility model. For any service you use, you and AWS share responsibilities across a set of operational and security areas. For Amazon EC2 instances and Amazon ECS container hosts, you are responsible for the security of the operating system, any applications, and your data. Deep Security is designed to help address these responsibilities. AWS offers a number of security services that also help address these responsibilities and can provide additional insights to Deep Security.

Workflow pattern

Most workflows for integrating Deep Security with AWS services follow the same pattern where Deep Security reacts to events and information that AWS generates.

  1. The AWS service generates a data point such as an alert or finding.
  2. A CloudWatch event is generated.
  3. The event triggers your AWS Lambda function.
  4. The Lambda function uses the Deep Security API to perform an action on Deep Security Manager.

This workflow captures information from the environment to make smarter decisions within Deep Security. You can easily customize this pattern to your environment, as illustrated in the following examples.

Amazon GuardDuty

The Amazon GuardDutyservice continuously monitors VPC flow logs, Amazon CloudTrail logs, and custom IP lists for issues and threats that may impact your AWS account.

As part of these activities, GuardDuty may also discover indications of issues on EC2 instances that are running in your account. When it discovers an issue, it raises a finding. These findings are an excellent source of information that you can use to trigger an action in Deep Security.

Use the following workflow to integrate with GuardDuty:

  1. Amazon GuardDuty generates a finding that cites an EC2 instance.
  2. Amazon CloudWatch raises an event with the GuardDuty finding.
  3. The Cloudwatch event triggers an AWS Lambda function that is subscribed to the CloudWatch event.
  4. The Lambda function determines whether the EC2 instance is protected by Deep Security and reacts accordingly:
    • Protected: The Lambda function runs a recommendation scan (applying the results) and an integrity scan to verify the protections are in place
    • Not protected: The Lambda function highlights the unprotected instance to the relevant team

When GuardDuty discovers an issue with an EC2 instance, such as possible crypto mining or unusual network traffic, Deep Security ensures that the EC2 instances have the latest rules applied and havent been compromised according to the applied integrity ruleset.

Amazon Macie

Amazon Macie (in limited release) examines the contents of Amazon S3 buckets to discover, classify, and protect sensitive data. Macie finds personally identifiable information (PII) or sensitive corporate data and highlights that risk.

When misconfigured, S3 buckets can be a significant source of exposure. When Macie discovers an issue, it raises an alert via a CloudWatch event. This event can trigger an action in Deep Security.

You can use the bucket and IAM permissions to determine if Deep Security can help to reduce the risk to the S3 buckets by ensuring that related EC2 instances have the latest rules applied.

Use the following workflow to integrate with Macie:

  1. Amazon Macie raises an alert.
  2. Amazon CloudWatch raises an event from the Macie alert.
  3. The CloudWatch event triggers an AWS Lambda function that is subscribed to the CloudWatch event.
  4. The Lambda function performs the following tasks:
    1. Discovers the IAM roles for which the S3 bucket permissions allow access.
    2. Determines whether any Deep Security-protected EC2 instances use the IAM roles and have access to the bucket.
    3. Runs a recommendation scan (applying the results) and an integrity scan to verify that protections are in place.

Amazon Inspector

Amazon Inspectoris an automated security assessment service that can help improve the security and compliance of your EC2 instances and ECS hosts. Inspector runs as an agent on the instance and generates a report as a result of an assessment request.

This report lists the vulnerabilities or issues that are discovered on the instance. For security vulnerabilities, the findings usually include a CVE identifier. The CVE identifier can be correlated with the applied Deep Security Intrusion Prevention rules to ensure that adequate coverage is in place.

Use the following workflow to integrate with Inspector to augment Deep Security recommendation scans:

  1. Amazon Inspector runs an assessment and generates a finding.
  2. Amazon CloudWatch raises an event from the finding.
  3. The event triggers an AWS Lambda function that is subscribed to the CloudWatch event.
  4. The Lambda function performs the following tasks:
    1. Determines whether the affected EC2 instance is protected by Deep Security.
    2. If protected, determines whether there is an Intrusion Prevention rule that corresponds to the CVE cited in the finding.
    3. Applies the rule to the policy that is assigned to the EC2 instance.

AWS WAF

AWS WAF is a web application firewall that runs on the 120+ points of presence that make up the AWS Edge. WAF examines layer 7 web requests to discover common web-based attacks.

While the Deep Security Intrusion Prevention module can stop these attacks, it is desirable to blocks these types of attacks as far away from organizational data as possible.

Trend Micro offers two sets of managed rules for AWS WAF:

Using the following simple workflow to highlight which EC2 instances and ECS hosts are protected by the AWS WAF and are a good candidate for leveraging the managed rule set:

  1. A scheduled Amazon CloudWatch task triggers an AWS Lambda function.
  2. The Lambda function performs the following tasks:
    1. Check each CloudFront distribution for an associated WAF WebACL (WACL) ID.
    2. Check each ELB and ALB for an associated WAF WACL ID.
    3. For each instance that is associated with a WAF-protected resource, determine which Deep Security policy is used to protect it.
    4. Apply the appropriate set of managed rules based on the Intrusion Prevention rules that are assigned to the policy (web server or web application).

AWS Config

The AWS Configservice records changes in your environment and creates visualizations of them. This information enables you to audit, evaluate, and asses your environment. As the service continuously monitors your environment, it allows rules (AWS Lambda functions) to execute when specific changes occur, and add information to this essential compliance tool.

As Deep Security plays a critical role in your compliance story, integrating with AWS Config can be invaluable.

The Rules feature in AWS Config is very straightforward: select a trigger and AWS Config executes your AWS Lambda function when that trigger occurs. The most common trigger to select is Resource/EC2 instance. Each time an instance changes, the Lambda function executes.

The Lambda function can retrieve information about the instance when a change occurs, for example:

  • Whether the instance protected by a specific policy
  • Whether a specific protection module (such as Anti-Malware) is active on the instance
  • Whether the instance is clear of warnings

Each of these examples provides valuable compliance information that can easily be recorded in AWS Config, creating a single source of data for compliance audits.