Ensure that only explicitly selected metrics, dimensions, and trace attributes are collected, so that sensitive data is neither captured in telemetry nor carried out through it.
Restrict Telemetry to Approved Fields
CCC.Monitor.CN07 · Observability
Related Capabilities
| ID | Title | Description |
|---|---|---|
| CCC.Monitor.CP01 | Custom Metric Ingestion | The service can receive user-defined, numeric time-series data points pushed by applications or external systems through its API, in addition to the metrics it collects automatically from provider resources. |
| CCC.Monitor.CP02 | Distributed Tracing | The service may be configured to collect traces that link a single request to the resulting operations in downstream components and external systems, providing an end-to-end view of a transaction. |
| CCC.Monitor.CP08 | Application Performance Monitoring | The service may be configured to collect application-level telemetry such as request latency, error rates, and dependency calls through instrumentation, in order to monitor performance and user experience. |
| CCC.Monitor.CP09 | Dashboards | The service can present metrics, alerts, service level objectives, and uptime results in user-defined visual dashboards that may be shared with other users. |
| CCC.Monitor.CP11 | Integration with External Tools | The service may be configured to forward alerts, notifications, and metric data to external systems such as incident management, ticketing, or third-party observability platforms. |
| CCC.Monitor.CP12 | Agent-Based Telemetry Collection | The service can collect metrics and traces from compute instances through a provider-supplied agent that runs on the instance and authenticates to the service using the instance identity or a configured credential. |
Related Threats
| ID | Title | Description |
|---|---|---|
| CCC.Monitor.TH01 | Sensitive Data is Captured in Telemetry | Metric dimensions, trace attributes, application telemetry, or agent-collected data may include personal or otherwise sensitive information when instrumentation is not configured to exclude it. The data is then stored, shown on dashboards, and forwarded to external systems with the access controls of the monitoring service rather than those of the originating system. This impacts the confidentiality of the captured data. |
| CCC.Monitor.TH05 | Telemetry is Used as a Data Exfiltration Channel | Custom metric values and dimensions, trace attributes, and agent-collected fields may be populated with encoded sensitive data by a compromised workload. The data is accepted as ordinary telemetry, staged in the monitoring service, and forwarded to external systems through configured integrations, bypassing controls applied to the workload's own network egress. This impacts the confidentiality of the exfiltrated data. |
Assessment Requirements
| ID | Text | Applicability |
|---|---|---|
| CCC.Monitor.CN07.AR01 | When agent-based telemetry collection is configured, the agent configuration MUST specify an explicit allow-list of the metrics and dimensions to collect. | tlp-clear, tlp-green, tlp-amber, tlp-red |
| CCC.Monitor.CN07.AR02 | When trace collection is configured, request and response payloads MUST NOT be recorded as trace attributes. | tlp-clear, tlp-green, tlp-amber, tlp-red |