AWS Cloud Operations Blog

Generate User Access Privilege Reports with AWS Audit Manager

Customers adhere to compliance programs and certifications mandated by their business and industry regulations. A key component of achieving compliance is producing a user privilege and access report for their cloud infrastructure.

Auditors use user privilege and access report to ensure permissions are locked down at a granular level. Access control mechanisms are imposed at different levels (e.g. Service control policies, resource-based policies, user/ group/ role policy, permission boundary etc). This makes it hard to generate a consolidated access report.

This post aims to help you get started on achieving a detailed privilege report using native AWS services and storing the results in AWS Audit Manager.

Audit Manager is a fully-managed service that provides prebuilt frameworks for common industry standards and regulations, and that automates the continual collection of evidence to help you prepare for an audit. The continuous and automated gathering of evidence related to your AWS resource usage helps simplify risk assessment and compliance with regulations and industry standards.

AWS Config enables customers to evaluate the configuration settings of AWS resources. This is done by AWS Config rules, which evaluate the current state against the desired state. Customers can use AWS-managed rules or custom rules. You can use Audit Manager to capture AWS Config evaluations as evidence for audits. When you create or edit a custom control, you can specify one or more AWS Config rules as a data source for evidence collection.

AWS Identity and Access Management (IAM) helps to specify who or what can access services and resources in AWS, centrally manage fine-grained permissions, and analyze access to refine permissions across AWS.

Service control policies (SCPs) are a type of organization policy that you can use to manage permissions in your organization. SCPs offer central control over the maximum available permissions for all accounts in your organization.

Overview of solution

We demonstrate how to create an AWS Config Custom Rule which gathers configuration evidence automatically, stores them in Amazon Simple Storage Service (Amazon S3), and provides the link to the evidence with the AWS Audit Manager assessment report. Using this solution, customers can automate the process of generating custom reports and reduce the manual effort of importing evidence to their Audit Manager assessments.

We use AWS Lambda backed AWS Config Custom Rules to extend AWS Config and collect configuration evidence for IAM Users/Groups. This evidence will be stored in Amazon S3 and referenced as part of your AWS Audit Manager custom assessment report.

In this post we will cover –

  1. Setting up Audit Manager Custom Assessment
  2. Setting up Custom Rules for AWS Config using AWS Config Custom Lambda Rules.
    • Use AWS Lambda to Generate policy report for IAM Users (includes AWS Managed, in-line policies and policies attached to assigned groups)

Figure 1. Architecture Diagram for Solution which includes AWS Audit Manager, AWS Config, AWS Lambda and Amazon S3.

Prerequisites

Deployment Steps

Step 1: Login to AWS Console and navigate to AWS Cloud9 IDE.

Step 2: Follow Instructions to Setup AWS Cloud9 Environment EC2.
(Make sure to Select the Amazon Linux 2 AMI for the platform)

Step 3: Run the following commands on the terminal of the AWS Cloud9 IDE.

Check Python Version by running
python – V
If Python version in your Cloud9 IDE is 3.9, then move to Step 5. Otherwise, continue to Step 4

Step 4: Download Python 3.9 to continue with the deployment:

a. Download the corresponding packages from https://www.python.org/ftp/python/ to create XlsxWriter Lambda layer.
wget https://www.python.org/ftp/python/3.9.10/Python-3.9.10.tgz

b. Extract the file:
tar xvf Python-3.9.10.tgz

c. Build and install the Python Version:
cd Python-*/
./configure --enable-optimizations
sudo make altinstall
cd ..

d. Check the version for python again by running:
python3.9 -V

e. Create a virtual environment:
python3.9 -m venv layer_package

f. Activate your virtual environment:
source layer_package/bin/activate

g. Create a new folder:
mkdir packaging
cd packaging

h. Continue to Step 5

Step 5: Create Lambda Layer:

pip install XlsxWriter
mkdir python
cp -r /home/ec2-user/.local/lib/python3.9/site-packages/*python/
zip -r lambda_layer.zip python
aws lambda publish-layer-version --layer-name my_lambda_layer --zip-file fileb://lambda_layer.zip --compatible-runtimes python3.9.10

Step 6: Create a S3 Bucket
(Note: Enable versioning on the S3 bucket, this enables us to save incremental versions of the report we generate)

Step 7: Navigate to AWS CloudFormation. Choose ‘Create stack’ followed by ‘With new resources (standard)’.  Download the following CloudFormation Template, then in the ‘Specify template’ section, select Upload a template, select choose file and choose the file you just downloaded.  Once you have configured the stack to use the “privileged-user-report” template file you can choose ‘Next’.

Step 8: Enter the requested information:

a. ConfigRuleName – specify a unique name for the AWS Config Rule which runs periodically to invoke a custom lambda function for generating a report on user privileges and saves it to an S3 bucket specified in the parameters below.

b. Under LambdaLayerARN – please specify the ARN copied in Step 5.

c. For the S3BucketName – enter the bucket name created in Step 6.

d. Choose ‘Next’.

Step 9: Choose ‘Next’, then check the Capabilities checkbox, and choose ‘Create stack’. Wait until the stack is in the ‘CREATE_COMPLETE’ state.

Step 10: Create a custom control under Audit Manager:

To create a custom control in Audit Manager that will use your new AWS Config Custom rule as a data source, follow Creating a new custom control from scratch. To attach your custom Config rule, choose Data source type as AWS Config. Follow below instructions to create Custom Control.

Figure 3. Add custom AWS Config Rule based data source in AWS Audit Manager

Step 11: Now that a custom control is defined that is leveraging the AWS Config custom rule that you built, it’s time to create a framework to use the custom control. Note that you could modify any existing framework and add the custom control. However, for the purpose of this post, we’ll create a custom framework and add the control that you previously created.

Step 12: Choose ‘Framework Library’ from the left pane of AWS Audit Manager Console.

Step 13: Choose ‘Custom frameworks’, followed by ‘Create custom framework’

Figure 4. Create Custom Framework on AWS Audit Manager Console.

Step 14: The ‘Framework name’ field is the only required field. However, you may complete the fields that are suitable for your use. You may also tag the framework with the key/value pairs in any way you wish. Tagging can help with automation and analysis in the future.

Step 15: Choose ‘Next’ to define custom control.

a. Enter a ‘Control set’ name

b. Choose ‘Custom controls’ from the ‘Select control type’ dropdown

c. Under ‘Available custom controls’, check the box next to the custom control that you defined in the previous step, and choose ‘Add to control set’.

Step 16: Confirm the choices, then choose ‘Next’.

Step 17: Review your choices and choose ‘Create custom framework’.

Step 18: Next Step is to create an Assessment.

a. Click on ‘Assessments’ on the left pane

b. Click on ‘Create Assessment’

c. On the Specify assessment details tab –

i. Enter an Assessment name

ii. Select the S3 bucket created in Step 6.

iii. Under Frameworks – pick the custom framework we created earlier in Step 16.

d. Select the AWS account you are running in

e. Under AWS Services in Scope – make sure to select AWS Config.

f. Pick Audit Owners.

g. Click ‘Review and Create Assessment’.

Step 19: Go to the AWS Config dashboard, and choose ‘Rules’ in the left navigation pane. Choose the rule created by the stack. Choose ‘Actions’, then ‘Re-evaluate’. The last successful evaluation should change within a few minutes and reflect the latest evaluation.

Step 20: On the Config Dashboard, navigate to ‘Rules’.
Select the Rule created by the CloudFormation template

Step 21: Set ‘Resources in scope’ to display ‘All’. You should see the latest rule evaluation details.

Step 22: Navigate Back to Audit manager console and Generate an assessment report and download it.

Step 23: Unzip the report zip file, go to the unzipped folder, and open the AssessmentReportSummary PDF file. Scroll down to the ‘Assessment report selection’ section and choose the collected evidence. This will open another PDF file (which can also be found separately in the folder structure in the same folder).

Step 24: Scroll down to the ‘annotation’ field where you should find the link to the evidence in the designated S3 bucket. Open the link in a browser, and download the evidence file. Open it and observe the collected configuration evidence.

Cleaning up

To avoid incurring charges, delete the resource you created as part of this post:

    1. Navigate to Audit Manager’s assessments page. Select the assessment you created, then select delete.
    2. Navigate to Audit Manager’s assessment reports page. Select the report you created, then select delete.
    3. Navigate to Audit Manager’s Framework library page. Under Custom frameworks tab, select the custom framework you created. Select action, then select delete.
    4. Navigate to Audit Manager’s Control library. Under Custom controls tab, select the custom control you created, then select delete.
    5. Delete the CloudFormation stack you created.
    6. Delete the lambda layer on the AWS Lambda Console.
    7. Delete the Cloud9 instance.

Consider this as a very first step in laying out the foundation for generating a consolidated access report. To take this further, similar reports can be generated for different policy controls (e.g.: resource based policy, resource boundary etc.) and stored in S3. The reports in S3 can be formatted and queried using Athena/ Glue. To make it more interactive, an Amazon QuickSight dashboard can also be created.

Conclusion

In this post, we demonstrated how to create an AWS Config custom rule to gather configuration evidence automatically, store them in Amazon S3, and provide a link to the evidence with the Audit Manager assessment report. Using this solution, customers can reduce the manual effort of importing evidence to their Audit Manager assessments.

In this blog post we described how to generate a permission report for AWS IAM users and Groups. We also have an example to pull a report for Service control policies (SCP) here. You can use this to list all SCPs affecting your AWS account.

About the authors:

Anu Jayanthi

Anu Jayanthi is an AWS Solutions Architect. She works with Startup customers, providing advocacy and strategic technical guidance to help plan and build solutions using AWS best practices.

Parth Shah

Parth Shah is a Sr. Startup Solutions Architect at Amazon Web Services. He enjoys working with startup customers in cloud adoption and business strategy as well as helping them design applications and services on AWS. Outside of work, he enjoys gaming, soccer, traveling, and spending time with his friends and family.

John Fischer

John Fischer is a Senior Assurance Consultant for the AWS Security Assurance Services team and is a product specialist for AWS Audit Manager. In his spare time, John enjoys performing in his wedding band and spending time with his wife and kids.