After this lesson, try to
- Recognize confidentiality, integrity and availability failures.
- Separate authentication, authorization and accounting in one event.
- Explain privacy and non-repudiation without promising a legal outcome.
Separate the security objectives
Confidentiality limits access and disclosure to authorized parties. Integrity concerns accuracy and completeness, including protection against accidental corruption. Availability concerns access and use by authorized parties when needed. These objectives can fail independently: a public, functioning website can publish incorrect prices, and a confidential database can be unavailable.
Separate identity, permission and records
Authentication checks evidence for an identity claim. Authorization determines permitted actions. Accounting records relevant activity so that actions can be traced and reviewed. They are related but distinct: a public page can be authorized for anonymous reading, while a named employee can authenticate successfully and still lack permission to change a record. A log is useful evidence, not an automatic guarantee that a human identity has been proven.
Privacy has a wider purpose
Privacy concerns the appropriate handling of information about people, including its purpose and limits. The EDPB’s EU/EEA example covers more than citizenship: establishment, offering goods or services and monitoring can matter. Its principles include lawful and transparent handling, limited purposes and collection, accuracy, limited retention, security and demonstrable accountability. Do not infer that a particular small-business headcount automatically settles DPO obligations; relevant activities and legal context matter.
Non-repudiation depends on evidence
Non-repudiation concerns evidence that can help counter a later denial of an action. Digital signatures can support it when identity binding, key protection and verification are sound. It is not a promise that a person can never dispute an action or that a court must accept a particular record.
Apply CIA to AI inputs and outputs
Editorial application: protect sensitive training or input information from unauthorized disclosure, protect models and data against unauthorized changes, and consider the impact of an unavailable or unreliable AI service. One event can affect more than one security objective. NIST distinguishes manipulation of training data from direct model manipulation; protecting a dataset alone does not cover every poisoning path.
Make it your own.
Invent three booking-service failures. Identify the affected CIA objective, then explain where AAA and privacy matter.
Use fictional information. Writing an answer helps expose assumptions; this exercise is not independently marked.
Connect the terminology.
Take the next practical step.
- AI governance, risk appetite and control choice
INTRODUCTORY MATERIAL SUPPLIED · The formerly missing introductory worked teaching and guided decision-record practice are supplied. This status means introductory material is available; independently marked learner performance remains unresolved.
What to take further.
Coverage and remaining teaching
- AI01: Introductory material is supplied; broader scope is unverified in the exam coverage register.
Practice and feedback
- AI01: A guided paper case and explained model are available; independent review of fresh learner work and any live validation remain separate.
Free and paid resources
The linked applied guides and their paper activities are free; no cloud purchase or real-system test is needed. Official examination and maintenance charges follow issuer terms. Optional paid training or feedback is distinct from these free exercises.
A reading acknowledgement tracks your place; it does not establish competence or course completion.