AWS Audit
AWS audit deliverables
Every audit produces a set of documents for three audiences: engineering teams, the CISO and leadership.
Reports are currently written in French.
| Deliverable | Format | For |
|---|---|---|
| 10 domain reportsFindings ranked by severity, affected resources (ARNs, IDs) and corrective actions with expected gains. | Word and PDF | Cloud and security teams |
| Kill-chain report5 to 10 attack scenarios chaining findings from several domains. They drive remediation priorities. | Word and PDF | CISO |
| Remediation planTechnical summary of the actions, prioritised P0, P1 and P2. An action that breaks several attack scenarios is raised to P0. | Word and PDF | Cloud teams |
| Action planPrioritised actions, per-domain summary, Gantt, Pareto and return on investment. | Excel | Project steering |
| Executive summaryA narrative summary: current state, major risks and recommended trajectory. | Word and PDF, 5 pages | Leadership, CISO |
| Board deckOverall verdict, scores for the ten domains, top five risks, flagship attack scenario and roadmap. | HTML and PDF, 17 slides | Executive committee |
| DAST results (option)OWASP ZAP alerts on your public endpoints are analysed in the web security report. | Included in the web security report | Application teams |
Sample deliverables
Two board decks produced on demo environments. Companies and data are fictitious. Samples are shown in English; delivered reports are currently written in French.
E-commerce - Maison Verano (demo)
1 AWS account, 2 regions, 2,146 resources, 142 findings, DAST scan enabled. Overall score: 74/100.
View the sample (HTML deck, 17 slides, use the ← → keys to navigate)
Fintech - Kaelis Pay (demo)
1 AWS account, 3 regions, 1,284 resources, 187 findings, DAST scan enabled. Overall score: 52/100.
View the sample (HTML deck, 17 slides, use the ← → keys to navigate)
What a domain report contains
The ten reports follow the same outline: they are quick to read and easy to compare across domains or from one audit to the next.
- Executive summary: the state of the domain in a few paragraphs, strengths, points of attention, main risks and a key-indicator table.
- Score per sub-domain: a mark out of 100 for each sub-domain, for example IAM, S3 or logging in the Security report.
- Detailed findings: a table sorted by severity, then each finding with the affected resource (ARN or identifier), its category, the reference control (FSBP, CIS v5.0) and the recommendation.
- Prioritised action plan: each action gives its priority, criticality, complexity, phase, effort in days and expected impact; for FinOps, the estimated monthly savings.
- Audit limitations: what could not be checked, for example a service disabled in the account.
Severities, scores and priorities
The reports, the action plan and the deck share the same scale. A critical finding in the IAM report weighs as much as a critical finding in the Network report.
- Finding severity: critical, high, medium or low. Passed controls are also listed as compliant, to show what is already in place.
- Score of each domain, out of 100: 90 and above, compliant; 70 to 89, medium; 50 to 69, high; below 50, critical.
- Action priority: P0, P1 and P2, from most to least urgent. An action that breaks at least three attack scenarios becomes P0.
The Excel action plan
The workbook gathers the actions of all ten domains in one file, to steer remediation over time.
- Action plan: every action with its domain, priority, criticality, complexity, expected impact and a Status column to keep up to date.
- Summary by domain: the number of actions per domain, split by priority.
- Timeline and simplified Gantt: the sequence of actions by phase, starting with P0.
- Pareto: actions sorted by monthly savings, with the running total, to spot the ones that pay off most.
Who reads what
- Leadership and board: the deck, for the verdict, the five main risks and the roadmap; the executive summary for detail.
- CISO: the kill-chain report, which shows how an attacker would chain the weaknesses, then the Security, IAM and Web security reports.
- Cloud teams: the remediation plan and the domain reports, which name every resource to fix.
- Programme management and FinOps: the Excel workbook, to track progress and quantify savings.
The Word files are editable: you can add your comments or a cover page before sharing them internally.
Delivery
Deliverables are emailed to the address verified at sign-up, as a ZIP archive and as individual downloads. They remain available for 7 days, then are deleted automatically.
Deliverables: frequently asked questions
How long until the deliverables arrive?
Usually 30–60 minutes after launch, depending on the number of regions and the size of the account. An email goes to the address verified at sign-up.
Are the reports available in English?
No. The reports are currently written in French.
How long do the deliverables stay available?
7 days. They are then deleted automatically: download the ZIP archive to keep them.
Can the reports be passed on to an auditor or a customer?
Yes, the deliverables are yours. They quote your resource identifiers: review them before sharing outside your organisation.
Can two audits of the same account be compared?
Yes. The outline and the score scale are the same from one audit to the next: run a new audit after remediation and compare the scores per domain.
Ready to audit your AWS account?
Subscribe on AWS Marketplace, deploy the read-only role and get your reports within the hour.