Unit 1 ยท Security foundations and risk
Confidentiality limits information disclosure, integrity protects correctness and provenance, and availability keeps authorized services usable. Real systems also require authenticity, accountability, privacy, and non-repudiation. A control should be connected to a concrete asset and objective rather than added because it sounds secure.
Asset: payroll records
Threat: unauthorized disclosure
Objective: confidentiality
Controls: least privilege, encryption, access loggingSecurity boundaries exist wherever trust, privilege, data classification, or administrative responsibility changes. A browser-to-API boundary is different from an API-to-database boundary, but both deserve explicit assumptions. Security architecture is the practice of making those assumptions visible and reducing blast radius when one control fails.
Risk combines an adverse event, its likelihood, and its impact. Quantitative estimates can be useful, but qualitative scales are often more honest when evidence is limited. A security decision should state what is protected, from which scenario, at what cost, and what residual risk remains.
1. Which objective concerns unauthorized disclosure?
2. Does encryption alone guarantee availability?
3. What makes a risk statement actionable?
A strong inventory identifies credentials and personal data as high-confidentiality assets, authorization records as high-integrity assets, and login availability as operationally important. Controls may include MFA, least privilege, encryption, monitoring, and tested recovery. Residual risks include compromised endpoints, recovery-channel abuse, and misconfiguration.