Minimum Permissions for AWS Connector
This page describes how to configure minimum permissions required by AWS connector to access AWS. The goal is to avoid All Admin rights and give only minimum permissions required for Compliance check and Remediation action.
This page explains how to create custom IAM policies of required roles and privileges in AWS using a JSON file.
Creating custom IAM policies:
This section talks about how to create the IAM policies using JSON file (containing details of permission required by AWS connector on AWS) and attach the Policy to AWS user (configured in AWS connector).
Steps for importing JSON document and attaching to the user:
Create policy -
Steps | Example Screens | |
---|---|---|
1. | Log in to Amazon Console. | |
2. | Go to IAM service. | |
3. | Select Policies from the left side of the screen. | |
4. | Select Create Policy and the following is displayed. | |
5. | Select option "JSON". | |
6. | Copy past below JSON in Policy document text box.
| |
7. | Select Review policy to evaluate the policy. | |
8. | Enter the Policy name (Eg. CompliancePolicy) and a description if required. | |
9. | Click Create policy. You will be notified when the policy is successfully created. |
Attach Policy -
Attach Policy to specific user which is created for BMC Helix Cloud Security.
Steps | Sample Screens | |
---|---|---|
1. | Go to IAM service. | |
2. | Select Users option from the side navigation bar. | |
3. | Select Grant permissions button. | |
4. | Click option "Attach existing policies directly". | |
5. | Select policy which you wish to attach (Eg. CompliancePolicy in this case). | |
6. | Click on button "Next: Review" at the bottom right corner of the page. | |
7. | A permissions summary is shown. Click Add permissions option at the bottom right corner of the page. | |
8. | Click Add permissions option again on the displayed page. | |
9. | After configuring the options available, click Add permissions option once more. The policy will be attached. |
Compliance JSON
For compliance, open the following JSON file:
Compliance and Remediation JSON
For compliance and Remediation, open the following JSON file:
Use Cases and Permissions
Below are the minimum permissions required for BMC Helix Cloud Security Compliance and Remediation use cases to work.
AWS Services involved | Permissions needed for Compliance | Permissions needed for Remediation |
---|---|---|
S3 | "s3:ListAllMyBuckets", | "s3:ListAllMyBuckets", "s3:GetBucketLogging", |
ES | "es:ListTags", | "es:listTags", |
Cloud Trail | "cloudtrail:listTags", "cloudtrail:describeTrails", "cloudtrail:GetEventSelectors" | "cloudtrail:listTags", "cloudtrail:getTrailStatus", |
IAM | "iam:generateCredentialReport", "iam:ListVirtualMFADevices", "iam:ListGroupsForUser" | "iam:generateCredentialReport", |
Cloud Watch | "Cloudwatch:describeAlarms" | "Cloudwatch:describeAlarms", |
Cloud Watch Logs | "cloudwatchlogs:describeMetricFilters" | |
RDS | "rds:DescribeEventSubscriptions", | "rds:describeDBInstances", |
KMS | "kms:DescribeKey", | "kms:DescribeKey", "kms:EnableKeyRotation", |
SNS | "sns:listSubscriptionsByTopic" | "sns:listSubscriptionsByTopic", |
configService | "config:describeConfigurationRecorders", |
"config:describeConfigurationRecorders", |
EC2 | "ec2:describeInstances", | "ec2:describeInstances", |
Elastic Load Balancer | "elasticloadbalancing:DescribeLoadBalancers", | "elasticloadbalancing:DescribeLoadBalancers","elasticloadbalancing:DescribeLoadBalancerAttributes", |
Logs | "logs:describeMetricFilters" "cloudwatchlogs:describeMetricFilters" | "logs:DescribeLogGroups", |
Organisations | "organizations:ListAccounts" | |
SSM | "ssm:describeInstanceInformation", | "ssm:describeInstanceInformation", |
If you select Cost on Minimum Permission for AWS Cloud Connector, please refer to this Page.