Following the recent IT earthquake - namely Log4Shell - most cybersecurity experts have asked (or been asked) one of the following: "How can we quickly identify and mitigate Log4Shell risk?", “How can we better detect new vulnerabilities in the future?”. As software development continually evolves, the need for protection against web application attacks is greater than ever. With cloud environments becoming too complex for humans to manage, the only way to keep up is with complete automated security, requiring no human intervention — no configuration, no installation, no dedicated security testing, no waiting for results, and no manual piecing together of information from multiple tools. The recent Log4Shell vulnerability is another example of why organizations need a solution that can immediately and automatically identify vulnerable systems, their dependencies, and help them prioritize the most critical systems to update first, especially on code running in production.

What you will learn

1.  For the record: Log4Shell identity card
2.  Dive-in: How to exploit Log4Shell? (Red Team Lab Session)
3.  Lessons learned: What has Log4Shell taught us about vulnerability detection?
4.  Hands-on: How to detect run-time vulnerabilities? (A Dynatrace Application Security Demo)
5.  Open Q&A session with our experts

Who should watch

All cyber security, information security and IT professionals responsible for the security of cloud-native applications across the entire software development lifecycle.