CCC Audit Logging Threats
Threats for Audit Logging technologies, as defined by the FINOS Common Cloud Controls project.
- ID
- CCC.AUDITLOG.TH
- Version
- v2026.06-rc4
- Gemara version
- v1.2.0
- Author
- FINOS Common Cloud Controls
Observability
The Observability group covers entries related to logging, monitoring, metrics, alerting, and event publication. This includes audit trail integrity, enumeration detection, and protection against tampering or unauthorized access to operational telemetry.
CCC.AUDITLOG.TH01 Insufficient Audit Logs
If security critical audit events are not logged then it increases the difficulty to detect threats and perform post incident analysis.
Capabilities
- CCC.Core.Capabilities
- CCC.Core.CP03
- CCC.Core.CP10
- CCC.Core.Capabilities
CCC.AUDITLOG.TH02 Log Ingestion Latency
Large spikes or sustained delays in log ingestion may degrade the timeliness and completeness of security telemetry. This can increase the time required to detect and investigate threats, potentially impacting incident response effectiveness.
Capabilities
- CCC.Core.Capabilities
- CCC.Core.CP03
- CCC.Core.CP10
- CCC.Core.Capabilities
CCC.AUDITLOG.TH03 Sensitive Data Logged
Sensitive information such as passwords, environment variables, or personally identifiable information (PII) may be included in audit logs due to a number of reasons such as; end user human error, developers not sanitizing fields or maliciously by a threat actor attempting to exfil data. This can lead to unauthorized disclosure if logs are accessed by unintended parties or forwarded to external systems.
Capabilities
- CCC.AuditLog.Capabilities
- CCC.AuditLog.CP03 — Sink
- CCC.AuditLog.CP08 — External Sink
- CCC.Core.Capabilities
- CCC.Core.CP03
- CCC.Core.CP10
- CCC.AuditLog.Capabilities
CCC.AUDITLOG.TH05 Logging Evasion via violating size constraints
An attacker can evade detection by intentionally crafting input that violates the size constraints of a clouds audit logging mechanism. Many systems impose a maximum size limit on individual log entries. By performing an action with oversized data such as whitespace or Unicode injection, the resulting log event, which often includes the offending data, exceeds this limit, which often is redacted in the audit logs.
Capabilities
- CCC.Core.Capabilities
- CCC.Core.CP03
- CCC.Core.CP10
- CCC.Core.Capabilities
Ingestion
The Ingestion group covers entries related to how a service receives or retrieves data, inputs, or commands for processing. This includes both active (pull-based) and passive (push-based) ingestion patterns.
CCC.AUDITLOG.TH04 Insufficient encoding of audit logs
User-supplied data such as scripts, control characters, escape sequences, or code fragments may be written to audit logs without proper encoding or sanitization. This can result in malformed or unexpected log entries that could disrupt or compromise systems that process or display these logs, including log viewers or downstream services.
Capabilities
- CCC.AuditLog.Capabilities
- CCC.AuditLog.CP03 — Sink
- CCC.AuditLog.CP08 — External Sink
- CCC.Core.Capabilities
- CCC.Core.CP03
- CCC.Core.CP10
- CCC.AuditLog.Capabilities