
Map your AI toolchain's dependency attack surface for supply chain risks
You'll have a documented list of every AI-adjacent dependency (IDE extensions, package managers, CLI tools) with disk access on your machine and a process for vetting them before installation.
What you'll make
AI Toolchain Security Audit
- Current Attack Surface Map: tools and access levels
- Risk Assessment Matrix: likelihood vs. impact scoring
- Vetting Process: criteria and workflow for new tools
- Ongoing Monitoring Plan: review triggers and intervals
The 3 parts
Each part ends with a check you can see.
Map Your Current Attack Surface
Catalog every AI-related tool with disk access on your development machine
Done when
Complete inventory of 10+ AI toolchain dependencies with documented access levels and installation dates
Test Your Exposure Assumptions
Discover what sensitive data your AI tools could actually access beyond your repositories
Done when
Evidence-based risk assessment of 5+ tools with specific exposure examples found on your machine
Build Your Tool Vetting Process
Create a repeatable decision framework for evaluating new AI development tools before installation
Done when
Working vetting checklist with 6+ criteria tested against 2+ real tool installation decisions
Capstone: you put together your AI Toolchain Security Audit.
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
- Audit your development machine for AI toolchain dependency attack vectors
- Build a repeatable vetting process for new AI development tools before installation
- Create a documented dependency map showing disk access levels across your AI workflow
- Distinguish between repository-level and machine-level security boundaries
Who it's for
- Developers using AI coding assistants who haven't mapped their toolchain's attack surface
- Teams adopting AI development tools without established security review processes
- Software engineers concerned about supply chain risks in their AI-enhanced development workflow
What it won't cover
- How to build secure AI models
- Network security or infrastructure hardening
- Specific secret management tool implementation
- Enterprise security policy development
Skills you'll practise
- Dependency attack surface analysis
- Tool vetting workflow design
- Risk assessment under uncertainty
- Security boundary identification