Patching Strategies are the central management objects in Tenable Patch Management because they group the details that define how, when, and where to update patches. Tenable Patch Management includes prepopulated templates that address most patching scenarios. You can save these templates using your own titles and descriptions, and then customize them to your environment.
Each Patching Strategy uses building blocks that can include Schedules, Notifications (Chains), Deployment Channels, and Bots to define a given patching scenario. At minimum, a Patching Strategy must include a Patching Process and a Deployment Bot.
Functionally, a Patch Strategy performs the following:
Automated handling of new patches
Automatically discovers new patches and uses the Deployment Bot to match new patches to the Patching Strategy. The Patching Process queues patches for processing and, according to the set schedule, activates patch deployment in groups to minimize the impact on endpoints and end users.
Customized targeting of patches
Administrators can target specific products and high-profile patches that trigger a Deployment Bot based on individual products. Targeting is particularly useful when you first install Tenable Patch Management , you have a considerable number of products that require patching, and you prefer to review the progress of patching before fully automating the process.
Reuse Intent Schema Objects
All objects in Tenable Patch Management are interoperable and designed for use in any Patching Strategy. Create a patching process, schedule, notification or approval chain, or deployment process once, and then use them in various Patching Strategies depending on your needs.
These built-in strategies are often enough to get an organization started with a patch deployment scenario.
