Skip to main content
Skip to content
Menu

Enterprise Security Beginner 3 parts

Document your AI tool's compliance posture for stakeholder review

You'll have a one-page compliance snapshot (controls, audit scope, subservice risks) ready to share with security teams, legal, or procurement without waiting for external audits.

What you'll make

AI Compliance Snapshot

  1. Tool Inventory: AI systems in use with security control assessment
  2. Dependency Map: Subservice risks and data flows
  3. Control Gaps: Where standard frameworks miss AI-specific vulnerabilities
  4. Evidence Summary: Audit findings and compliance decisions with justification

Submit as a single PDF or document with sections clearly marked for security team review

The 3 parts

Each part ends with a check you can see.

  1. Audit Your Current AI Tools

    Examine actual AI tool configurations and vendor documentation to build evidence-based security assessments.

    Done when

    Security assessment of 5+ AI tools with specific evidence from vendor docs, SOC reports, or configuration details that supports each maturity score

  2. Trace Actual Data Flows

    Investigate where your data goes when using AI tools and map real subservice dependencies.

    Done when

    Data flow map showing specific third-party processors for 3+ AI tools with evidence of actual data handling practices

  3. Document Control Gaps

    Create audit-ready documentation that addresses AI-specific compliance gaps with evidence-based recommendations.

    Done when

    Compliance snapshot document with specific control gaps, risk levels, and mitigation decisions ready for stakeholder review

    Capstone: you put together your AI Compliance Snapshot.

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 your AI tools by security control maturity
  • Map subservice dependencies that create hidden risk exposure
  • Produce audit-ready documentation that addresses AI-specific vulnerabilities
  • Make and defend compliance decisions using actual evidence vs generic frameworks

Who it's for

  • Security professionals evaluating AI tools in their stack
  • Compliance teams preparing for audits involving AI systems
  • IT leaders who need to document AI risks for stakeholders without waiting for vendor certifications

What it won't cover

  • Building custom security controls
  • Conducting penetration testing
  • Legal interpretation of specific regulations
  • Comprehensive risk frameworks or maturity models

Skills you'll practise

  • Security control assessment
  • Dependency risk mapping
  • Audit documentation
  • Evidence-based compliance decision-making