CIS Safeguard 16.5: Use Up-to-Date and Trusted Third-Party Software Components

CIS Safeguard 16.5: Use Up-to-Date and Trusted Third-Party Software Components

By Steve Gold
Posted in Security
On November 17, 2026

In Top Gun: Maverick, the mission briefing makes one thing clear: flying an aging F-14 against fifth-generation fighters is not a challenge, it is a death sentence. The problem is not the pilots. The problem is the hardware. The F-14 cannot maneuver the way modern threats do. It cannot respond fast enough. It is a liability dressed up as an asset. Outdated third-party software components in your application stack work the same way: they might look like they are doing the job, but they cannot handle what is coming at them.

What Is Use Up-to-Date and Trusted Third-Party Software Components?

Building on Safeguard 16.4, which says to know what third-party components you are running, Safeguard 16.5 says to keep them current and choose them wisely in the first place.

The official CIS text reads:

"Use up-to-date and trusted third-party software components. When possible, choose established and proven components developed and actively maintained by a trusted community or entity."

Two requirements here. First, keep your components updated. Second, be selective about which ones you adopt.

Why It Matters

A library with known, unpatched vulnerabilities is not a problem waiting to happen. It is a problem happening right now, quietly, until someone decides to exploit it.

Attackers actively scan for systems running vulnerable component versions. They do not need zero-days when they have a list of publicly disclosed CVEs and a straightforward way to check which version your application is running. Tools like Shodan and common vulnerability scanners make this trivial.

Abandoned libraries are a specific category of risk. When a maintainer stops responding to security disclosures, vulnerabilities accumulate without patches. Any organization still running that component is holding the bag. The colors and event-stream incidents in the npm ecosystem are historical examples. There will be more.

Software supply chain attacks have added another layer. A component that is actively maintained can still be compromised. Threat actors have poisoned npm packages, inserted malicious code into PyPI uploads, and taken over dormant maintainer accounts to push malicious updates. Trusting a maintained component does not mean trusting it blindly.

Key Details or How It Works

  • Outdated is not the same as old: A component can be years old and still current if it is actively maintained. The issue is whether the version you are running has unpatched vulnerabilities, not how long the library has existed.
  • CVE databases are the ground truth: The National Vulnerability Database (NVD) and OSV.dev publish known vulnerabilities tied to specific package versions. Your inventory from Safeguard 16.4 only has value if you are regularly checking it against these sources.
  • Software composition analysis (SCA) tools automate this: Tools like Snyk, Grype, OWASP Dependency-Check, and Trivy scan your dependencies and flag versions with known CVEs. This should run on every build, not as a quarterly exercise.
  • Transitive dependencies carry the same risk: You may keep your direct dependencies updated while a nested dependency two levels down sits at a version with a critical CVE. SCA tools need to scan the full dependency tree, not just the top level.
  • "Trusted" requires evaluation, not assumption: Check maintenance activity, response time to security disclosures, contributor diversity, and whether there is an entity with accountability behind the project. Popularity on GitHub is not a substitute for due diligence.
  • End-of-life components need a plan: When a library reaches end-of-life, it stops receiving security patches. Running it is a policy decision that should be documented, time-boxed, and paired with compensating controls until a replacement is in place.
  • Version pinning has limits: Pinning versions for stability is reasonable. Pinning them indefinitely while vulnerabilities accumulate is not. You need a defined cadence for reviewing and applying updates.

How to Implement Use Up-to-Date and Trusted Third-Party Software Components

  1. Integrate SCA scanning into your CI/CD pipeline. Every build should scan the full dependency tree against known vulnerability databases. Configure pipeline gates to fail or alert on critical and high-severity findings. This is not a once-a-quarter check.
  2. Establish a patch SLA for third-party components. Define how quickly critical CVEs and high-severity findings must be remediated. Thirty days for critical is a common baseline. Document the policy, enforce it with pipeline controls, and track exceptions formally.
  3. Evaluate components before adoption. Before pulling in a new library, check its maintenance status, last commit date, open issue queue, and security disclosure history. A quick review at adoption is considerably cheaper than an emergency patching sprint later.
  4. Monitor for newly disclosed vulnerabilities continuously. Subscribe to NVD feeds or use tooling that alerts you when a new CVE is published against a component you are running. A component that passed your last scan may have a critical finding published today.
  5. Build a defined process for end-of-life dependencies. When a library reaches EOL, trigger a workflow: identify a maintained replacement, assign ownership, set a migration deadline, and document compensating controls in the meantime. Do not let EOL components sit in production without a plan.
  6. Review high-risk components periodically. The landscape changes. A component that was well-maintained and trusted two years ago may have shifted. Include a periodic review of critical dependencies as part of your application security program.

Final Thoughts

Maverick's team completed the mission. But they did it by adapting fast and accepting that the hardware they were flying was not built for what they were flying into. They got lucky. Your applications are not going to get lucky when they are built on outdated, unmaintained components with published CVEs and no patches coming. The F-14 in your application stack is not charming. It is a vulnerability with a countdown clock.

Resources

Here is a link to the Policy Templates provided free of charge from the fine folks at the Center for Internet Security.

Looking for even more detail? Here you go. If this still does not satisfy your curiosity, DM me.

Official CIS Text

CIS Control 16: Application Software Security Manage the security life cycle of in-house developed, hosted, or acquired software to prevent, detect, and remediate security weaknesses before they can impact the enterprise.

CIS Safeguard 16.5: Use Up-to-Date and Trusted Third-Party Software Components Use up-to-date and trusted third-party software components. When possible, choose established and proven components developed and actively maintained by a trusted community or entity.

Shameless Marketing Information

Gotham Technology Group helps organizations build application security programs that include software composition analysis, dependency management, and supply chain risk controls. If your development pipeline is not scanning for vulnerable components today, that is a gap worth closing.

Steve Gold

Steve Gold

Steve Gold is the Cybersecurity Practice Director at Gotham Technology Group (Gotham). He is responsible for providing the vision and thought leadership to expand Gotham’s legacy of success and build a world-class cybersecurity practice. He works closely with Gotham’s customers, industry partners, and subject matter experts to develop relevant solutions for Gotham’s clients and prospects.

Prior to joining Gotham, Steve worked with the Center for Internet Security (CIS), where he expanded the global reach, revenue, and impact of the CIS Benchmarks, CIS Controls, and CIS Hardened Images. He led the efforts to promote the CIS portfolio of low-cost and no-cost cybersecurity products and services that help private and public organizations stay secure in the connected world. He grew a team of security specialists from 12 to over 40 to assist organizations with implementing security best practices in their continual journey of cybersecurity maturity.

During his more than 20-year career, Steve led teams responsible for developing and implementing technology solutions at some of the industry’s most recognized companies such as Varonis, VMware, Dell & Wyse Technology

Steve is a frequent speaker/moderator at industry conferences and webinars, covering a wide array of information security topics. He resides and works remotely in Baltimore, MD.