AWS Configuration Pentest

One of the strongest features of AWS is the immense flexibility offered to the user in setting up the environment. This flexibility is great, but also presents a major security issue that is verified with pentests.

Definition and explanation - IT Security Analysis

What is AWS Penetration Testing?

Amazon Web Services, or AWS, Penetration Testing provides your organization with an IT security analysis of the effectiveness of the AWS configuration. Here, the AWS architecture and its powerful APIs are analyzed using the methods of a real attacker. Deeply integrated into the AWS ecosystem, our security engineers test for a range of AWS-specific misconfigurations, permissions, and implementation flaws.

Modern Cyber Security

AWS Cloud Security

As the basis for secure applications and communication, the cloud infrastructure cannot be neglected. Advanced knowledge of server operating systems, transport encryption, and infrastructure configuration enables our security engineers to efficiently analyze AWS configurations.

Pentesting in the Cloud

Penetration Testing for AWS Configurations

The pentest for AWS configurations is planned, executed and evaluated by our specially trained security engineers according to recognized standards.

Compliance with Safety Standards and Guidelines: We basically test all types of virtualization environments, such as server and operating system virtualizations, application virtualizations and network virtualizations.
AWS Components: We test IAM permissions for exploitable misconfigurations, the access keys for EC2 user accounts, AWS privileges on IAM misconfigurations, Lambda features, and CloudTrail bypassing.
Cloud Native Pentesting: We have developed a comprehensive final report that provides optimal insight into our work and its results. We conduct audits in accordance with the OWASP Cloud Security Guide, among others, and evaluate them accordingly. Alignment with OSSTMM and PCIDSS is also possible on request.

Learn more about Performing Cloud Penetration Tests with turingpoint!

More information

AWS Components and Cloud Security

Scope of Amazon Web Services Cloud Security

As a general rule, the longer our cloud security engineers examine your configuration, the more meaningful the results. If you have special requirements, we will be happy to make you an individual offer.

IAM: The goal of this category is to analyze permissions for privilege escalation paths, through services such as Lambda, EC2, etc., and check for misconfigured roles and access attempts.
EC2/VPC: The purpose of this category is to enumerate instances, security groups and AMIs to perform EC2 attacks. Additionally, the misuse of Simple Systems Manager for remote access to instances is tested and an analysis of EC2 user data for system credentials is created.
S3: This category deals with checking for misconfigured buckets due to unauthenticated access. After authentication, access to S3 buckets for sensitive files and data can be checked and the use of existing S3 buckets to exfiltrate data or perform further attacks.
RDS: The goal of this category is to ensure that the security group rules for accessing RDS databases cannot be circumvented. In addition, RDS authentication is checked by copying backups and changing the RDS password. Lastly, it is checked whether exfiltration of RDS data through the cross-account C2 channel is possible.
Cloudtrail: The requirements from this category are to ensure that various methods to evade detection and cover tracks are detected. Additionally, logs are analyzed to get a better idea of the AWS ecosystem.
Lambda: The goal of this category is to ensure that the code and configuration do not contain sensitive information. In addition, privilege escalation through Lambda IAM roles and SDK's is tested. Finally, data exfiltration through the modification of data processing functions is simulated.