New Relic
Connect New Relic to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect New Relic 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 |
| New Relic's guide | docs.newrelic.com |
Connect with an API token
-
In New Relic:
- Sign in as the New Relic user the key should belong to (a user key is tied to a specific user and can query any account that user has been granted access to).
- Go to one.newrelic.com/api-keys (EU: one.eu.newrelic.com/api-keys; JP: one.jp.newrelic.com/api-keys).
- Click Create a key in the top-right corner, enter a key name, select User as the Key type, add an optional description, and click Save.
- Copy the full key now. After creation the API Keys UI shows only the first 8 characters; to get the full key later you must query it with NerdGraph.
Where to find the other values:
- Account ID: User menu › Administration › Access management › Accounts lists account IDs (or use the account selector dropdown).
- Region: US if you use one.newrelic.com, EU if you use one.eu.newrelic.com.
New Relic shows the secret only once, so copy it before you leave the page.
A user key is tied to one user, cannot be transferred, and can query any account that user can access. Setting up the read-only role for that user was not covered on the fetched pages.
Source: docs.newrelic.com, docs.newrelic.com, checked 2026-10-07.
The permissions Safeguard needs:
read-only: user management, alerts, data management. -
On Compliance › Connectors, open New Relic, click Connect, choose API token and fill in:
Field What to enter User key Required. Stored encrypted and never shown again. Account ID Required. Region Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read New Relic 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 | CC6.2, CC6.3, CC7.2 | 4 |
| ISO/IEC 27001 | Automated tests | A.5.16, A.5.18, A.6.5, A.8.15, A.8.16 | 4 |
| HIPAA Security Rule | Automated tests | 164.308(a)(3), 164.308(a)(4), 164.312(b) | 4 |
| PCI DSS | Automated tests | 7.2.4, 8.2.5, 10.4.1, 10.5.1 | 4 |
| NIST CSF 2.0 | Automated tests | DE.CM-01, PR.AA-01, PR.AA-05, PR.PS-04 | 4 |
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