Accenture MDR Quick Start Guide for Role Based Access Control in AWS Generic Sensor

This quick start guide will help Accenture MDR customers configure Amazon Web Service (AWS) Role Based Access Control to allow log collection from the Log Collection Platform (LCP).

The document includes the following topics:

1 Pre-requisites
2 Scope
3 Log Collection using cross AWS account (Where LCP is hosted in MDR SOC AWS account and logging resource is in Customer AWS account)
- 3.1 Configure IAM role in MDR SOC AWS account (Account B) to access customer resources (MDR Side Configuration)

Pre-requisites

AWS users should have access to create, modify the IAM role.
Get assumable role ARN from the Accenture MDR(device onboarding team) to configure it in the cloud formation template ACNMDRAwsAccountARN field.

Scope

Log Collection using cross AWS account (Where LCP is hosted in MDR SOC AWS account and logging resource is in Customer AWS account)

Note: Logging resources we support are S3 Bucket, SQS, and CloudWatch log

Log Collection using cross AWS account (Where LCP is hosted in MDR SOC AWS account and logging resource is in Customer AWS account)

Follow these steps:

Configure IAM role in customer AWS account (Account A) with appropriate permissions to the resource (customer side configuration)
Configure IAM role in MDR SOC AWS account (Account B) to access customer resource (MDR Side Configuration)

Configure role in customer AWS account (Account A) with appropriate permissions to the resource using CloudFormation (customer side configuration)

Sign in to the AWS Management Console with Account A.
Open the AWS CloudFormation console at https://console.aws.amazon.com/cloudformation.
Create a new stack by using one of the following options:
1. Choose Create Stack This is the only option if you have a currently running stack.

b. Choose Create Stack on the Stacks page. This option is visible only if you have no running stacks.

4. Select With new resources (standard) Option

5.Create a stack page.

a. On Prerequisite - Prepare template, select Template is ready option

b. On Specify template, select Upload a template file

c. Choose File to select the template file cloudformation.yaml attached below. Once you have chosen your template, CloudFormation uploads the file and displays the S3 URL.

d. Click on Next

6. Specify the stack details

a. Type a stack name as per choice.

b. Parameters:

CreateNewRole: If a role with the name 'ACNMDRCrossAccountRole' does not exist and it needs to be created, select 'Yes'. Otherwise select 'No'
ACNMDRAwsAccountARN: Provide assumable role ARN collected from the Accenture MDR device onboarding team(Accenture MDR assumable role will be used to create trust relation with customer role)
ACNMDRExternalId: Provide an External ID as per your choice, Make sure external id matches the pattern:[\w+=,.@:\/-]* as per the AWS document: AssumeRole - AWS Security Token Service
LoggingResource:

a) S3Bucket: If data is going to be collected directly from S3 Bucket

b) SQS: If SQS is configured for S3 Bucket

c) CloudWatchLog: Data collection from Cloud watch log group

PolicyName: It should be a unique policy name that has not been used previously to assign the policy to 'ACNMDRCrossAccountRole'. Recommended PolicyNames - CrossAccountPolicyFor<S3BucketName> or CrossAccountPolicyFor<SQSName> or CrossAccountPolicyFor<LogGroupName>
S3BucketARN: ARN of the S3 bucket from which logs are going to be collected. S3BucketARN is also required if LoggingResource is 'SQS'. Example Values - arn:aws:s3:::<BucketName> or arn:aws:s3:::<BucketName>/<PrefixPath>/. (Note: Keep S3BucketARN blank in case of 'CloudWatchLogs')
SQSOrCloudWatchLogGroupARN: Provide SQS or CloudWatchLogGroup ARN as per LoggingResource selection, SQSOrCloudWatchLogGroupARN required in case of LoggingResource is 'SQS' or 'CloudWatchLogs', (note: Keep SQSOrCloudWatchLogGroupARN blank if LoggingResource is 'S3Bucket')
S3KMSKeyARN: Provide KMS Key ARN used to encrypt S3 Bucket (Note: Value required in case LoggingResource 'S3Bucket' or 'SQS' and s3 Bucket is encrypted)
SQSKMSKeyARN: Provide KMS Key ARN used to encrypt SQS (Note: Value required in case LoggingResource 'SQS' and sqs queue is encrypted)
SQSOrCloudWatchLogKMSKeyARN: Provide KMS Key ARN used to encrypt SQS queue or CloudWatch log group as per selected LoggingResource (Note: Value required in case of LoggingResource is 'SQS' or 'CloudWatchLog' and SQS queue or CloudWatch log group is encrypted)

c. Click on Next

7. In the Configure stack option, Add Tags and Permissions required as per the organization standards and nomenclature, or keep it unchanged and click on the Next button.

8. On the Review page, review the details of your stack, Please acknowledge the acknowledgment by clicking on the checkbox and click on Create stack button.

9. While your stack is being created, it would appear on the Stacks page with the status as CREATE_IN_PROGRESS, after some time the status will change to CREATE_COMPLETE

10. Once Stack is created, Go to the Outputs tab, copy output values, and share values with Accenture MDR.

Note: CloudFormation template will create a new Role with the name "ACNMSSCrossAccountRole" and will attach read-only policies to the role for the resources that need to be monitored, Template also have the option to attach read-only resource policy to the preexisting role with the name "ACNMSSCrossAccountRole"

Below are the resource policies which will get attached to "ACNMSSCrossAccountRole" based on the logging resources selected in the template

{
"Effect": "Allow",
"Action": ["s3:ListBucket","s3:GetObject"],
"Resource": ["arn:aws:s3:::bucketname", "arn:aws:s3:::bucketname/*"],
"Condition": {}
}

{
"Effect": "Allow",
"Action": [
"logs:describeLogGroups",
"logs:describeLogStreams",
"logs:filterLogEvents",
"logs:getLogEvents"
],
"Resource": [
"arn:aws:logs:region:accountID:log-group:specificLogGroupName"
]
}

{
“Action”: [
“sqs:GetQueueAttributes”,
“sqs:GetQueueUrl”,
“sqs:ReceiveMessage”,
“sqs:DeleteMessage”,
“sqs:ListQueues"
],
“Effect”: “Allow”,
“Resource”: “arn:aws:sqs:region:accountID:SQSName”
}

Note: In the case of SQS make sure you are creating and attaching SQS policy as well as S3 policy to the rule.

Configure IAM role in MDR SOC AWS account (Account B) to access customer resources (MDR Side Configuration)

Sign in to the AWS Management Console with Account B
Open the IAM console.
From the navigation pane, choose Roles.
Choose to Create role.
For Select the type of trusted entity, choose AWS service.
For Choose the service that will use this role, choose EC2
Choose Next: Permissions.
Choose Next: Tags.
You can add optional tags to the role. Or, you can leave the fields blank, and then choose Next: Review.
For the Role name, enter a name for the role.
Choose to Create role.
From the list of roles, choose the role that you just created.
Choose to Add inline policy, and then choose the JSON view.

14. Enter the following policy. Replace arn:aws:iam::111111111111:role/ROLENAME with the Role ARN shared by Customer AWS Account (Account A)

{

"Version": "2012-10-17",

"Statement": [

{

"Effect": "Allow",

"Action": "sts:AssumeRole",

"Resource": "arn:aws:iam::111111111111:role/ROLENAME"

}

]

}

15. Choose Review policy.

16. For Name, enter a name for the policy.

17. Choose to Create policy.

18. Go back to AWS Management Console.

19. Open the EC2 Dashboard.

20. Go to Instances (running) if the LCP machine is running or else go to Instances, search for LCP instance, and start it.

21. Select an LCP instance, go to Actions→ Security→ Modify IAM role

22. Search for the IAM role that you have created earlier and click Save.

23. Go to the LCP UI and configure the appropriate collector using the below sensor configuration

Property	Value	Description
Secret Access ID	<Role ARN>	Configure Role ARN shared by the customer
Secret Access Key	<External ID>	Configure External id shared between Customer and Accenture
S3 Bucket/Log Group(s)/SQS Queue URL	<Resource Name>	Provide S3 bucket name, Log Group Name(s), or SQS URL based on logging source
Region	<Region>	Enter region (Eg: us-west-2)
Logging Source	<Select logging Source >	Select logging Source from dropdown S3, CloudWatch or SQS
Bucket Prefix Path(s)	<PrefixPath>	Incase of Logging Source as S3 example: /AWSLogs/Account-ID/CloudTrail/region,