Data is dynamic. Data is unique. It's critical for businesses to maintain data security and integrity by treating it differently based on what it is, what it's for, who is accessing it, how it's being used, and the overall context surrounding these things.
In this second episode, we take a closer look at Log4j and what business/operations impacts it had on organizations faced with the attacks against the vulnerability. We also get to hear about some successful mitigation measures Imperva customers used to mitigate the impact of Log4j and take that to the next level for some actionable steps companies can take to prepare for other supply chain vulnerabilities.
Note: This story contains promotional content. Learn more.
Guest: Peter Klimek, Director of Technology - Office of the CTO at Imperva [@Imperva]
On LinkedIn | https://www.linkedin.com/in/peter-klimek-37588962/
Resources
Learn more about Imperva and their offering: https://itspm.ag/imperva277117988
Blog: Log4j: One Year Later
Solution page: Stopping software supply chain attacks
Learning center: Supply Chain Attack
Learning center: Zero-day (0day) exploit
National Telecommunications and Information Administration: Software Bill of Materials
National Telecommunications and Information Administration: Vulnerability-Exploitability eXchange
Are you interested in telling your story?
https://www.itspmagazine.com/telling-your-story