Secure your New Relic surface
Alert policy coverage, notification channels nobody reads, and agents missing from critical services. We don’t connect to New Relic to collect evidence for its own sake — we connect to secure it, and the compliance artefacts follow from that work.
Book a Demo[01] What This Surface Exposes
Where New Relic goes wrong
New Relic goes wrong at the destination: alert policies route to channels that nobody actually watches any more.
- Services monitored without any alert policy attached
- Notification channels routing to inboxes and channels nobody watches
- Agents absent from services that carry regulated data
- Data retention below investigation requirements
- User roles granting broad account administration
[02] What We Secure
What we watch, catch and fix on New Relic
On New Relic we verify that notification destinations are genuinely monitored and measure alert coverage per service against criticality.
- Alert policy coverage measured per service against criticality
- Notification destination verified as actually monitored
- Agent coverage reconciled against your service inventory
- Retention checked against requirement
- Role assignment reviewed
[03] Where It Lands
Where New Relic lands in your registers
Logging and alerting platforms enter the asset register as critical dependencies, since losing them blinds every detective control you own. Access reviews cover who can alter retention, silence alerts, or read logs containing personal data. The risk register carries what a monitoring gap actually means: an incident window you would not be able to reconstruct.
[04] How We Engage
On New Relic specifically
On New Relic, we attach alert policies to uncovered services and correct notification routing. Instrumentation rollout to unmonitored services we drive with your engineers.
Platform licence
Everything you need to find and fix it yourself, with no ceiling on the depth of the answer.
- Every connected tool monitored for misconfiguration and drift, with findings mapped to the assets and risks they affect
- Remediation guidance that tells you what is wrong and exactly how to fix it — however deep or awkward the issue is. We are engineers running a security company, so the answer is the real one, not a link to vendor documentation
- Assets, access reviews, and risk register populated from the tools themselves rather than from spreadsheets
- Unlimited integrations and unlimited users, with anything missing built within two weeks
Managed service
Every tool you connect through Konfirmity comes under our care, with our team doing the work.
- Continuous misconfiguration and drift monitoring across every connected tool, watched by our analysts rather than by a dashboard waiting for you
- Incident response led by us, with containment coordinated with your team
- Remediation performed directly wherever you have granted us the authority to act — and where we cannot act, we project-manage the fix to completion rather than handing you a ticket
- Decision support on the tools themselves: where something is failing you on capability or costing more than it returns, we will tell you, and help you replace it
[05] New Relic FAQs
What New Relic access does Konfirmity need?
Konfirmity needs a user key with read access to the NerdGraph API covering entities, alert policies, notification channels and users. That is enough to measure instrumentation coverage and alert routing.
How do you verify a notification channel works?
By checking it end to end rather than confirming it is configured. A channel pointing at a decommissioned Slack channel or an unmonitored shared inbox is configured correctly and delivers nothing, which is indistinguishable from working until an incident.
Datadog
Splunk
Amazon CloudWatch
Grafana
Elastic