Operations | Monitoring | ITSM | DevOps | Cloud

Our sales team receives handfuls of patching questions so often, we almost brought in the bots to answer. But because the questions below require more explanation, I grabbed a few minutes with Ivanti’s patch management resident expert, Chris Goettl, for answers to questions concerning patching in the cloud, standalone patching, validating patches, and patching remote endpoints.

As the industry leader in the DevOps space, we’re excited to share recent updates to the Puppet Enterprise platform that give infrastructure operations teams the flexibility to manage and automate more infrastructure and complex workflows in a simple yet powerful way.

Patching systems is not a new problem; this is something that organizations are very familiar with. Organizations have tried solving this issue in various ways by cobbling together multiple tools, processes, different teams, and more. Organizations are constantly trying to stay secure and keep their systems up to date, but patch management isn’t a simple process. In fact, applying the patch itself is just one part of the overall workflow, which involves multiple teams and various steps.