Lesson 1 · Audio + reading
Threats, vulnerabilities and risk
Approx. 5 minutes
Learning objectives
- Understand threats, vulnerabilities and risk.
- Apply the skill to a realistic task.
- Identify one limitation or failure mode.
Audio-first lesson
Listen to Threats, vulnerabilities and risk
The narration follows the approved lesson script. The full transcript remains available below for accessibility and study.
Technical explanation
Threats, vulnerabilities and risk belongs to the Security Foundations stage of the course. The professional focus is risk identification, identity and access, defensive controls, incident handling and AI-specific security boundaries. Treat inputs, permissions, assumptions and outputs as explicit interfaces; validate important results instead of trusting a first successful demonstration.
Real-world example
A small organization discovers a suspicious login while staff are also using an AI assistant. The learner must identify the asset, assess the risk, choose a control and preserve a clear escalation path.
Full lesson text used for narration
Learning objectives Understand threats, vulnerabilities and risk.\nApply the skill to a realistic task.\nIdentify one limitation or failure mode. Technical explanation Threats, vulnerabilities and risk belongs to the Security Foundations stage of the course. The professional focus is risk identification, identity and access, defensive controls, incident handling and AI-specific security boundaries. Treat inputs, permissions, assumptions and outputs as explicit interfaces; validate important results instead of trusting a first successful demonstration. Real-world example A small organization discovers a suspicious login while staff are also using an AI assistant. The learner must identify the asset, assess the risk, choose a control and preserve a clear escalation path. Knowledge check **Q1 (Apply).** Which approach demonstrates professional use of threats, vulnerabilities and risk? - Define the outcome, validate the inputs and outputs, test failure cases and document the fallback. - Skip testing because the first demonstration worked. - Give the system unrestricted access so it can solve more problems. - Treat every AI-generated result as verified. *Explanation:* This answer matches the lesson's stated knowledge check. **Q2 (Apply).** What should happen when the system reaches a case it cannot verify safely? - Escalate to the defined human owner or safe fallback. - Silently continue and hide the uncertainty. - Increase permissions automatically. - Delete the evidence of the failure. *Explanation:* This answer matches the lesson's stated knowledge check.