Course contentsShow
← Security
Lesson 2460 of 3,05247. Vulnerability ManagementFree lesson

Third-Party and Application Patching

Managing patches for non-OS software including browsers, plugins, and enterprise applications.

Third-Party and Application Patching

What you'll learn: How to manage patches for non-operating-system software—browsers, plugins, office suites, and enterprise applications—which often present the largest attack surface.

Why Third-Party Software Matters

While operating systems get the spotlight in patch management discussions, the reality is that most successful exploits target third-party applications. Web browsers, PDF readers, Java runtime, Adobe products, and business applications like SAP or Salesforce frequently contain vulnerabilities. Unlike centralized OS patching, third-party software comes from dozens of vendors, each with different update mechanisms, schedules, and quality standards.

The Challenge

Third-party patching is harder than OS patching because:

  • Fragmentation: No single tool patches everything. You might need separate mechanisms for browsers, Java, Office, Zoom, Slack, and custom enterprise apps.
  • Silent failures: Some apps auto-update but fail quietly when corporate proxies or permissions block them.
  • Compatibility risks: Business-critical plugins or integrations may break with updates.
  • User-installed software: Shadow IT and personal installations bypass centralized control.

Managing the Complexity

Effective third-party patching requires:

  1. Inventory everything: Use asset discovery and endpoint agents to find all installed software, including versions.
  2. Leverage automation: Tools like SCCM, Intune, or third-party solutions (Ivanti, ManageEngine) can deploy application patches alongside OS updates.
  3. Prioritize internet-facing apps: Browsers, email clients, and collaboration tools receive the most targeted attacks.
  4. Test thoroughly: Application patches are notorious for breaking integrations or workflows—staging environments are essential (as you learned in lesson 2455).
  5. Monitor vendor feeds: Subscribe to security bulletins from each major vendor.

Think of it like maintaining a fleet of vehicles from different manufacturers—each needs specific parts, schedules, and expertise.

Key Takeaway: Third-party and application patching demands comprehensive inventory, vendor-specific automation, and rigorous testing because these diverse software packages collectively represent your largest vulnerability exposure outside the operating system itself.