When Your Dashboard Explodes – Do You Care Enough to Send the Very Best?
summary
Case study of a security dashboard that stops being trusted after cloud and sandboxing rules break phishing telemetry, forcing a two‑month pause, internal testing and a rebuild tied to the NIST CSF. Vulnerability scans run unauthenticated, EDR is seven versions behind, SIEM needs rebuilding, and O365 sandboxing blocks simulated phishes. Benchmarks show 3% industry average failure target; leadership ties director bonuses to that metric, swaps phishing vendors to align with the email gateway, and achieves under 1% after change.
AI-written summary · about
chapters (12)
- 0:00Start
- 2:02Building the Brand
- 7:27Your first board presentation at the new company...
- 8:25Build Common Ground
- 10:33Magic Slides?
- 12:40Protecting the Brand
- 14:12Patching, Really? Patching...Again?
- 15:01Patching, resolved...Maybe
- 17:33How are you Phishing?
- 23:29Investigation and Indigestion
- 27:19Ahh, Back to Normal
- 28:06Apply What You Have Learned Today • Next week you should - Review the accuracy of metrics in your dashboard
related talks
51mCloudSec Hero to Zero: Self-Obsolescing Through Prolific Efficiency
30mGetting Engagement in the Midst of Chaos
57mBuilding a Modern Security Engineering Organization
46mLearning security monitoring through failure
44mDeveloping Cybersecurity - How do you make Staff Know Security
20mCalcifying Crisis Readiness
21mOn Trust: Stories from the Front Lines
35mMetrics That Matter: How to Choose Cloud Security KPIs for Your Business