
Map your AI tool's blind spots visually
You'll have an infographic or diagram showing which parts of your AI-built application are high-risk (data exposure, no auth, unvetted logic) and which are safe.
What you'll make
AI Code Risk Map
- Legend: risk levels and what they mean
- Architecture: boxes for each major component
- Risk indicators: color coding and warning symbols
- Annotations: specific vulnerabilities found
Upload a diagram, infographic, or screenshot of your risk map with components clearly labeled and color-coded
The 3 parts
Each part ends with a check you can see.
Inventory Your AI-Built Components
List every piece of code AI generated for your project and what it actually does
Done when
You have a complete list of 8+ AI-generated components with their specific function and data they touch
Test AI's Security Assumptions
Run specific security checks on your riskiest AI-generated components to find actual vulnerabilities
Done when
You have tested 3+ high-risk components and found at least 2 specific issues AI missed (input validation, access control, error handling, etc.)
Create Your Visual Risk Map
Build an infographic showing your application's components color-coded by security risk level
Done when
You have a visual map with all components from Task 1 color-coded (red/yellow/green) and annotations showing specific vulnerabilities from Task 2
Capstone: you put together your AI Code Risk Map.
Where this helps
An elective: a single lesson that sits outside rtwo's job certificates and doesn't count toward one.
About this lesson
What you'll be able to do
- Map at least 10 specific components of your AI-built project with risk levels (critical/moderate/low)
- Have 3-5 concrete security checks you run on any AI-generated code before using it
- Know which parts of your codebase you'd never let AI touch vs which are safe for full AI generation
Who it's for
- Anyone building with AI assistance who's wondering what they're missing in code review
- Developers who've shipped AI-generated code and want to audit what's already live
- Technical leads evaluating AI coding practices for their team
What it won't cover
- How to write secure code from scratch — this is about auditing AI output
- Penetration testing or formal security analysis
- Tool-specific security features (auth providers, cloud configs, etc.)
Skills you'll practise
- Component-level risk assessment
- AI output security auditing
- Visual risk communication
- Trust calibration for AI-generated code