Standards & Regulations
Built on the standards auditors require
FIOR AI Gateway aligns with FIPS, ISO, SOC 2, EU AI Act, NIST AI RMF, GDPR and NIS2, so you can deploy autonomous AI without rewriting your compliance programme.
Framework Coverage
Each framework is mapped to specific FIOR controls. Request the full compliance pack for auditor-ready evidence.
FIPS 204
NIST · USA
ML-DSA (CRYSTALS-Dilithium)
Status: Aligned
Post-quantum digital signatures used to sign every agent certificate. NIST Level 3 security.
- ML-DSA-65 signature generation and verification
- Quantum-safe certificate chain from Root CA to agent leaf
- Algorithm metadata exposed in every validate-certificate response
FIPS 203
NIST · USA
ML-KEM (CRYSTALS-Kyber)
Status: Aligned
Post-quantum key encapsulation for protecting session keys against harvest-now-decrypt-later attacks.
- ML-KEM-768 key exchange supported on gateway TLS termination
- Hybrid X25519 + ML-KEM mode for transitional deployments
FIPS 205
NIST · USA
SLH-DSA (SPHINCS+)
Status: Aligned
Stateless hash-based signatures available as a conservative backup signing algorithm for highest-assurance environments.
- SLH-DSA available as alternate Root CA signing scheme
- NIST Level 5 security parameter set supported
FIPS 140-3
NIST · USA
Cryptographic Module Validation
Status: In Progress
FIOR.Gateway is designed for deployment alongside FIPS 140-3 validated HSMs and KMS providers (AWS CloudHSM, Azure Managed HSM, Thales Luna).
- External HSM integration for Root CA private key custody
- No private keys stored in application memory in HSM mode
- Validated cryptographic primitives via OpenSSL FIPS provider
ISO/IEC 27001
ISO · International
Information Security Management
Status: Aligned
FIOR controls map directly to Annex A requirements for access control, cryptography, logging, and supplier security.
- A.5.15 Access control — per-agent certificate-based identity
- A.8.24 Use of cryptography — quantum-safe key management
- A.8.15 Logging — tamper-evident hash-chained audit trail
- A.5.21 Information security in the ICT supply chain — agent provenance
ISO/IEC 27002:2022
ISO · International
Security Controls Code of Practice
Status: Aligned
Implementation guidance for the Annex A controls referenced by ISO 27001, including the new attribute-based control taxonomy.
- Preventive, detective, and corrective controls across the gateway
- Identity, cryptography, and threat intelligence attributes
ISO/IEC 42001
ISO · International
AI Management System
Status: Aligned
The first international standard for AI governance. FIOR provides the technical enforcement layer for AI risk controls.
- AI system inventory via certificate registry
- Continuous monitoring of AI agent behaviour
- Documented incident response for AI-related events
SOC 2 Type II
AICPA · USA
Trust Services Criteria
Status: Aligned
FIOR supports the Security, Availability, Confidentiality and Processing Integrity trust services criteria.
- CC6.1 Logical access controls — certificate-bound identity
- CC7.2 System monitoring — real-time gateway events
- CC7.3 Incident detection — automated quarantine pipeline
NIST AI RMF 1.0
NIST · USA
AI Risk Management Framework
Status: Aligned
Maps to the govern, map, measure and manage functions for autonomous AI systems.
- GOVERN — Documented AI agent ownership via operator binding
- MAP — Per-agent capability and constraint declaration
- MEASURE — Continuous traffic and policy compliance metrics
- MANAGE — Sub-second revocation and incident response
EU AI Act
European Union
Regulation (EU) 2024/1689
Status: Aligned
FIOR provides the technical controls required for high-risk AI systems under Articles 9, 12, 14, 15 and 50.
- Article 9 — Risk management with continuous anomaly scoring
- Article 12 — Automatic record-keeping (audit logs)
- Article 14 — Human oversight via instant revocation
- Article 15 — Accuracy, robustness, and cybersecurity
- Article 50 — AI system identification (certificate-based)
GDPR
European Union
General Data Protection Regulation
Status: Aligned
Domain restriction and data sovereignty controls support GDPR-compliant AI agent deployments.
- Article 32 — Security of processing (encryption, access control)
- Article 25 — Data protection by design
- Per-certificate domain allow-lists prevent unauthorised data egress
NIS2 Directive
European Union
Network and Information Security 2
Status: Aligned
Supports incident detection, reporting and supply-chain security obligations for essential and important entities.
- Real-time incident detection and 24-hour reporting workflow
- Supply-chain integrity via certificate provenance
Common audit questions
Quick answers to the questions auditors and security teams ask most often about FIOR’s cryptographic posture and regulatory scope.
Yes. FIOR’s cryptographic stack supports the NIST post-quantum standards: FIPS 203 (ML-KEM) for key encapsulation, FIPS 204 (ML-DSA) for digital signatures, and FIPS 205 (SLH-DSA) as a stateless hash-based signature alternative.
These are used for agent identity certificates, mutual authentication handshakes and policy signing, providing quantum-safe protection against “harvest now, decrypt later” attacks on AI agent traffic.
Yes. Policies can require hybrid suites that combine ECDSA/RSA with ML-DSA, or ECDH with ML-KEM, so deployments stay interoperable with legacy PKI while gaining quantum resistance. Enforcement is per-policy and can be tightened over time.
FIOR is designed to operate with FIPS 140-3 validated cryptographic modules. Customers requiring validated modules deploy FIOR against an approved provider (e.g. a FIPS-validated OpenSSL provider, HSM or cloud KMS) and FIOR consumes its primitives through that boundary.
Validation status of any specific deployment is determined by the chosen module and operating environment. We provide a configuration guide and module attestation references in the compliance pack.
Agent identity keys are bound to hardware roots of trust where available: TPM 2.0 on Linux/Windows hosts, Secure Enclave on macOS, and network HSM / cloud KMS for gateway and CA keys. PCR measurements are included in attestation evidence.
FIOR operates at the network and identity layer. It authenticates agents, signs policies and records connection metadata (agent ID, certificate serial, timestamp, decision). It is not designed to inspect or store the content of agent payloads.
Where metadata constitutes personal data (e.g. an agent acting on behalf of an identified user), FIOR acts as a processor under the customer’s instructions. A DPA, records-of-processing template and data-flow diagram are included in the GDPR compliance pack.
Yes. FIOR is offered as a self-hosted gateway (K3s/Kubectl) and can run entirely within customer infrastructure or a chosen cloud region. No agent traffic or audit logs leave the customer boundary unless explicitly configured.
For essential and important entities under NIS2, FIOR contributes to Article 21 risk-management measures – cryptography and access control, supply-chain security (signed agent identities) and incident detection, and supports Article 23 incident reporting through the audit and incident pipeline (early warning, 24h / 72h notifications, final report evidence).
Yes. Every agent, internal or third-party, must present a valid X.509 identity issued under your policy. Revocation propagates network-wide in milliseconds, so a compromised supplier agent can be cut off without redeploying applications.
The framework-specific Compliance Pack typically covers initial auditor walkthroughs without bespoke documentation.