Dynatrace Application Security

Name: Dynatrace Application Security
Brand: Dynatrace
Rating: 4.4 (1787 reviews)

Leader

Cloud done right.

Est 2005|Valuation $18.5B|Raised $2.1B

LinkedIn 413K|Website|Web traffic 1.3M|FTEs 5,200|HQ Boston, Massachusetts, US

MarketsApplication Security Testing (AST)

Dynatrace Application Security screenshot

Published May 16, 2026

01Common complaints

Primary need is CNAPP breadth rather than runtime application context
- If the primary requirement is comprehensive cloud posture management, identity and entitlement management, and infrastructure-as-code scanning within a single security-first platform, CNAPP vendors (for example Sysdig Secure, Wiz, Prisma Cloud) may be more appropriate.
Budget constraints or strict spend predictability
- Organizations that cannot accommodate potential enterprise minimums, multi-SKU expansion, or complex billing models should consider alternatives with simpler or free-tier pricing structures.
Preference for an integrated developer-first code security suite
- If the priority is developer-oriented SAST/Secrets/IaC workflows within one suite, dedicated AppSec tools or vendors with developer workflow integrations may be preferable.
Agent/instrumentation restrictions
- If organizational policy or architecture prevents deep runtime instrumentation, a lighter-weight agentless approach may be required.
Requirement for extensive independent security-module reviews prior to procurement
- If procurement policies mandate abundant third-party reviews focused specifically on the Application Security module, note that public review material is currently more aggregated under Dynatrace observability.

1. Primary need is CNAPP breadth rather than runtime application context - If the primary requirement is comprehensive cloud posture management, identity and entitlement management, and infrastructure-as-code scanning within a single security-first platform, CNAPP vendors (for example Sysdig Secure, Wiz, Prisma Cloud) may be more appropriate. 2. Budget constraints or strict spend predictability - Organizations that cannot accommodate potential enterprise minimums, multi-SKU expansion, or complex billing models should consider alternatives with simpler or free-tier pricing structures. 3. Preference for an integrated developer-first code security suite - If the priority is developer-oriented SAST/Secrets/IaC workflows within one suite, dedicated AppSec tools or vendors with developer workflow integrations may be preferable. 4. Agent/instrumentation restrictions - If organizational policy or architecture prevents deep runtime instrumentation, a lighter-weight agentless approach may be required. 5. Requirement for extensive independent security-module reviews prior to procurement - If procurement policies mandate abundant third-party reviews focused specifically on the Application Security module, note that public review material is currently more aggregated under Dynatrace observability.

Deal disqualifiers

Very small teams or organizations seeking low-cost, minimal-scope vulnerability scanning.
Organizations that prioritize broad CNAPP coverage (CSPM/CIEM/IaC) over runtime observability and correlation.
Environments where OneAgent instrumentation is prohibited or infeasible.
Buying policies that require extensive independent third-party validation specifically for Application Security prior to purchase; such reviews are less common relative to established AppSec/CNAPP vendors.

- Very small teams or organizations seeking low-cost, minimal-scope vulnerability scanning. - Organizations that prioritize broad CNAPP coverage (CSPM/CIEM/IaC) over runtime observability and correlation. - Environments where OneAgent instrumentation is prohibited or infeasible. - Buying policies that require extensive independent third-party validation specifically for Application Security prior to purchase; such reviews are less common relative to established AppSec/CNAPP vendors.

Limitations evidenced in sources

Module-specific review scarcity: third-party reviews tend to address Dynatrace overall, which complicates validation of false-positive rates and performance overhead specific to the Application Security module.
Complexity and learning curve: recurring feedback highlights a need for training and potential usability challenges.
Pricing and contract ambiguity: public list prices exist, but community reports of minimums and commitments represent a procurement risk to clarify.

- Module-specific review scarcity: third-party reviews tend to address Dynatrace overall, which complicates validation of false-positive rates and performance overhead specific to the Application Security module. - Complexity and learning curve: recurring feedback highlights a need for training and potential usability challenges. - Pricing and contract ambiguity: public list prices exist, but community reports of minimums and commitments represent a procurement risk to clarify.

Vendor-acknowledged / documented technical constraints

Application Security capabilities rely on OneAgent runtime instrumentation and are subject to the platform’s licensing models (for example DPS GiB-hour billing or classic ASUs).

02Why they buy

Differentiators (evidence-aligned)

Runtime context for vulnerability prioritization: vendor documentation indicates prioritization based on libraries and execution evidence to reduce noise from non-executed or non-exposed vulnerabilities.
Configurable runtime blocking (RAP): documentation describes detection and configurable blocking for specified attack patterns.
Integration with the observable entity model: security findings are correlated with topology, traces, and service context used by the rest of the Dynatrace platform.

- Runtime context for vulnerability prioritization: vendor documentation indicates prioritization based on libraries and execution evidence to reduce noise from non-executed or non-exposed vulnerabilities. - Configurable runtime blocking (RAP): documentation describes detection and configurable blocking for specified attack patterns. - Integration with the observable entity model: security findings are correlated with topology, traces, and service context used by the rest of the Dynatrace platform.

Where competitors have clear advantages

Broader security portfolio: some competitors provide an extensive set of security SKUs and broader cloud posture coverage.
Security-first posture breadth: CNAPP vendors may provide more comprehensive CSPM/CIEM/IaC capabilities.

03Field reports

What reviews are available (and what’s missing)

Gartner Peer Insights

The Dynatrace product review pages include examples where reviewers report monitoring limitations and compatibility issues requiring architectural changes. These observations relate primarily to observability and agent compatibility.

TrustRadius

TrustRadius provides an overall Dynatrace rating and many reviews. Common themes identified across reviews include:

Pros: deep visibility, drill-down capabilities, automation features.
Cons: learning curve, navigation complexity, retention limits depending on plan, occasional performance or version-related issues.

A representative paraphrase of a TrustRadius comment: a reviewer described Dynatrace as versatile across monitoring use cases but noted a significant learning curve for dashboard navigation.

Reddit / community discussions (more candid, less structured)

Community threads reflect polarized views:

Some users reported a difficult experience after product changes and criticized usability.
Other users described automated data collection as reducing ongoing operational tasks but noted difficulties with alert routing and ownership mapping.
Cost concerns appear frequently, with users expressing a range of perspectives on relative cost compared with alternatives.

Most review platforms (review marketplaces and analyst review sites) aggregate feedback for Dynatrace as a whole (observability/APM) rather than for the Application Security SKUs specifically. This aggregation limits the ability to isolate sentiment about the security module. #### Gartner Peer Insights - The Dynatrace product review pages include examples where reviewers report monitoring limitations and compatibility issues requiring architectural changes. These observations relate primarily to observability and agent compatibility. #### TrustRadius TrustRadius provides an overall Dynatrace rating and many reviews. Common themes identified across reviews include: - Pros: deep visibility, drill-down capabilities, automation features. - Cons: learning curve, navigation complexity, retention limits depending on plan, occasional performance or version-related issues. A representative paraphrase of a TrustRadius comment: a reviewer described Dynatrace as versatile across monitoring use cases but noted a significant learning curve for dashboard navigation. #### Reddit / community discussions (more candid, less structured) Community threads reflect polarized views: - Some users reported a difficult experience after product changes and criticized usability. - Other users described automated data collection as reducing ongoing operational tasks but noted difficulties with alert routing and ownership mapping. - Cost concerns appear frequently, with users expressing a range of perspectives on relative cost compared with alternatives.

Why customers choose Dynatrace (themes)

Single agent architecture (OneAgent) that provides automatic discovery and instrumentation.
Dependency mapping and root-cause analysis capabilities derived from topology and traces.
Desire to correlate runtime security findings with existing observability data for incident triage and remediation prioritization.

Why some customers don’t choose it / leave (themes)

Perceived total cost and procurement complexity, including possible enterprise-level minimums or multi-SKU management.
Learning curve and usability concerns, including the need to learn platform-specific query language and navigation patterns.
Potential mismatch for smaller organizations where the breadth and cost of the platform may exceed needs.

Vendor-published testimonial example

Critical evaluation:

The testimonial is vendor-selected and lacks disclosed methodology.
No independent or quantified metrics (for example measured MTTR reduction, counts of vulnerabilities remediated, or time-to-patch) are provided in the testimonial.

A vendor-published quote attributed to an enterprise customer (Auto Club Group) states that enabling the module helped identify vulnerabilities and monitor security posture during the Log4j/Log4Shell incident. Critical evaluation: - The testimonial is vendor-selected and lacks disclosed methodology. - No independent or quantified metrics (for example measured MTTR reduction, counts of vulnerabilities remediated, or time-to-patch) are provided in the testimonial.

Press-release style proof points

Vendor press releases describe the introduction of real-time attack detection and blocking capabilities, with examples referencing historic vulnerabilities such as Log4Shell.

Critical evaluation:

Press releases describe capabilities and timelines but do not provide independent testing results, false-positive rates, or measured performance overhead.
Buyers should request performance and detection metrics, ideally under representative workloads, and request third-party validation where available.

Vendor press releases describe the introduction of real-time attack detection and blocking capabilities, with examples referencing historic vulnerabilities such as Log4Shell. Critical evaluation: - Press releases describe capabilities and timelines but do not provide independent testing results, false-positive rates, or measured performance overhead. - Buyers should request performance and detection metrics, ideally under representative workloads, and request third-party validation where available.

04Best fit

Company size

Typical fit: mid-market to large organizations where centralized platform tooling and dedicated SRE/observability resources exist.

Industries

Common fits include financial services, insurance, telecommunications, retail, SaaS, and public sector organizations where uptime and incident response capabilities are priorities.

Roles / personas

Buyers: CISO, Head of AppSec, VP Engineering, Head of Platform/SRE, Observability lead.
Users: AppSec engineers, SRE/on-call engineers, developers, incident responders.

Pain points the product addresses

High volumes of vulnerability findings with low signal-to-noise; need for runtime evidence to prioritize remediation.
Difficulty linking vulnerabilities to specific services, real user impact, and production exposure.
Requirement to detect and contain certain exploit attempts without deploying separate runtime protection tooling.

05The pitch

What the product does (core value proposition)

Dynatrace Application Security is a runtime-focused application security capability integrated into the broader Dynatrace observability platform. It provides the following functional areas:

Runtime Vulnerability Analytics (RVA): identifies and prioritizes first-party and third-party vulnerabilities based on runtime evidence of libraries and execution paths.
Runtime Application Protection (RAP): detects and can be configured to block certain exploitation attempts (RASP-like functionality) for specific attack classes (for example SQL injection, command injection, JNDI injection, SSRF) using Dynatrace OneAgent runtime instrumentation.
Security Posture Management (SPM): a posture/compliance-oriented SKU within Dynatrace’s security offering intended to surface misconfigurations and compliance evidence; this SKU is distinct from runtime vulnerability detection and protection.

Dynatrace describes the module as integrated runtime security that is unified with topology, tracing, and an AI-assisted triage capability (branded as "Davis") to reduce alert volume and accelerate triage workflows. This characterization reflects vendor positioning.

Note: Most independent user commentary discusses Dynatrace as a whole (observability/APM) rather than the Application Security SKUs specifically, which makes it more difficult to validate security-module claims from user reviews alone.

Dynatrace Application Security is a runtime-focused application security capability integrated into the broader Dynatrace observability platform. It provides the following functional areas: - Runtime Vulnerability Analytics (RVA): identifies and prioritizes first-party and third-party vulnerabilities based on runtime evidence of libraries and execution paths. - Runtime Application Protection (RAP): detects and can be configured to block certain exploitation attempts (RASP-like functionality) for specific attack classes (for example SQL injection, command injection, JNDI injection, SSRF) using Dynatrace OneAgent runtime instrumentation. - Security Posture Management (SPM): a posture/compliance-oriented SKU within Dynatrace’s security offering intended to surface misconfigurations and compliance evidence; this SKU is distinct from runtime vulnerability detection and protection. Dynatrace describes the module as integrated runtime security that is unified with topology, tracing, and an AI-assisted triage capability (branded as "Davis") to reduce alert volume and accelerate triage workflows. This characterization reflects vendor positioning. Note: Most independent user commentary discusses Dynatrace as a whole (observability/APM) rather than the Application Security SKUs specifically, which makes it more difficult to validate security-module claims from user reviews alone.

Target market and market positioning

Primary target: mid-market to enterprise organizations with hybrid/multi-cloud estates, Kubernetes/microservices deployments, and a preference for combining observability and security workflows.
Positioning: a security capability that operates at the intersection of runtime detection/protection and vulnerability management, leveraging observability context for prioritization and investigation.

Get a comprehensive analysis of Dynatrace Application Security including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →