neural-bridge.dev
/ Compliance & Risk · Working Paper · v0.2 · 9 min read

AI Security Regulation in 2026: What Practitioners Need to Know

By Andy Herman

TL;DR. Four jurisdictions matter for most working practitioners: the EU (most prescriptive, AI Act fully applicable August 2026), the US federal level (NIST AI RMF, voluntary but de-facto standard), US states (fragmented; Colorado is the test case, June 30 2026), and the UK (third path). For most teams, your AI compliance is the intersection of one of these AI-specific regulations and your sector regulations (HIPAA, DORA, NIS2, GDPR). NIST AI RMF + ISO/IEC 42001 cover the largest fraction of every other framework. Personal projects are mostly out of the regulatory net.

Skip to your situation

If you…Read this section
Sell into the EU at allThe EU AI Act
Are US-based, building any AI productNIST AI RMF
Sell into Colorado or any other US stateUS state-level regulation
Need a certification you can show enterprisesISO/IEC 42001
Are in finance, healthcare, or critical infrastructureSector-specific overlays
Are building a personal AI projectWhat this means for personal projects
Want to know what to actually do this quarterHow they intersect

If you build, deploy, or use AI in production right now, you’re being regulated by people you’ve never met. Some of those regulations took effect this year. More are coming. The landscape is fragmented, fast-moving, and sometimes contradictory across regulators. It’s also the most consequential thing happening in cybersecurity policy in a generation.

This piece is the lay of the land as of mid-2026. It is not legal advice. It is a working practitioner’s map of what exists, who it applies to, and what it actually changes about how you build.

The four jurisdictions that matter

For most practitioners working with AI in 2026, four jurisdictions matter:

  1. The European Union, by far the most prescriptive, anchored by the AI Act
  2. The US federal government, voluntary frameworks (NIST AI RMF) and sector-specific rules
  3. US states, fragmented, growing fast, Colorado is the test case
  4. The UK and Commonwealth, a third path between the EU and US approaches

The EU AI Act

Skip if: you have zero EU exposure (no EU customers, no EU users, no EU employees touching the AI). Otherwise read.

The EU AI Act is the world’s first comprehensive AI regulation. It entered force in August 2024 and is fully applicable in August 2026. Some categories of high-risk AI got a transition extension to December 2027 in the recent Digital Omnibus amendment.

The Act’s core mechanism is risk tiering:

TierWhat it coversCompliance weight
ProhibitedSocial scoring by governments, certain biometric ID, manipulative AI exploiting vulnerable groupsIn effect since Feb 2025. You either don’t do these, or you stop.
High-riskHiring software, credit scoring, medical AI, education assessment, infrastructure safety. Annex III is the official list.Heavy. Documentation, risk management, human oversight, conformity assessment, CE marking.
Limited riskChatbots, emotion-recognition systemsMostly transparency obligations.
Minimal riskMost AI applicationsVoluntary codes of conduct.

For practitioners, the questions are concrete:

  1. Are you a “provider” or a “deployer”? Different obligations.
  2. Is your AI on the high-risk list (Annex III)? If yes, the heavy compliance kicks in.
  3. Are you using a General-Purpose AI model (a foundation model)? Specific obligations have applied to those since August 2025.

The penalty structure is stiff. Up to €35M or 7% of global annual turnover for prohibited-use violations. Up to €15M or 3% for other violations. The pattern (and the percentages) will sound familiar to anyone who lived through GDPR. That is not an accident.

If you operate in or sell into the EU and your AI does anything in the high-risk list, you should already be deep in this. If your AI is generic and doesn’t touch a high-risk domain, you have lighter obligations but real ones, particularly around transparency.

The US federal landscape: NIST AI RMF

Skip if: you have no US exposure. Otherwise this is your single most important framework.

The US doesn’t have a federal equivalent of the EU AI Act. What it does have is the NIST AI Risk Management Framework (AI RMF), originally released January 2023 and substantially expanded with the Generative AI Profile (NIST AI 600-1) in July 2024.

Three things to know:

  • It’s voluntary. No fines for not adopting it. But…
  • It’s the de-facto US standard. Federal agencies, federal contractors, and most large enterprises use it as their reference framework.
  • It’s structured around four functions: Govern, Map, Measure, Manage. You build a program that does all four; the details are organization-specific.

The Generative AI Profile adds 200+ specific suggested actions for managing GenAI-specific risks: confabulation, harmful content, privacy leaks, environmental impact, misuse.

Why does voluntary matter? Because state-level regulation is increasingly using NIST AI RMF as the baseline for what “reasonable” risk management means. Colorado’s AI Act explicitly accepts NIST conformance as an affirmative defense. Other state bills follow the same pattern.

If you operate in the US and want a single framework to orient around, this is it.

US state-level regulation

Skip if: you don’t sell software that makes consequential decisions about people in any US state. Otherwise read.

The US is regulating AI state by state. The pattern is fragmented and accelerating.

The most consequential is the Colorado AI Act (SB 24-205), which takes effect June 30, 2026 (delayed from February 2026). It applies to high-risk AI in employment, housing, education, healthcare, insurance, legal, and financial services. Key requirements:

  • Risk Management Program aligned with NIST AI RMF, ISO/IEC 42001, or another recognized framework
  • Impact assessments within 90 days of deployment, repeated annually and after major changes
  • Notice obligations to affected consumers
  • Right to appeal consequential decisions

Colorado is being watched as the test case. Other states with active bills or laws as of 2026 include New York (Local Law 144 on bias audits in hiring), Illinois, California (multiple proposals), and Texas. The contours differ; the direction of travel is one-way.

For practitioners: if you sell software that makes consequential decisions about people in any of these states, you have a compliance question even if you’re not based there.

ISO/IEC 42001

Skip if: you’re early-stage and not selling to enterprises that ask for certifications. Otherwise this is the most useful single thing to align toward.

ISO/IEC 42001:2023 is the first international standard for AI Management Systems. It’s the AI equivalent of ISO 27001 (information security) and ISO 9001 (quality management).

Why it matters: it is certifiable. Organizations can hire an accredited auditor, get certified to ISO 42001, and use that certification as evidence of responsible AI governance. Several regulations explicitly accept ISO 42001 conformance as compliance evidence, including the Colorado AI Act’s affirmative-defense clause.

For most companies: if you’re going to formalize an AI program, ISO 42001 is the closest thing to a recognized destination. Whether you certify or just align is a budget conversation.

Sector-specific overlays

Skip if: you’re a generic SaaS / developer tool with no regulated-industry customers. Read if any of HIPAA, DORA, NIS2, FedRAMP, or GDPR ring bells.

Most practitioners face regulations beyond the AI-specific ones above. The overlays that matter:

RegulationScopeWhat changed for AI
NIS2 (Network and Information Security Directive 2)EU; cybersecurity for critical infrastructure / essential servicesAI security falls within operational-security obligations. Member-state laws landing 2025-2026.
DORA (Digital Operational Resilience Act)EU financial servicesRequired ICT risk management, including AI used in financial decisions. In effect Jan 2025.
HIPAAUS healthcare privacyAI processing PHI is in scope. Security Rule maps onto AI risk management with new wrinkles around training data.
FedRAMPUS government cloud authorizationGenAI services for government use have additional requirements via the Emerging Technology Prioritization Framework.
GDPREU personal dataPredates AI but applies. Article 22 (automated decision-making) is suddenly very relevant.

For most teams, your AI compliance is the intersection of AI-specific regulations and your sector-specific regulations. The practical work is the joint mapping.

How they intersect

Real compliance for a US-based SaaS product with EU customers and an AI feature, in 2026, looks roughly like:

  1. Adopt NIST AI RMF as your internal framework.
  2. Map your AI features against the EU AI Act risk tiers. If anything is high-risk, plan for the August 2026 (or December 2027) deadline.
  3. Maintain impact assessments ready to show Colorado regulators if asked.
  4. Watch other states. Bills move fast.
  5. Layer sector overlays (HIPAA, DORA, etc.) where they apply.
  6. Consider ISO 42001 certification if you sell to enterprises that ask for it.

This is a lot, but tractable: most of these frameworks are designed to be compatible, not contradictory. A well-built NIST AI RMF program covers maybe 70% of what ISO 42001 wants and 60% of what the EU AI Act wants for high-risk systems.

That last 30-40% is non-trivial. It’s the part most companies don’t realize they’re missing until an audit.

What changes by team size and role

Team / roleWhat you should do this quarter
Solo / pre-PMFRead NIST AI RMF (4 hours). Don’t build a compliance program; just don’t actively trip the EU AI Act prohibited list or Colorado’s consequential-decision triggers.
Series A/B startup, EU customersRead the EU AI Act risk tiers (1 hour). Self-assess against Annex III. If any feature is high-risk, start the conformity-assessment conversation now.
Series A/B startup, US-onlyAdopt NIST AI RMF. Cover Govern + Map this quarter; Measure and Manage next quarter.
Mid-market, mixed jurisdictionsHire fractional GRC. ISO 42001 alignment is the cheapest path to multi-framework coverage. Certify when revenue demands it.
EnterpriseYou already have GRC. Make sure they have AI-specific subject-matter expertise. The generalist program won’t cover the GenAI Profile’s 200+ actions.
Personal / hobbyistMostly out of scope. Watch for the threshold where your project becomes a service to other people.

How to keep up

The landscape moves quarterly. Sources I recommend:

The big-block reads (AI Act, NIST AI RMF, ISO 42001) are 4-8 hours each. For ongoing tracking, the source list above is the shortcut.

What this means for personal projects like Neural Bridge

Personal projects are mostly out of the regulatory net. Building a personal AI substrate for your own use doesn’t trigger the EU AI Act or Colorado AI Act, because those target consequential decisions affecting other people. But two things to track:

  1. If Neural Bridge ever gets a public chat interface where users other than me input data, the limited-risk transparency obligations under the EU AI Act apply.
  2. If I ever monetize a service built on Neural Bridge, the rules tighten fast.

For now, Neural Bridge is in scope for OWASP’s technical guidance, out of scope for most AI regulation. That’s a comfortable place to build from, but I’m noting the threshold.

Further reading

See also