AWS Policies

This page has moved

For consolidated, up-to-date information about AWS Policies, go to AWS Overview.

InsightCloudSec offers several different AWS policies for harvesting resource information found in your AWS accounts and enabling features such as Event-driven Harvesting (EDH), Least Privileged Access (LPA), Host Vulnerability Management (HVM), and Container Vulnerability Management (CVM).

If you're interested in setting up an AWS China or GovCloud account, review the China Cloud Support Reference or Government Cloud Support Reference for details instead.

As always, if you have questions or concerns reach out to us through the Customer Support Portal.

Useful Terminology

Some concepts and terminology you should be aware of while reviewing the sections below:

  • Consolidated -- All IAM Resources deployed by the onboarding CFT include a path prefix of /rapid7/, which helps organize all Rapid7 IAM resources together.
    • Additionally, Roles and Policies both use the naming convention rapid7-<access type>-<feature/usecase> for easy identification.
    • You'll note the IAM Role name rapid7-consolidated, which denotes that policies for all three access types of readonly, egress (a.k.a. data access), and automation are attached to the same role. We reserve this naming convention if we decide to support multiple Roles for each access type use case.
  • Access Types -- The onboarding CFT creates different roles to collect various types of information from your AWS accounts. The access types are listed below.
    • Read Only -- Explicit and fully enumerated read only permissions for cloud configuration control plane APIs without explicit scoping that gives the customer full visibility into their cloud inventory.
    • Egress -- To facilitate features that require collecting/analyzing both cloud control and data plane data that cannot practically be done with cloud APIs. This often requires permissions to create, modify, delete and read from resources in the customer's account.
    • Automation -- Customers can attach as few or as many polices to the consolidated Role to facilitate the customer's automation strategy for a given account. Automation is any action to notify systems InsightCloudSec doesn't own or mutate resources InsightCloudSec don’t own.

Note: New required permissions are announced in our release notes. The API calls that are supported with any of the policies can be found in the Supported API Calls section.

🚧 Policy URLs

As of InsightCloudSec v. 23.4.11, the new universal onboarding experience for AWS accounts uses CloudFormation Templates (CFTs) to automatically provision relevant accounts with the necessary policies and roles that contain your specific, unique InsightCloudSec account information.

We highly recommend using the new experience to onboard your AWS accounts and only use the policies below for reference as some of the URLs provided on this page represent the generic versions of the policies, i.e., there are placeholder values for account-specific information.

Onboarding and Harvesting Policies

Consolidated Assume Role Policy

The Consolidated Assume Role Policy is used to establish the trust relationship to the Authenticating Principal (your InsightCloudSec installation role). Note: This link contains placeholder values for InsightCloudSec-specific account information.

Standard Self Referential Policy

The Standard Self Referential Policy allows for the role to refer to itself, the account, and organization it exists within.

Read-Only Policy

The Read-Only policy consists of three parts (the permissions have exceeded AWS's limitation on policy size). These policies only contain read only-type permissions, e.g., List, Describe, Get, etc., and will need to be updated any time InsightCloudSec supports a new AWS Service.

Feature Enablement Policies

Egress EventBridge Auto Provisioning Policy

The Egress EventBridge Auto Provisioning Policy grants the Rapid7 IAM Role permission to create/manage EventBridge Rules/Targets and create/manage an SQS queue from consuming the Events. Review AWS Event-Driven Harvesting for more information.

Egress LPA Auto Provisioning Policy

The Egress LPA Auto Provisioning Policy grants the Rapid7 IAM Role permission to access CloudTrail, to create the necessary AWS Glue tables and to create/execute Athena queries with a S3 bucket for results. Review AWS Least-Privileged Access (LPA) for more information.

Egress Host Vulnerability Management Via Role Policy

The Egress Host Vulnerability Management Via Role Policy grants the Rapid7 IAM Role permissions to create and download EBS snapshots for vulnerability scanning. Review Host Vulnerability Management for more information.

Egress Container Vulnerability Management Via Role Policy

The Egress Container Vulnerability Management Via Role Policy grants the Rapid7 IAM Role ECR read permission to all ECR repositories in the AWS Account. This allows for pulling images and scanning for vulnerabilities. Some read permissions overlap with the Rapid7 Read-Only Policies, which are used for general visibility and discovery. This Policy duplicates those permissions because the Rapid7 IAM Role may need to access additional metadata before or after pulling an image to capture the most recent context when producing a finding. Review Container Vulnerability Management for more information.

Example Deployment Policies

These IAM Policies can be used as a reference example for a dedicated IAM Role to be used via automation or CI/CD pipeline. These policies allow for programmatically deploying the onboarding CFT, but you'll need to periodically update the CFT for new permissions. Note: the statements scope the permissions to only IAM Roles and Policies related to Rapid7 using our naming conventions but could be expanded upon with more fine grain conditionals.