Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SCA overview: remove redundant content #27303

Merged
merged 2 commits into from
Jan 27, 2025
Merged

SCA overview: remove redundant content #27303

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6863651
Update _index.md
michaelcretzman Jan 24, 2025
0e1f365
Merge branch 'master' into mcretzman/SCA-remove-redundant-content
michaelcretzman Jan 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 1 addition & 22 deletions content/en/security/code_security/software_composition_analysis/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,15 +14,11 @@ Using Software Composition Analysis provides organizations with the following be
- Risk-based prioritization and remediation based on runtime detection of vulnerabilities
- Identification of malicious packages, end-of-life libraries, and library riskiness based on OpenSSF standards

### Static vulnerability detection in repositories
### Vulnerability detection in repositories
SCA supports scanning for libraries in the following languages and technologies:

{{< partial name="code_security/sca-getting-started.html" >}}


### Runtime vulnerability detection in services
{{< partial name="code_security/sca-getting-started.html" >}}

SCA can also detect vulnerable libraries running in your services based on your Datadog telemetry.

Runtime detection allows for risk-based prioritization of library vulnerabilities in your deployment environments.
Expand All @@ -31,8 +27,6 @@ Runtime detection allows for risk-based prioritization of library vulnerabilitie

### Library Catalog

{{< partial name="code_security/sca-getting-started.html" >}}

The Datadog SCA [Library Catalog][8] helps you understand the list of libraries and its versions that compose your application.

For each library version, you can assess how often it is used across your codebase and running in your services
Expand Down Expand Up @@ -106,21 +100,6 @@ The Datadog SCA [Library Inventory][8] helps you understand the list of librarie

With Datadog SCA spanning your software development lifecycle from code to production, it detects libraries throughout the lifecycle of an application and alerts you to vulnerabilities, risks, licenses, and more.


### Datadog severity score

Each vulnerability has a defined base severity score. To assist in prioritizing remediation, Datadog modifies the base CVSS score into the Datadog Severity Score by considering evidence of suspicious requests or attacks, the business sensitivity or internet exposure of the environment, and the risk of a successful exploit.

Four score modifiers may apply to a base score. Two are provided by runtime context:
- Vulnerability is in production
- Service affected by vulnerability is under attack

Two are provided by CVE context:
- Whether an exploit is available
- The exploitation probability

Datadog shows how the base CVSS score is adjusted to the Datadog Severity Score based on the factors above.

<!-- ### Remediation

The Vulnerability Explorer offers remediation recommendations for detected vulnerabilities. Recommendations enable you to change the status of a vulnerability, assign it to a team member for review, and create a Jira issue for tracking. They also include a collection of links and references to websites or information sources to help you understand the context behind each vulnerability. -->
Expand Down
Loading