Keynote - Starting a metrics program
summary
Concrete claims, tools, counts and results: pick a talk that names a unit of measurement and shows how it maps to business impact, shows data from Nessus scans or runtime control experiments, and reports a hard outcome like three production stoppages costing 15,000 widgets or one business unit causing 70% of incidents. Look for a built artifact (automation that zips logs and answers the ten IT questions, a process flowchart) and before/after numbers (50% fewer incidents, reduced downtime). If it lacks those, skip it.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:45What are Metrics?
- 5:39Why Keep Metrics
- 20:01An Illustration
- 37:09How to Establish Metrics.
- 44:24Keeping Metrics Relevant
- 52:16Advanced Work
- 58:24Why Metrics Win
related talks
59mKeynote: Measure Security Effectively
01h 01mFinding Metrics that matter and using them safely
15mKeynote
44mOpening Keynote: Prove It! Confronting Security With Data.
23mYou Get What You Measure—Why Metrics Are Important
01h 01mKeynote Presentation Balancing Core Conflicts A DevOps Story
01h 00mTop 10 Metrics for Successful DevSecOps Projects
25mWhen Metrics Lie
