Secure your Dynatrace surface
OneAgent coverage, alerting profile scope, and management zones that hide problems from the people who own them. We don’t connect to Dynatrace 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 Dynatrace goes wrong
Dynatrace goes wrong through narrow alerting profiles: filters tuned to reduce noise quietly filter out problems that should page someone.
- Hosts and services without OneAgent deployed
- Alerting profiles scoped so narrowly that real problems are filtered out
- Management zones restricting visibility in ways that leave owners blind
- Data retention below investigation requirement
- API tokens with broad scope
[02] What We Secure
What we watch, catch and fix on Dynatrace
On Dynatrace we review alerting profile scope against what should genuinely wake someone, and reconcile OneAgent coverage.
- Agent coverage reconciled against your asset register
- Alerting profile scope reviewed against what should actually page someone
- Management zone boundaries checked against ownership
- Retention verified
- Token scope and rotation tracked
[03] Where It Lands
Where Dynatrace 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 Dynatrace specifically
On Dynatrace, we correct alerting profiles and drive agent deployment. Management zone restructuring we plan with your platform team.
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] Dynatrace FAQs
What Dynatrace access does Konfirmity need?
Konfirmity needs an API token with read scopes for entities, problems, alerting profiles and settings. That covers agent coverage, alerting configuration and management zone structure.
Why do management zones matter?
Because they control who can see what, and a zone drawn too tightly leaves the team that owns a service unable to see its problems. That is an ownership failure disguised as an access control setting.
Datadog
Splunk
Amazon CloudWatch
Grafana
New Relic