3.2.2 Ensure packages are automatically scanned for known vulnerabilities
ID |
cis_sscs/package_scan_vuln |
Severity |
high |
Category |
dependencies/validate_packages |
Levels |
|
Optional |
true |
Tags |
sca, security, slsa-4, supply-chain |
Description
Automatically scan every package for vulnerabilities.
The vulnerability scanners to be considered may be configured for this checkpoint.
Rationale
Automatic scanning for vulnerabilities detects known vulnerabilities in packages and dependencies in use, allowing faster patching when one is found. Such vulnerabilities can lead to a massive breach if not handled as fast as possible, as attackers will also know about those vulnerabilities and swiftly try to take advantage of them. Scanning packages regularly for vulnerabilities can also verify usage compliance with the organization’s security policy.
Gathering the dependencies graph and analyzing each dependency for vulnerabilities and other issues is named "Software Composition Analysis" or SCA. Tools that automate such analysis are called SCA tools.
| A project compliant with this check typically is also compliant with the 3.2.3 check "Ensure packages are automatically scanned for license implications", as most SCA tools analyze vulnerabilities, license issues and obsolescence. |