Build Cyber-Awareness in Platform Development Teams
summary
States that platform teams adopt a secure-by-design mindset, run penetration testing every 3 months and use static code analysis plus automated tools and SIEMs like Microsoft Defender to catch issues early. Recommends concrete controls: enforce 15‑character passwords, MFA and encryption, least‑privilege access, VLAN/VPN segmentation, firewalls, secure logging that records who accessed what and when, regular backups, and a documented incident response plan.
AI-written summary · about
chapters (11)
- 0:00intro
- 0:14introduction to cybersecurity awareness
- 0:53understanding modern cyber threats
- 1:56secure by design mindset
- 2:33quality assurance and testing
- 3:39building a security-conscious culture
- 5:34secure coding practices
- 8:01network security and segmentation
- 10:14incident response planning
- 11:15continuous monitoring and empowering your team
- 13:22conclusion and final thoughts
related talks
26mPlatform Engineering Loves Security: Shift Down To Your Platform, Not Left To Your Developers! - Maxime Coquerel, Royal Bank of Canada
28mImplementing Critical Cybersecurity Controls in a DevOps Environment
01h 03mBe your own Threatbuster!
21mIncorporating Security into Platform Engineering: The Dos and Dont’s
52mContinuous Security
27mBridging the Dev-Sec divide: Three tips for agile developers
45mBuilding Secure Software: Practical Strategies for Developers
29mSecuring the platform: Hard-won lessons from the teams who've been breached, scaled, and survived