AI governance & compliance
Your staff already use AI. Now govern it.
Lavawall® detects the AI already in your environment from the security and IT data you have, recommends the right AI governance framework automatically, and generates the matching policies and disclosures. Five AI frameworks share one control set with every other framework Lavawall supports, and every step is written in plain language anyone can use. Somewhere in your business, someone is pasting client data into an AI tool nobody approved.
Start with the GRC Wizard See GRC & compliance
NIST AI RMF · ISO/IEC 42001 · EU AI Act readiness · OWASP Top 10 for LLMs · Canadian AI governance · Over 75 frameworks in all
Five AI frameworks, one control set
Find the shadow AI first
Built from the security and IT data you already have, Lavawall detects the AI tools in use across your environment, including the ones nobody logged. You can't govern what you can't see, so this is where governance actually starts.
The right framework, recommended for you
Based on what it finds and how you operate, Lavawall recommends the framework that fits: the NIST AI Risk Management Framework, ISO/IEC 42001, EU AI Act readiness, the OWASP Top 10 for LLM Applications, or Canadian AI governance. No guessing which standard applies to you.
Satisfy one control, cover many
The AI frameworks share a single control set with your security and privacy frameworks. A control you turn on typically counts across NIST, ISO, EU, OWASP, and Canadian expectations at once, and toward SOC 2, ISO 27001, or PIPEDA where they ask for the same thing, so you cover them all without separate projects.
Policies and disclosures, generated
Lavawall generates the AI policies your team needs and the disclosures your clients and regulators expect, matched to the framework you're adopting and kept current, not copied from a stale template.
Plain language anyone can use
Every step is explained in language a non-specialist can follow, so a small team can stand up credible AI governance without hiring an expert or decoding a standard line by line.
A live view of where you stand
See which AI controls are in place, which are open, and how to close them, per framework, so AI governance becomes an ongoing score instead of a one-time scramble.
The five AI frameworks you can adopt
NIST AI RMF
The US AI Risk Management Framework for identifying, measuring, and managing AI risk across its lifecycle.
ISO/IEC 42001
The international standard for an AI management system, the ISO 27001 equivalent for AI.
EU AI Act readiness
Prepare for the risk-tiered obligations of the EU AI Act before they apply to your use of AI.
OWASP Top 10 for LLM Applications
The security baseline for anyone building or deploying large-language-model features.
Canadian AI governance
Align with Canada's direction on responsible and accountable AI use.
One shared control set
Map once and progress on every framework on this page at the same time.
Every framework, one engine
Every framework Lavawall supports
Over 75 frameworks in all. Your AI governance runs in the same control set as the security, privacy, and industry frameworks your clients, insurers, and regulators already ask about. Turn on a control once and it counts toward every framework below that asks for the same thing.
Frameworks, standards, and regulations Lavawall® maps and evidences:
Security & governance
- CIS Controls v8 8.1
- Canadian Program for Cyber Security Certification (CPCSC) ITSP.10.171 Oct 2025; Level 1 Apr 2026
- NIST Cybersecurity Framework (NIST CSF) 2.0
- NIST SP 800-171 r3
- Canadian Centre for Cyber Security Guidance 2024
- COBIT 2019 2019
- ITIL 4 4
- Ontario Cyber Security Framework 2024
- ISO/IEC 27001 2022
- Sarbanes-Oxley Act (SOX) 2002
- C-SOX (Canadian Securities NI 52-109) 2023
- EU NIS2 Directive 2024
- CMMC v2.0
- UK Cyber Essentials 2025
- EU Cyber Resilience Act (CRA) 2024
- SOC 2 2024
- IEC 81001-5-1 Health Software Security Life Cycle 2021
- ANSI/AAMI SW96 Medical Device Security Risk Management 2023
- HSCC Medical Device and Health IT Joint Security Plan v2.0 (March 2024)
- Canadian Cyber Essentials 2024
- Australian Essential Eight 2024
- Ontario Personal Health Information Protection Act (PHIPA) 2004, as amended
- Ontario AODA - Integrated Accessibility Standards (O. Reg. 191/11) O. Reg. 191/11, consolidated 30 March 2026
Privacy
- CCPA / CPRA 2023
- Alberta PIPA 2022
- BC PIPA 2023
- Quebec Law 25 (Private Sector Privacy) 2024
- BC FIPPA 2023
- EU GDPR 2018
- UK GDPR / Data Protection Act 2018 2021
- Australian Privacy Act 1988 2024
- PIPEDA 2024
- Children's Online Privacy Protection Rule (COPPA) 16 CFR 312, amended 2025
- Consumer Privacy Protection Act (CPPA) - Draft, not in force Bill C-27 first reading (died 6 January 2025)
- Protecting Privacy and Consumer Data Act (PPCDA) - Draft, Bill C-36, not in force Bill C-36 first reading (15 June 2026)
Payment card
Energy & critical infrastructure
Government & public sector
- NIST SP 800-53 - Security and Privacy Controls Rev. 5
- FBI CJIS Security Policy 6.1
- FBI CJIS Security Policy 5.9.5 (Pre-Modernization) 5.9.5
- Alberta Protection of Privacy Act (POPA) / Access to Information Act (AITA) 2025
- Ontario MFIPPA - Municipal Freedom of Information and Protection of Privacy Act (as amended by Bill 194) 2024 amendments
- Iowa Public Sector Information Obligations 2026
- IRS Publication 1075 - Federal Tax Information 2024
- US Water & Wastewater Cyber Security (AWIA) 2026
- ADA Title II - Web and Mobile Accessibility 2024 Final Rule
- GovRAMP (formerly StateRAMP) - Cloud Vendor Assurance 2026
- CCCS Cloud Control Profiles (ITSP.50.103) ITSP.50.103 Annexes A and B
- CCCS Cloud Assessment: Medium and PBHVA Program page June 2026; ITSM.50.100
- CCCS Common Criteria Program (Product Certification) Program Instructions v2.3 (May 2025)
Healthcare
AI governance
Financial services
- FTC Safeguards Rule 2023
- GLBA: Gramm-Leach-Bliley Act 2023
- NYDFS Cybersecurity Regulation 2023
- FINTRAC / PCMLTFA 2024
- EU DORA 2025
- BC Financial Services Authority Security Guidance 2024
- CPA Canada Cybersecurity Framework 2024
- CIRO Cybersecurity Program - Dealer Members 2026
- CSA Staff Notice 33-322 - Registered Firm Cybersecurity 15 July 2026
Works with the rest of the platform
Shadow IT discovery
See the unsanctioned apps and AI tools in use before they become an incident.
Learn more →GRC & compliance automation
Run your AI frameworks alongside your security and privacy frameworks in one engine.
Learn more →Trust Centre
Publish your responsible-AI commitments where prospects and clients can see them.
Learn more →Common questions
- Which AI frameworks does Lavawall support?
- Five AI-specific frameworks: the NIST AI Risk Management Framework, ISO/IEC 42001, EU AI Act readiness, the OWASP Top 10 for LLM Applications, and Canadian AI governance. They share one control set with the rest of the frameworks Lavawall supports, so a control you satisfy once counts across every framework it maps to.
- What other frameworks does Lavawall support besides the AI ones?
- Over 75 in all, across security and governance, privacy, payment card, energy and critical infrastructure, government, healthcare, and financial services. They include SOC 2, ISO 27001, NIST CSF, CIS Controls, CMMC 2.0, PCI DSS, HIPAA, PIPEDA, and Quebec’s Law 25. See the full list.
- How does Lavawall know which framework I need?
- Lavawall detects the AI tools already in use across your connected security and IT tools, then recommends the framework that fits your situation automatically. You are not left guessing which standard applies.
- What is shadow AI and why does it matter?
- Shadow AI is any AI tool your staff adopt on their own, without review, often pasting company or client data into them. It creates data-leakage and compliance risk you cannot see. Lavawall surfaces the AI already in your environment so you can govern it.
- Do I need an AI expert to use this?
- No. Lavawall recommends the right framework, generates the matching policies and disclosures, and explains each step in plain language, so a small team can stand up credible AI governance without hiring a specialist.
- Does adopting one framework help with the others?
- Yes. Because the frameworks share one control set, progress on one framework advances the others at the same time, including your security and privacy frameworks.