Cybersecurity foundations
What are we protecting, and how do we reason about it?
- F1Assets and the CIA triad: what we protect and how it fails
Identify tangible and intangible assets and connect each to the business workflow it supports
- F2Threat, vulnerability, and risk: the core equation
Distinguish threats, threat actors, vulnerabilities, exposures, and business risks in operational discussions
- F3Networks in one request: DNS, TCP, TLS, and HTTP
A fresh HTTP/1.1 connection runs DNS, TCP, TLS, and HTTP in order, and a cached answer or a reusable connection skips setup work.
- +
- +
- +
- F4Identity, authentication, authorization, and recovery
Identity, authentication, authorization, and recovery are four jobs inside one login.
- +
- +
- +
- F7Logs, alerts, and evidence: why an alert title is a hypothesis, not proof
Distinguish raw logs, detection alerts, and corroborated evidence
- F5Least privilege, defense in depth, and Zero Trust boundaries
Scope access grants across four dimensions: principal, target resource, permitted action, and time window (Just-In-Time)
- F5bApplication trust boundaries: why the client UI is never a security gate
Locate the exact trust boundaries in a modern web or microservice architecture
- F6Data protection and resilience: why encryption is not a backup plan
Separate what encryption at rest and in transit protect from what they leave vulnerable
- F6bCloud shared responsibility: what you rent vs what you still own
Draw the exact responsibility line between cloud provider and customer across IaaS, PaaS, and SaaS models
- +
- F8aOutcomes before controls: using NIST CSF, CIS, ISO 27001, and ATT&CK together
State a concrete risk reduction outcome before selecting a technical control or framework citation
- +