Featured

Log4J and Beyond: Protect Your Ass{ets} with ServiceNow



Published
The Log4j vulnerabilities have been weaponized as a high-risk and complex seismic event, affecting everyone on a global scale, and no organization should assume it's safe. What does this mean? It allows remote code execution on platforms leveraging the popular Apache Log4j java library. Any application which uses Log4j for log file management or LDAP queries could be vulnerable and open to attacks, affecting resources beyond the security scope - one line of malicious code can be executed to remotely run on the affected server, taking full control of the vulnerable device. MITRE has rated this vulnerability as critical and assigned a CVSS score of 10/10. So what can WE do? Join our live webinar to learn how ServiceNow can detect, protect, and prioritize your organization's defensive measures from Log4j and future vulnerabilities!

Lorin Miller: CMDB - Query & Parry!

M Naser: Vulnerability Response: Patch & Punch

Chris Walker: MITRE & Major Security Incident Management
Category
Management
Be the first to comment