Skip to main content
McAfee MVISION Cloud

Configure Container Security for ECS

To enable MVISION Cloud Container Security for use with Amazon ECS and EKS, make the following configurations in the Amazon Console and MVISION Cloud. 

NOTE: If you already have an AWS instance set up in MVISION Cloud, nothing will change until you import ECS or EKS policies, after which you will need to provide necessary permissions for configuration audit. 

Configure Amazon ECS

  1. In the AWS Console, go to ECS. 
  2. Create an ECS cluster to use with MVISION Cloud detection. 
  3. Provide permissions to the MVISION Cloud for ECS policies. 

Configure MVISION Cloud IAM Roles for AWS

MVISION Cloud uses AWS CloudFormation Templates to create the IAM roles required to configure AWS accounts. Permissions for all MVISION Cloud features are consolidated in CloudFormation Templates, so you do not have to track and provide permissions separately for each feature. 

For Container Security, use one of three options:

  1. AWS Managed Policy SecurityAudit. This is the recommended option. 
  2. Read-Only Access
  3. Minimum Permissions

Install the SSM Agent on Amazon EC2 Instances

To enable the Docker runtime in ECS and EKS, install the AWS Systems Manager (SSM) agent in the EC2 instance (host) of a particular ECS or EKS cluster. 

For install instructions, see https://docs.aws.amazon.com/systems-manager/latest/userguide/sysman-manual-agent-install.html.

Also, to the IAM role associated with the EC2 instance where you want SSM capabilities, add the policy: arn:aws:iam::aws:policy/service-role/AmazonEC2RoleforSSM

To view SSM managed instances in AWS, go to AWS Systems Manager > Managed Instances

aws_systems_manager.png

NOTE: If the ping status is inactive or lost, restart the SSM agents for different instance types, as mentioned in https://docs.aws.amazon.com/systems-manager/latest/userguide/ssm-agent.html.

Configure MVISION Cloud

Configure a New AWS Instance

If you haven't configured an AWS instance in MVISION Cloud yet, use the following steps.

NOTE: Permissions against all the pre-defined policy templates are checked during authentication.

  1. Go to Settings > Service Management
  2. Select the AWS service instance and click the Setup tab. 
  3. Enable API access, then click Edit
  4. For Enabled Features, make sure Security Configuration Audit is enabled. Click Next
  5. In the Review Prerequisites screen, review permissions and click I have reviewed all prerequisites for enablement and completed any that are mandatory. Click Next
  6. For Accounts, enter your Role ARN. Click Add
  7. Click Authenticate Accounts
  8. Click Save

Configure an Existing AWS Instance

If you already have an AWS instance configured in MVISION Cloud, use the following steps.

NOTE: Permissions against imported policies are checked during authentication and On-Demand Scans. 

  1. Go to Policy > Policy Templates
  2. In the Table view, filter by Business Requirement > Container Security. (For details about policy templates for ECS and EKS, see Policy Templates for Container Security.)
    container_security_policy_templates.png

NOTE: In the Filters > Usage section, you can also choose Not Used to list all un-imported templates.

  1. Select all the templates you want to create policies for and click Actions > Create Policy. Click Create Policies
  2. All the imported policies will appear under Policy > Configuration Audit page
  3. Select the policies and click Actions > Activate Policies.

The policies are activated. Subsequent AWS configuration audit scans discover ECS and EKS resources, and also evaluate these policies and report any incidents.

You may also choose to manually trigger the scan from the Policy > On-Demand Scan. For details, see On-Demand Scans for Container Security

  • Was this article helpful?