Hi everyone,

In the face of the current vulnerability crisis with log4shell, many people have been asking me how ServiceNow can help, and asking here in these forums how ServiceNow is doing with it.

Several teams worked together to assemble a two page response on the question of how we can help our customers manage the challenge, and I've attached it here in case it can help you.

Here are some image previews - please see the article's attachment for the full doc.

Update: since the initial post of this message, we have also created the attached "Log4J detection and remediation with ServiceNow" PDF to walk through solutions in more detail. Kudos to Steve Emerson and Sree Subramaniam from ServiceNow's ITOM Product Management team for their work on this doc!

Here is a sample:

\

In addition, here is a demo video from ServiceNow's M Naser, showing how Vulnerability Response can help drive remediation efforts:

Next, regarding ServiceNow's status with Log4J / Log4Shell, please see these KB articles which speak to the threat and our readiness in general:

ServiceNow KB: KB1000959

ServiceNow Security Advisory KB: KB0870307

Edit: please note that these links require logging in! They will show as "No Longer Available" until you log in.