AWS Overview & Support
After InsightCloudSec is successfully installed, you're ready to enable visibility into your target AWS Organization(s) and/or cloud account(s). This documentation details configuring your Amazon Web Services (AWS) environment to "talk" with InsightCloudSec securely. Review the sections below to determine the best starting point for your environment.
AWS in InsightCloudSec: Frequently Asked Questions (FAQ)
The following frequently asked questions and answers should help you understand AWS in InsightCloudSec.
What does InsightCloudSec support from AWS?
What does InsightCloudSec support from AWS?
As one of the leading public cloud service providers, InsightCloudSec provides broad support for Amazon Web Services (AWS). Review the full list of AWS-specific supported services on the AWS Support Reference page.
How do I start seeing my AWS environment(s) in InsightCloudSec?
How do I start seeing my AWS environment(s) in InsightCloudSec?
InsightCloudSec relies on a process called "harvesting" to pull data from various CSPs. Review AWS - Onboarding for details.
What do I do after my environment(s) is being harvested?
What do I do after my environment(s) is being harvested?
After at least one AWS account is harvested by InsightCloudSec, you're free to configure additional AWS services as necessary to enhance, optimize, or further secure your experience. Review AWS Additional Configuration for more information. Note: The items in this section were written in the AWS Commercial context.
How can I optimize harvesting?
How can I optimize harvesting?
InsightCloudSec harvesting is the term we use to describe the process of data collection from a selected cloud service provider (CSP) within InsightCloudSec. Check out our Harvesting Overview documentation to understand the basics and refer to Harvesting Strategies for details on specific strategies.
In addition, for AWS, InsightCloudSec offers Event-Driven Harvesting, which requires additional configuration but optimizes harvesting by only pulling in new data when certain AWS CloudWatch Events occur. Review our AWS Event-Driven Harvesting documentation for more information.
Manage AWS Cloud Accounts
After initial configuration of the account in AWS, you can add the account to InsightCloudSec. You can manage and delete existing accounts in InsightCloudSec.
Add a cloud account
Add a cloud account
Onboard a cloud account using the cloud account onboarding wizard. Go to Connect an AWS Cloud Account to get started.
New AWS Onboarding
Beginning with InsightCloudSec version 23.4.11, a new AWS onboarding experience is available. This experience replaces our previous onboarding process.
Modifying and Deleting Existing AWS Cloud Accounts
Modifying and Deleting Existing AWS Cloud Accounts
- Modify: For general information about managing existing AWS Cloud accounts, check out the Clouds section and subsections on Cloud Account Setup & Management. Information about viewing the details of a single cloud account is available on the Cloud Account Detail Page. You can always add additional cloud accounts through the AWS Cloud - Onboarding process
- Delete: Cloud accounts can be deleted through their individual page, details on deleting a cloud account are available here.
AWS Commercial Support Reference
Supported Services
Supported Services
Listed below are all of the AWS services (and their components) supported by InsightCloudSec. If you have questions related to AWS or specific services and their support, contact us through the Customer Support Portal.
Note: If you're interested in the AWS China or GovCloud support for InsightCloudSec, review the China Cloud Support Reference or Government Cloud Support Reference for details instead.
📘 AWS Supported Services & Regions
In general, InsightCloudSec provides support for the AWS services listed below for all regions in which they are available. In some scenarios, some services may not be available in certain regions (or for AWS GovCloud/China in general). This is typically the result of restrictions related to the region itself or otherwise imposed by AWS to comply with regional policies. We recommend that you refer to the AWS documentation on those specific regions for official details.
Also note that InsightCloudSec now recognizes the EC2 Serial Console as part of general EC2 service support.
text
Supported API calls
Supported API Calls
Listed below are all of the API calls supported across AWS services based on the many policies that InsightCloudSec provides. This list is for administrators who may want to fine tune a policy with granular read/write operations.
text
AWS policies
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.
Policy URLs during onboarding
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 AWS onboarding experience to add 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.
Useful Terminology
Some concepts and terminology you should be aware of while reviewing the sections below:
| Term | Description |
|---|---|
| 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:
|
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.
Onboarding and Harvesting Policies
Consolidated Assume Role Policy
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
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
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
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
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
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
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.
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.