diff --git a/content/en/security/code_security/software_composition_analysis/setup_runtime/_index.md b/content/en/security/code_security/software_composition_analysis/setup_runtime/_index.md index 76640456d87..b39a41ebaca 100644 --- a/content/en/security/code_security/software_composition_analysis/setup_runtime/_index.md +++ b/content/en/security/code_security/software_composition_analysis/setup_runtime/_index.md @@ -10,8 +10,9 @@ SCA can detect vulnerabilities that affect open source libraries running in your Before setting up runtime detection, ensure the following prerequisites are met: 1. **Datadog Agent Installation:** The Datadog Agent is installed and configured for your application's operating system or container, cloud, or virtual environment. -2. **Datadog APM Configuration:** Datadog APM is configured for your application or service, and web traces (`type:web`) are being received by Datadog. -3. **Supported SDK:** The Datadog SDK used by your application or service supports Software Composition Analysis capabilities for the language of your application or service. For more details, refer to the [Library Compatibility][2] page. +2. **Supported SDK:** The Datadog SDK used by your application or service supports Software Composition Analysis capabilities for the language of your application or service. For more details, refer to the [Library Compatibility][2] page. + +
The Datadog Agent and SDK are the only requirements for SCA. APM tracing and Infrastructure Monitoring are not required; SCA reports findings independently of both. To disable APM or Infrastructure Monitoring, see Disable APM and Infrastructure Monitoring. If APM is disabled, expect some APM intake costs to support SCA features (for example, security traces and spans).
## Software Composition Analysis enablement types