CloudTrail Not Enabled
API activity in this account is not recorded, so there is no audit trail to investigate an incident with.
Free to start. No card. The playground just needs your work email.
AWS
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across AWS, with read-only access to the account.
Explain
Every finding says exactly what to change: Enable a multi-region CloudTrail.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- CloudTrail on AWS
- The fix, by hand
- CloudTrail → Trails → Create trail → Apply to all regions = yes.
- Storage location → new S3 bucket with Object Lock + versioning + a KMS CMK.
- Enable Log file validation, CloudWatch Logs integration (optional), and Insights events.
- (Optional) Enable Data events for sensitive S3 buckets and Lambda functions.
- Verify a test API call surfaces in Event History within 15 min.
These are the steps the finding carries in the product.
- Category
- Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
- Where it appears
- The Compliance tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1521- Full reference
Related checks
See the compliance findings in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.