Learning paths › Security Engineer › 01. Security Fundamentals & SOC Workflow
01. Security Fundamentals & SOC Workflow
The vocabulary a SOC actually runs on, and the loop it runs: classify the failure, separate weakness from consequence, map the controls and their shared dependencies, then turn an alert into a question, a proportionate containment and a named owner.
Lessons
- Confidentiality, Integrity, Availability — And What Each Costs The Others
- Weakness, Threat Event, Consequence: Three Words People Use Interchangeably
- Attack Surface: Listeners, Management Interfaces And Who The Service Logs In As
- Identification, Authentication, Authorization, Audit — Four Records, Four Questions
- Hashing Is Not Encryption, And Encrypted Is Not Safe
- Layered Controls And The Shared Dependency That Defeats All Of Them
- Four Threat Patterns And The Evidence That Separates Them
- Backups You Have Restored, And The Dependency Nobody Tested
- From Alert To Owner: The Triage Question That Comes Before Containment
- Facts, Hypotheses, Unknowns: A Handoff The Next Analyst Can Continue
- Lab 1: Map Five Services To Their Exposure, Owner And Recovery Control
- Lab 2: Order Four Overnight Alerts And Write The Handoff
- Case: A Service Account Joined An Admin Group At 02:14
- Project: A Security Service Review Another Engineer Could Act On
- Checkpoint: Ten Outcomes, One Unseen Example, And The Limits Of Your Evidence
More in Security Engineer
- 00. Prerequisites: Packets, Protocols & Log Reading
- 02. Firewall & Perimeter Rule Logic
- 03. Network Traffic Analysis
- 04. Intrusion Detection
- 05. SIEM & Log Correlation
- 06. Vulnerability Management
- 07. Multi-Source Incident Response (Capstone)
- Cisco ASA
- Cisco Firepower (FTD)
- Fortinet FortiGate
- Splunk for Network & Security Operations
- Snort & Suricata IDS/IPS
- Security Scenarios & Capstone
- Zscaler: Secure Web & Private Access