Home

This document is covering the AWS Penetration testing test cases collected from the internet.

1. Creating a new policy version
2. Setting the default policy version to an existing version
3. Creating an EC2 instance with an existing instance profile
4. Creating a new user access key
5. Creating a new login profile
6. Updating an existing login profile
7. Attaching a policy to a resource
8. Updating an inline policy for a resource
9. Adding a user to a group
10. Updating the AssumeRolePolicyDocument of a role
11. Passing a role to a new Lambda function, then invoking it
12. Passing a role to a new Lambda function, then triggering it with DynamoDB
13. Updating the code of an existing Lambda function
14. Passing a role to a Glue Development Endpoint
15. Updating an existing Glue Dev Endpoint
16. Passing a role to CloudFormation
17. Passing a role to Data Pipeline
18. Privilege Escalation to C2 AWS Administrator
19. EC2 User Data Sensitive H1 Information Leakage
20. CloudTrail H2 Logging Disabled
21. AWS S3 H3 Bucket Data Leakage
22. Weak H4 IAM Password Policy
23. Redshift Cluster Database M1 Encryption Disabled
24. VPC M2 Flow Logs Disabled
25. Redshift Parameter Group M3 SSL Not Required
26. No IAM User M4 Access Key Rotation
27. Unencrypted Elastic Block Store L1 (EBS) Snapshots
28. S3 Bucket Access L2 Logging Not Enabled
29. S3 Bucket Versioning L3 Not Enabled
30. Redshift User Activity L4 Logging Not Enabled
31. Elastic Load Balancer Access L5 Logs Not Enabled
32. EC2 Termination Protection I1 Is Disabled
33. EC2 SSRF Vulnerability

Credit to RhinoSecurityLabs for creating such good resources for the AWS penetration testing.