Charles Leaver – The Lowdown On Patch Validation

Written By Logan Gilbert And Presented By Charles Leaver



A current report indicates almost twenty thousand brand-new software application vulnerabilities were discovered in 2017 – an all-time record. Think of that for a second. That’s an average of 55 brand-new vulnerabilities per day. That’s a big amount for any IT store to handle.

Actually there’s good news and bad news. The bright side is that patches were offered for eighty six percent of those vulnerabilities on the day of disclosure. The bad news is that a lot of organizations continue to have a problem with patch prioritization, application, and validation. And as IT tasks progressively move to the cloud, vulnerability visibility tends to reduce – worsening an already difficult challenge.

Let’s take a better look at ways to manage cloud patch validation efficiently.

Initially, a Patch Management Primer

Patch management is the practice of updating software applications with code modifications that address vulnerabilities exploitable by cyber hackers. Despite the fact that it’s been around for decades, patch management remains a difficult procedure for a lot of IT organizations.

Modern businesses have complicated IT environments with multiple integration points in between business systems. That means it is difficult for software designers to represent all unintended effects, e.g., a condition that might close a port, disable crucial infrastructure interaction, or perhaps crash its host server.

And concentrating on the effective patching of known vulnerabilities is the unquestionable ‘big bang for the buck’ play. In 2017, Gartner reported 99% of exploits are based upon vulnerabilities that have actually currently been understood to security and IT professionals for a minimum of 12 months.

Cloud Patching Principles

The first secret to closing down the right vulnerabilities in your cloud IT infrastructure is being able to see everything. Without visibility into your cloud systems and applications, you can’t truly understand if both those systems and applications are patched where it is crucial. The 2nd key is patch validation. Just firing off a patch is no assurance that it triggered appropriately. It may, or might not, have actually released successfully.

How would you be sure of this?

The Ziften Method

Ziften supplies the visibility and validation you require to guarantee your cloud IT environment is safe and secure from the vulnerabilities that are the most crucial:

– In-depth capture of discovered OS and application vulnerabilities

– Findings mapped to vulnerability insight references, e.g., OWASP, CIS, CVE, CWE, and OSVDB

– Detailed descriptions of the ramifications of findings, organization effects, and dangers for each of the determined exposures

– Vulnerability prioritization based upon asset criticality and threat of attack

– Remediation suggestions to close identified shortages

– Comprehensive actions to follow while mitigating reported deficiencies

– Detection and mitigation of attacks that take advantage of unpatched systems with quarantine procedures

Far too frequently we find that the data from customer’s patching systems incorrectly report that vulnerabilities are indeed patched. This develops a false sense of security that is undesirable for IT operations and security operations groups.

Leave a Reply

Your email address will not be published. Required fields are marked *