Skip to main content
Skip to content
Menu

Developer Tools Beginner 3 parts

Audit your local machine for AI-exposed secrets beyond version control

You'll have a documented inventory of credential exposure points on your machine that version control alone won't protect, plus a repeatable audit workflow to run before onboarding new AI tools.

What you'll make

Local Machine Security Audit

  1. Credential Inventory: location → exposure level
  2. Tool Access Analysis: what can read what
  3. Pre-AI-Tool Checklist: questions to ask before installation

The 3 parts

Each part ends with a check you can see.

  1. Map Your Credential Storage

    Inventory where credentials actually live on your machine, beyond what Git tracks

    Done when

    Complete file system map of credential locations with exposure assessment for each

  2. Test What Tools Can Actually Read

    Verify which installed tools and extensions can access your credential locations

    Done when

    Documented access scope for your current development tools with specific examples of what each can read

  3. Build Your AI Tool Evaluation Checklist

    Create a repeatable workflow for assessing credential exposure before installing new AI development tools

    Done when

    Working checklist with specific questions that covers disk access, storage patterns, and exposure verification

    Capstone: you put together your Local Machine 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

  • Inventory all credential storage locations on your local machine beyond Git scope
  • Distinguish between theoretical and actual exposure vectors in your development environment
  • Build a repeatable pre-AI-tool audit checklist that covers disk-level, not just repo-level security

Who it's for

  • Developers using AI coding tools who assume .gitignore protects their credentials
  • Teams evaluating AI development tools without understanding disk-level exposure
  • Individual contributors responsible for their own security posture

What it won't cover

  • How to set up secret management systems like Infisical
  • Network security or VPN configuration
  • Supply chain attack prevention strategies
  • Team-wide security policy design

Skills you'll practise

  • Local asset inventory
  • Exposure risk assessment
  • Security gap analysis
  • Audit workflow design