CCC Monitoring Threats
Threats for Monitoring technologies, as defined by the FINOS Common Cloud Controls project.
- ID
- CCC.Monitor.TH
- Version
- v2026.06-rc3
- 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.Monitor.TH01 Capture Personal Identifiable Information
Unauthorised viewers may get access to PII if it is incorrectly collected by monitoring systems through metrics or tracing.
Capabilities
- CCC.Monitoring.Capabilities
- CCC.Monitoring.CP01 — Metric collection
- CCC.Monitoring.CP02 — Tracing
- CCC.Monitoring.CP08 — Application Performance Monitoring (APM)
- CCC.Monitoring.CP09 — Dashboard
- CCC.Monitoring.CP11 — Integration with Third-Party Tools
- CCC.Monitoring.Capabilities
CCC.Monitor.TH02 Health Checks Used to Identify Attack Targets
Health Checks are used to inform those responsible for maintaining a system that there is a problem, but if that information gets into the hands of a malicious actor, it can be used to target already problematic systems and mask malicious activity.
Capabilities
- CCC.Monitoring.Capabilities
- CCC.Monitoring.CP04 — Health Checks
- CCC.Monitoring.Capabilities
Resource Management
The Resource Management group covers entries related to the lifecycle, configuration, and operational integrity of cloud resources. This includes resource exhaustion, tag manipulation, version rollback, scaling, and cost management.
CCC.Monitor.TH03 External Monitoring DoS
If an external monitoring service is compromised, it can act as a host for instigating denial of service attacks on internal system which otherwise may not be protected against this form of attack.
Capabilities
- CCC.Monitoring.Capabilities
- CCC.Monitoring.CP06 — Synthetic Monitoring
- CCC.Monitoring.Capabilities
CCC.Monitor.TH06 Cost Exhaustion Through Tampered Alerts or Metrics Collection
Monitoring systems are expected to generate traffic, but it a malicious actor were to change alerts that were being fired at an API which charged per requests or generate large volumes of metric data which would then need to be stored and processed, or even triggering resource scaling, this would cause an increase in cloud bill.
Capabilities
- CCC.Monitoring.Capabilities
- CCC.Monitoring.CP01 — Metric collection
- CCC.Monitoring.CP11 — Integration with Third-Party Tools
- CCC.Monitoring.Capabilities
Access Control
The Access Control group covers entries related to authentication, authorization, and trust perimeter enforcement. This includes multi-factor authentication, least privilege access, network access rules, and prevention of unauthorized access or reconnaissance.
CCC.Monitor.TH04 External Monitoring Access
If an external monitoring system is compromised, it acts as a trusted external remote service and can then access internal services which would otherwise not be accessible directly.
Capabilities
- CCC.Monitoring.Capabilities
- CCC.Monitoring.CP06 — Synthetic Monitoring
- CCC.Monitoring.Capabilities
Data Resilience
The Data Resilience group covers entries related to ensuring data availability, integrity, and sovereignty across its lifecycle. This includes replication, backup, recovery, region restrictions, and protection against data loss or corruption.
CCC.Monitor.TH05 Data Exfiltration Through Tampered Metrics
If a malicious actor is able to make changes to the metrics being collected, it could be used to encrypt and or compress sensitive data and bypass controls preventing exfiltration. The data can then be staged in the monitoring system and exfiltrated in bulk at a later point in time
Capabilities
- CCC.Monitoring.Capabilities
- CCC.Monitoring.CP01 — Metric collection
- CCC.Monitoring.CP11 — Integration with Third-Party Tools
- CCC.Monitoring.Capabilities
Compute
The Compute group covers entries related to processing, execution, and runtime infrastructure. This includes CPU, memory, storage allocation, network ports, command-line interfaces, and elastic scaling.
CCC.Monitor.TH07 Trigger Malicious Code
If a malicious actor is able to create new triggers, they would be able to use valid metric data to trigger malicious actions and re-compromise a newly replaced container or compute instance.
Capabilities
- CCC.Monitoring.Capabilities
- CCC.Monitoring.CP01 — Metric collection
- CCC.Monitoring.CP10 — Triggering
- CCC.Monitoring.CP11 — Integration with Third-Party Tools
- CCC.Monitoring.Capabilities