OWASP cautions against “insufficient logging & monitoring.” What does sufficient l...
summary
OWASP A10 insists on concrete controls: append-only centralized store for logs, enough retention and normalization to enable forensic reconstruction, runtime PII protection and validation plus incident training. Real numbers matter — 203 days discovery 73 days remediation — and roughly half of breaches stem from mistakes not just attacks. Practical options include turnkey API observability like Resurface that reduces assembly cost; measure what’s collected, who can access it, and whether it actually supports reconstruction.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:08What is A10
- 2:18Why does this matter
- 3:58Is this problem getting worse
- 5:43A10 Official Recommendations
- 10:05Challenges
- 12:43Best practices
- 15:46Benefits across the software development lifecycle
- 17:35Why is sufficient logging and monitoring important
- 20:27Triggering feelings
- 22:18Challenges of working with PHI
- 25:35Security and privacy techniques
- 28:25Software development life cycle
- 35:13Antipatterns
- 36:01No PII here strategy
- 43:48Strategies
related talks
33mLearning from Past Security Breaches: Strengthening AppSec Efforts and Focus
26mStop Hitting Yourself: How to Prevent Common Attacks to your Application
28mBreaches Are Everywhere; What's a Good Security Leader to Do
31mDemystifying Data Protection: Steps To Find, Monitor And Control Without Chaos
58m: The OWASP Top Ten Proactive Controls 2018
52mContinuous Security
23mInformation Security Expert
22mSecurity and Risks