{"id":6974,"date":"2022-08-17T18:13:18","date_gmt":"2022-08-17T18:13:18","guid":{"rendered":"http:\/\/52.32.235.136\/?p=6974"},"modified":"2023-04-11T10:12:01","modified_gmt":"2023-04-11T17:12:01","slug":"securins-incident-response-to-the-log4j-vulnerability","status":"publish","type":"post","link":"https:\/\/webdev.securin.xyz\/articles\/securins-incident-response-to-the-log4j-vulnerability\/","title":{"rendered":"Securin\u2019s Incident Response to the Log4j Vulnerability"},"content":{"rendered":"\r\n
Rapid Action from Securin\u2019s Incident Response Team<\/em><\/strong><\/h5>\r\n\r\n\r\n\r\n
Safeguards Its Clients from the Log4j Vulnerability<\/em><\/strong><\/h5>\r\n\r\n\r\n\r\n
\u00a0<\/div>\r\n\r\n\r\n\r\n

Described as a \u201ccybersecurity Hiroshima\u201d or a \u201cFukushima moment,\u201d the impact of the Log4j vulnerability continues to be felt by thousands of companies exploited or attacked by hackers and ransomware. Yet, rapid and proactive action from Securin\u2019s Incident Response Team has helped protect all its clients.<\/p>\r\n\r\n\r\n\r\n

When the Log4j vulnerability was publicly disclosed on December 9, 2021, Securin immediately had its Incident Response Team reach out to all its clients to guide them on protective measures. Realizing that any vulnerability in Log4j, one of Java’s most popularly used open-source logging libraries, would put the clients using Apache Log4j at risk of data thefts, malware, or ransomware attacks, Securin\u2019s team came up with a rapid protection plan to safeguard clients\u2019 infrastructure.<\/p>\r\n\r\n\r\n

\r\n
\"\"<\/figure><\/div>\r\n\r\n\r\n
<\/div>\r\n\r\n\r\n\r\n

Objectives<\/strong><\/h2>\r\n\r\n\r\n\r\n