Give your developers a clear foundation for dependency use: decide which packages can enter development, then keep visibility into what your applications already use.
Malicious packages surged 9x in 2024, a reason to evaluate package admission separately from scanning for known vulnerabilities.
Veracode Package Firewall evaluates packages before they enter your development environment. It supports policy-based blocking and logs package installations, giving your team concrete controls and records to evaluate.
Package Firewall includes 20+ pre-built policies across license, vulnerability, and provenance domains, giving your team a starting point for defining admission rules.
For example, your team could establish a package-age policy that restricts newly published packages. The policy choice should reflect your risk tolerance and development needs, not become a blanket substitute for judgment.
Package admission complements software composition analysis (SCA). Veracode SCA identifies known vulnerability and license risk in dependencies already in use. Software Supply Chain Intelligence (SSCI) supplies intelligence on emerging package threats.
As you evaluate admission controls, consider where policies fit, what developers experience when a package is restricted, and how your organization will handle exceptions. Agree on those practices with development before enforcement becomes a daily dependency.
The Package Firewall datasheet explains its package evaluation, policy controls, and installation logging so you can assess the fit.
No comments:
Post a Comment