Phying News
P非影 中文
Curated security research, vulnerabilities, advisories and tools for practitioners.

Living with and Learning from Log4Shell

bugcrowd.com | blog | #supply-chain | #incident-response | #waf | #log4j | #soc | #supply-chain-security | #log4shell | #hardening

Summary

Bugcrowd CIO Nick McKenzie advises SOC teams to stay in red-alert mode for weeks after Log4Shell, use software composition analysis and trusted images, and watch for third-party supply chain attacks.
Published
Collected

original ↗

Related coverage

  1. Log4Shell: Attack Evolution (hackerone.com)
  2. Empower and Accelerate Your SOC with the Blue Agent (wiz.io)
  3. Building a Security Operations Center for the Cloud: Key Considerations for People, Processes, and Technology (wiz.io)
  4. Unveiling the power of Wiz's Security Graph with automated blast radius and root cause analysis for cloud incident response (wiz.io)
  5. Bugcrowd’s Log4j Response: Behind the Numbers (bugcrowd.com)
  6. Log4Shell, The Worst Java Vulnerability in Years (bugcrowd.com)

back