AWS security audit
Identify the risks of your AWS infrastructure
For SaaS teams who want to understand their IAM permissions, network exposure, and cloud configuration. Define the perimeter, connect your AWS accounts, and review recommendations based on observed resources.
Discuss an AWS auditA three-step journey
1. Define the perimeter
Select your AWS accounts, regions, and services. Exclude resources that should not be reviewed.
2. Connect AWS
Open the pre-filled CloudFormation page, verify the permissions, and create the audit-specific role. Brunel verifies the connection and initiates resource discovery.
3. Validate and start
Accept the estimate and processing policy, sign the authorization, and pay for the audit. Authorize the read-only role, then explicitly start the analysis.
A report to prioritize corrections
Findings associate observed configuration, evidence, and recommendations. Your team decides on corrections and their implementation. The price depends on the perimeter, the size of the infrastructure, and the depth of analysis chosen. AI providers, regions, and processing rules follow your authorization.
Frequently asked questions
Do I need to provide an AWS access key?
Can the audit modify my infrastructure?
What controls are useful for a SaaS startup?
Is this a compliance certification or a pentest?
Let's talk about your AWS environment
Start with a precise perimeter and the security decisions your team needs to make.