How to Be Your Security Team's Best Friend
summary
Summarizes concrete steps: adopt the CIS Critical Security Controls; maintain searchable inventories of instances, containers and installed packages so alerts map to actual hosts; run authenticated and non‑authenticated scans weekly and prioritize patching by risk; enforce separate admin accounts and role/group-based privileges with logged privilege escalation; automate config and CI/CD testing of patches and gold images; log outbound traffic and protect secrets (use truffleHog on GitHub), monitor licenses/domains/SSL expirations, and clean up technical debt to reduce attack surface.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:08The CIS Critical Security Controls
- 7:25Inventory and Control of Hardware Assets
- 10:57Inventory and Control of Software Assets
- 17:46Controlled Use of Admin Privileges
related talks
28mHow To Be Your Security Team's Best Friend
01h 03mBe your own Threatbuster!
20mWhat do security teams really want?
29mGet the Freaking Basics Right!
38mPrioritizing Trust While Creating Applications
31mSharing Security Secrets: How to Encourage Security Advocates
52mContinuous Security
58mHow to embed security into your process