Skip to content

Commit 3abb086

Browse files
gorkavicenteclaude
andauthored
[Code Security] Add Public exploit sources section to SCA docs (#35797)
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
1 parent 8d092a3 commit 3abb086

File tree

1 file changed

+6
-0
lines changed
  • content/en/security/code_security/software_composition_analysis

1 file changed

+6
-0
lines changed

content/en/security/code_security/software_composition_analysis/_index.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,12 @@ Datadog SCA draws from multiple public and private sources to build a curated pr
4848

4949
Datadog uses these sources to identify known vulnerabilities, malicious packages, and emerging supply chain threats across supported ecosystems. There is a maximum of 1 hour between when a new vulnerability is published and when it appears in Datadog, with emerging vulnerabilities typically appearing in Datadog within minutes.
5050

51+
## Public exploit sources
52+
53+
Datadog identifies whether a vulnerability has a known public exploit by aggregating data from multiple public sources, including CISA (Known Exploited Vulnerabilities Catalog), Exploit-DB, NIST (National Vulnerability Database), and GitHub (public exploit references).
54+
55+
When Datadog identifies a public exploit for a vulnerability from any of these sources, it flags the finding to help you prioritize remediation.
56+
5157
## Key capabilities
5258

5359
### Review and prioritize vulnerabilities

0 commit comments

Comments
 (0)