How We Battled the Log4j Zero Day Vulnerability
summary
SurePay already runs 4 billion checks since 2017 with 80–83% matches, 12% close matches and 5% no matches, cutting misdirected payments by 67%. The incident response builds a GitHub‑crawling script, a Log4j war room, and active probes replaying exploit payloads against staging; Jenkins is briefly pulled from service and Elastic/Kibana and other third‑party stacks get priority review. Detection uses HTTP header monitoring, SBOMs and Sonatype Nexus Lifecycle, and mitigation relies on AWS controls (GuardDuty, Security Hub, CloudWatch) and fast configuration fixes.
AI-written summary · about
chapters (13)
- 0:00ShPay introduction
- 4:25ShPay architecture
- 10:30Security at ShPay
- 11:14Zero day vulnerability response begins
- 13:43Log4j investigation
- 16:55Log4Shell severity
- 18:23Unrelated incident
- 19:51Log4j landscape scan
- 21:19Crisis monitoring
- 23:04Third-party checks
- 23:47Log4Shell exploit
- 26:56Mitigation risks
- 27:39Lessons learned
related talks
26mHunting for log4shell Compromises
07mLog4j Hygiene
40mLog Story Short: Chopping Through Forests Of Data
32mBuilding a secure future using DEVSECOPS practices and technologies
33mLog4J, SpringShell and all that Jazz (or why bad things can happen to good software)
31mSecuring hybrid cloud environments
17mLog4j - A Placement Student's Baptism by Fire
23mWin the 0-Day Racing Game Against Botnet in Public Cloud