A vulnerability in a third-party library makes upgrading the dependency a security requirement. Keep the technology stack current, especially library and framework versions, to address vulnerabilities. section 5.3.2 section 5.3.3
Choose the upgrade path based on the change required:
- When no code changes are needed, the security team can upgrade the library, test the change, and deploy the application in less than a day. section 5.3.3
- When code changes are required, make large upgrades incrementally, one team at a time. section 5.3.3

















