What factors are most important for organizational patch management?

JA

James J Azar

Chief Information Security Officer · Artera Services

Prioritize by Risk and Impact

James J Azar says organizations should prioritize patch remediation based on exploitation, business impact, exposure, and the privileges of affected systems, since security teams cannot patch every vulnerability with the same urgency.

Vipin Samar

Senior Vice President, Database Security · Oracle

Immediate, Fleet‑Wide Deployment

Vipin Samar says organizations should patch immediately rather than wait months, and deploy across the entire fleet, because AI gives hackers tools to reverse-engineer patches and build exploits.

Michael Jenkins

C.T.O. · Threatlocker

Keeping Up with Patches

Michael Jenkins says keeping up with patches matters, suggesting organizations might want bleeding-edge updates rather than N-minus-one for network edge appliances because it may yield a more hardened stack.

Sam Curry

Chief Information Security Officer, SVP · Zscaler

Third‑Party Risk Management

Sam Curry says his emphasis to people would be doing their third-party risk management surveys, so they can make sure people are getting ready rather than to bait the wounded.

The answer starts at 23:24.

Tal Kollender

Co-Founder & CEO, CISO · Remedio

Communication and Collaboration

Tal Kollender says good communication and collaboration—between infrastructure teams, senior managers and the board—are important for patch management, because upgrades and downtime need to be explained properly.

Joshua Aaron

CEO · Aiden Technologies, Inc.

Visibility

Joshua Aaron says it comes down to visibility, since you need to know what is out there and understand its risk, because you cannot patch fast enough.