The service may be configured to probe an endpoint from external provider-operated locations on a schedule and record whether it is reachable and responding.
Uptime Monitoring
CCC.Monitor.CP07
Related Threats
| ID | Title | Description |
|---|---|---|
| CCC.Monitor.TH02 | System Health is Exposed to Unauthorized Viewers | Dashboards, uptime results, and service level objective status may be shared beyond the intended audience through overly broad sharing settings or public links. Degraded or failing components are then visible to unauthorized viewers, who can target systems that are already in a weakened state or time activity to coincide with existing incidents. This impacts the confidentiality of operational information and the availability of the affected systems. |
| CCC.Monitor.TH03 | Monitoring Probes Overload the Monitored Target | Synthetic and uptime checks may be configured with excessive frequency, concurrency, or number of provider-operated locations, or their definitions may be modified to point at a different target. The probe traffic then consumes the capacity of the monitored endpoint from trusted provider address ranges that are typically exempt from rate limiting. This impacts the availability of the monitored system. |
| CCC.Monitor.TH04 | Monitoring Probes are Used to Reach Internal Systems | Synthetic and uptime checks run with an identity, network placement, and stored credentials that allow them to reach endpoints not otherwise exposed. If the check definition or its script can be modified, the check becomes a trusted path through which arbitrary requests are issued against internal systems and their responses are recorded. This impacts the confidentiality and integrity of the internal systems reached. |