Am new to Dynatrace’s Application Security capabilities, so pardon me if my question sounds trivial: the following is an excerpt from Dynatrace Application Security detects and blocks attacks automatically in real-time which hints that Dynatrace performs source/sink tracking or taint propagation to identify injection vulnerabilities.
With transaction analysis and code-level insights, Dynatrace detects whenever user-generated inputs are sent to vulnerable application components without sanitization. With this approach, you can identify SQL injection attacks, command injection attacks, and JDNI attacks like log4shell or the H2 vulnerability.
This means that Dynatrace doesn’t rely on vulnerability databases but is rather able to identify and block such attacks automatically even if they are exploiting unknown weaknesses. A perfect OWASP benchmark score for injection attacks—100% accuracy and zero false positives—impressively proves the precision of our approach.
The examples I’ve come across of Application Security issues Dynatrace is able to identify seem to rely on vulnerability databases such as synk to identify or component vulnerabilities, or am I missing something? I’m not interested in Dynatrace flagging component vulnerabilities without proof-of-exploitability: that is already covered by other SCA tools.
Can someone who’s experienced with Dynatrace Application Security capabilities confirm if it has source/sink tracking and/or taint propagation capabilities that is capable of detecting and preventing injection attacks that are introduced with custom code without code change?