1. Confidentiality
Confidentiality keeps data secret from unauthorized parties; encryption is the primary control.
confidentiality: encrypt-at-restTyporithm · easy
Step 1 of 8 · intro card
Foundations
The CIA triad — Confidentiality, Integrity, Availability — is the core model for what security protects. AAA (Authentication, Authorization, Accounting) is how access is controlled: proving who you are, what you may do, and recording it.
Confidentiality, Integrity, and Availability form the CIA triad — the three properties every security control aims to preserve. Confidentiality keeps data from leaking, integrity keeps it from being altered, and availability keeps it reachable.
AAA describes the access-control lifecycle. Authentication answers "who are you?" by verifying credentials. Authorization answers "what can you do?" by checking permissions once identity is established.
Accounting (the third A) records what was done, producing audit logs for detection and forensics. Every concrete control — encryption, hashing, failover, MFA, role checks — maps back to one of these properties.
CIA = Confidentiality, Integrity, Availability.
AAA = Authentication, Authorization, Accounting.
Every control maps to one of these properties.
security:
confidentiality: encrypt-at-rest
integrity: sha256-checksums
availability: redundancy-failover
authentication: who-are-you
authorization: what-can-you-do
accounting: audit-logsConnect each part of the code to the concept before you type.
Confidentiality keeps data secret from unauthorized parties; encryption is the primary control.
confidentiality: encrypt-at-restIntegrity ensures data is not altered; checksums and hashes detect tampering.
integrity: sha256-checksumsAvailability keeps systems reachable; redundancy and failover resist outages and DoS.
availability: redundancy-failoverAuthentication verifies identity — proving who you are with credentials or factors.
authentication: who-are-youAuthorization decides what an authenticated identity is permitted to do.
authorization: what-can-you-doRead the concept map and follow the code breakdown.
Type the implementation, repair mistakes and work through every recall exercise.
Use the final check without hints; revisit weak concepts in short practice sessions.