CyberSecurity is too general: Why we need Security Domains
summary
Argues that cybersecurity must split into six domains — compliance, network, monitoring, cryptography, architecture, and hacking — because compliance checklists and one-size-fits-all roles leave exploitable gaps. Shows monitoring increasingly relies on ML/Data‑science rather than pure security skillsets, points to cloud tools like CNAPP/CSPM/CWPP, recommends moving security reviews earlier in development, and names reverse‑engineering tools IDA and OllyDbg while noting real exploit discovery requires painstaking work, not movie‑style keystrokes.
AI-written summary · about
chapters (15)
- 0:00intro
- 1:43preamble
- 1:56about michal
- 3:00security domains
- 4:33motivation
- 7:52security domains
- 8:50compliance
- 11:08network security
- 14:33monitoring
- 17:05cryptography
- 21:34security architecture
- 24:05hacking
- 26:41summary
- 27:16additional resources
- 28:08thank you
related talks
59mCybersecurity as an ecosystem
11mCybersecurity for an Inclusive Future
31mThe Art of Cybersecurity Mastery: From Entry-Level to Staff+
44mCyber Security Careers Security Specialties & Skills Development
40mTotal Security: Investigative Perspectives from Public to Private Sector
28mImplementing Critical Cybersecurity Controls in a DevOps Environment
23mCyber Security: In search of the Holy Grail?
51mThinking Differently About Security