c
Jan. 6, 2022, 6 p.m. |

Cloud Security Alliance cloudsecurityalliance.org

Quick note: from now on I will refer to log4j version 2 as “log4j2” To learn how to deal with the critical vulnerability in log4j2, read the first blog in this series, Dealing with log4shell. To get a breakdown of the timeline of events, refer to the second blog, Keeping up with log4shell. So how did we end up in this #log4shell situation? #log4shell is actually two intertwined problems: The vulnerability in log4jThe widespread usage of log4j, especially in ways …

cve cve-2021-44228 log4shell

More from cloudsecurityalliance.org / Cloud Security Alliance

SOC 2 Manager, Audit and Certification

@ Deloitte | US and CA Multiple Locations

Information Security Engineers

@ D. E. Shaw Research | New York City

Cybersecurity Consultant- Governance, Risk, and Compliance team

@ EY | Tel Aviv, IL, 6706703

Professional Services Consultant

@ Zscaler | Escazú, Costa Rica

IT Security Analyst

@ Briggs & Stratton | Wauwatosa, WI, US, 53222

Cloud DevSecOps Engineer - Team Lead

@ Motorola Solutions | Krakow, Poland