High severity
Audit logging incomplete
Gaps in the record of who did what: missing regions, missing data-access events, or logs that can be altered.
Updated
What it looks like in each cloud
CloudTrail not enabled in all regions, log file validation off, or no trail capturing data events for sensitive buckets.
Cloud Audit Logs with Data Access logs disabled for the services that hold data; no log sink to a retained bucket.
No diagnostic setting exporting the Activity Log, or key resources without diagnostic settings for audit categories.
Why it matters
Without complete logs you cannot detect an intrusion, scope it afterwards or prove to an auditor what happened. Every framework treats logging as a prerequisite for the other controls.
How it happens
Logging was configured for the first region and never extended. Data-access logs are off by default because of volume and cost. A trail was deleted during cleanup.
How to check
Confirm audit logging is organisation-wide and multi-region, that integrity validation is on, that data-access events are captured for the services holding sensitive data, and that logs land in a protected, retained store.
How to fix it
Enable an organisation-level, all-region trail with validation, turn on data-access logging for the services that matter, and write logs to a locked-down account or project with retention.
Frameworks that require this
The controls this issue falls under. AKRIBOS reports the finding once and maps it to each framework you have in scope.
CIS Benchmarks
AWS Foundations 3.1 (CloudTrail in all regions), 3.2 (log file validation), 3.8 and 3.9 (S3 data events); Google Cloud Foundations 2.1 (audit logging configured); Azure Foundations 5.x (diagnostic settings and Activity Log retention).
SOC 2
CC7.2 (monitoring for anomalies) and CC7.3 (evaluating security events).
ISO/IEC 27001
A.8.15 Logging, A.8.16 Monitoring activities.
DORA
Art. 10 detection of anomalous activities; Art. 17 incident management.
NIS2
Art. 21(2)(b) incident handling, 21(2)(f) assessing effectiveness.
PCI DSS v4
Req. 10.2 (audit logs for all access), 10.3 (logs protected), 10.5 (retention).
NIST CSF 2.0
PR.PS-04 (log records generated), DE.CM-01 and DE.CM-09 (monitoring).
BSI C5
OPS (logging and monitoring of security events).
DNB Good Practice Information Security
Logging and monitoring.
How AKRIBOS handles it
AKRIBOS finds this during a read-only review of every connected account, project and subscription, shows the exact resource and setting behind the finding, and ranks it by the attack path it enables rather than in isolation. The fix is proposed as CLI commands or Terraform for you to review and approve, and the approval is recorded in the audit trail together with the compliance controls it satisfies.
Related issues
Storage bucket open to the internet
CriticalObject storage that anyone can list or read, usually from a permissive ACL, bucket policy or account-wide setting that was never switched on.
Read moreRoot or owner account without MFA
CriticalThe most privileged identity in the account protected by a password alone.
Read moreDatabase reachable from the internet
CriticalA managed database with a public address and a firewall that lets the world in.
Read moreAttackers don't wait for your next audit. Neither does AKRIBOS.
Connect AWS, Google Cloud or Azure and get your first review today.
