Patching Automation Adaptable to Your Workflow
Due to the complexity of today’s IT infrastructure, when patching an endpoint, multiple operations must often be run prior to and after the actual patching.
Nowadays, no endpoint resides in isolation, rather is part of a cluster, whether on-premise or on private or public clouds. Each is controlled by a specific group and adheres to different regulations and ‘modus operandi’.
Common endpoint pre-patch preparations include checking disk space, shutting down critical applications, creating a backup image of the endpoint (in preparation for a worst-case scenario), separating the endpoint from its current cluster and more.
Post-patching activities may include clearing unrequired files, starting applications, executing a reboot -- or multiple reboots -- and validating of system status prior to going live.
Orchestrating this sequence of actions is not an easy task, since it generally involves multiple people and combinations of manual and semi-automatic processes.
JetPatch provides a dynamic and easy-to-use workflow mechanism that orchestrates all tasks. Once plugged into the workflow automation, no manual intervention is required.
As you can see above, the JetPatch workflow interface can be customized to support the specific pre and post patching-related tasks of each organization and create an automatic chain of events.
One of the primary steps in creating an enterprise patching strategy is to split endpoints in the environment into several reference groups, according to severity levels.
The main purpose is to help the operations team to prioritize patching cycles, which are already complex. Categorizing endpoint groups according to asset importance allows for more effective decision making, as well as enabling quick reaction in the event of an emergency cycle, such as when a zero-day patch is required.
__________________________________________________________________________
Experience a JetPatch Free Trial today!