Prometheus
Connect Prometheus to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Prometheus to collect observability evidence with automated compliance tests, switched on per workspace.
| Category | Observability |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Prometheus's guide | prometheus.io |
Connect with an API token
-
In Prometheus:
- Prometheus has no token issuer. To require credentials natively, add basic_auth_users to Prometheus's web configuration file with a username and a bcrypt-hashed password for Safeguard; enter that username and the plain password in Safeguard.
Where to find the other values:
- Server URL: The https address where your Prometheus server is reachable.
- Alertmanager URL (optional): The https address of your Alertmanager.
Prometheus's public documentation does not cover every step.
Prometheus's web config gives basic-auth users full access to the web server; it documents no read-only role and no native bearer tokens, so read-only enforcement needs a proxy, whose setup is outside Prometheus's docs.
Source: prometheus.io, checked 2026-10-07.
The permissions Safeguard needs:
read access through your proxy. -
On Compliance › Connectors, open Prometheus, click Connect, choose API token and fill in:
Field What to enter Server URL Required. Your own server: an https address reachable from the internet. Alertmanager URL (optional) Your own server: an https address reachable from the internet. Bearer token (optional) Stored encrypted and never shown again. Username (optional) — Password (optional) Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Prometheus and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | CC7.2 | 1 |
| ISO/IEC 27001 | Automated tests | A.8.16 | 1 |
| HIPAA Security Rule | Automated tests | 164.312(b) | 1 |
| PCI DSS | Automated tests | 10.4.1 | 1 |
| NIST CSF 2.0 | Automated tests | DE.CM-01 | 1 |
These tests are switched on per workspace by the Safeguard team.
Related
- Observability connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks