> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neuraltrust.ai/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> These docs cover three products: TrustGate (AI agent gateway), TrustGuard (runtime security), and TrustTest (AI red teaming). Start from each product overview for the definition and How it works. Prefer the .md URL next to a page in /llms.txt when you need the full article. Use /llms-full.txt for a single-file dump of the site.
# ISO/IEC 42001
> How TrustGate and TrustGuard produce evidence for an ISO/IEC 42001 AI management system, clause by clause and control by control.
ISO/IEC 42001 certifies **your** AI management system, and the certification is
yours to hold. NeuralTrust supplies the operational evidence and enforcement it
rests on.
## Coverage at a glance
| Clause | Requirement | Coverage |
| ------ | ---------------------- | :------------------- |
| **4** | Context | 🟢 Partially covered |
| **5** | Leadership | 🟢 Partially covered |
| **6** | Planning | ✅ Covered |
| **7** | Support | 🟢 Partially covered |
| **8** | Operation | ✅ Covered |
| **9** | Performance evaluation | ✅ Covered |
| **10** | Improvement | 🟢 Partially covered |
## Clauses 4 to 10
| Clause | What it asks | What NeuralTrust contributes |
| ------------------------------ | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **4 — Context** | Understand your AI footprint and interested parties | The [Registry](/trustgate/registry/overview) inventories what each gateway may reach: [model providers](/trustgate/registry/models) on the LLM plane, [MCP servers](/trustgate/registry/mcp) on the MCP plane, each an entry plus the credential that reaches it |
| **5 — Leadership** | Policy, roles, accountability | [Roles and permissions](/platform/users) per product, [SSO](/platform/sso) and [SCIM provisioning](/platform/scim), and [break-glass](/platform/break-glass) as the auditable emergency path |
| **6 — Planning** | Risk assessment and treatment | The [detector catalog](/trustguard/detectors/overview) defines what is looked for; [TrustGuard](/trustguard/concepts/policies) and [TrustGate](/trustgate/policies/overview) policies apply the treatment, each with an **Observe** mode that measures before it enforces |
| **7 — Support** | Resources, competence, documented information | [Audit logs](/platform/audit-logs) and TrustGuard findings as retained documented information |
| **8 — Operation** | Operational planning and control | The gateway is the control point: [policies](/trustgate/policies/overview) decide budgets, rate limits, what may be said and which tools may run, scoped by who calls and what they touch; [access levels](/trustgate/access/overview) decide who reaches which server |
| **9 — Performance evaluation** | Monitoring, measurement, analysis | [Alerts](/platform/alerts) across both products with correlation and deduplication, and [SIEM forwarding](/platform/alert-integrations) as OCSF Detection Findings |
| **10 — Improvement** | Nonconformity and corrective action | Findings carry the detector, the side, the decision and its evidence; [policy history](/trustguard/concepts/policies#history) records what changed and when |
## Annex A controls
| Control | Evidence |
| -------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **A.5 — Assessing impacts of AI systems** | Findings per policy and detector, with severity and evidence summary |
| **A.6 — AI system life cycle** | Request-level records through the gateway, with [end-user attribution](/trustgate/observability/end-user-attribution) tying traffic behind a shared key to the person a client was serving |
| **A.7 — Data for AI systems** | [Data Loss Prevention](/trustguard/detectors/data-loss-prevention) detects PII and secrets on input and output, and masks them where the Transform action is set; [credential redaction](/trustguard/data-handling#credential-redaction) runs before any record is written |
| **A.8 — Information for interested parties** | ⚪ Not covered — neither product enforces AI-identity disclosure |
| **A.9 — Responsible use of AI systems** | Enforced [guardrails](/trustgate/policies/guardrails), [rate limits](/trustgate/policies/rate-limiter), [budgets](/trustgate/policies/llm-budget) and [request size limits](/trustgate/policies/request-size-limiter) |
| **A.10 — Third-party relationships** | The [Registry](/trustgate/registry/overview) bounds every provider and MCP server a gateway may reach; [Indirect Prompt Injection](/trustguard/detectors/agent-mcp-security) inspects what a third-party tool returns, and its tool descriptions |
## Residency
Clause 8 and Annex A.7 both turn on where records live, which your deployment
decides:
| Deployment | Where records live |
| ------------------------ | -------------------------------------------------------- |
| **Self-hosted / hybrid** | Your own infrastructure, entirely |
| **SaaS** | The NeuralTrust region your workspace was provisioned in |
On hybrid, evaluated traffic never leaves your perimeter — the link back to
NeuralTrust carries configuration only. On SaaS the region is fixed at
provisioning. See [Data handling](/trustguard/data-handling).
## Your evidence pack
* **Inventory** — registry entries for model providers and MCP servers per gateway.
* **Control configuration** — the policy set in force, its mode and its scope.
* **Operating evidence** — findings, and the request bodies behind them, credential-redacted and capped at 1 MiB.
* **Administrative trail** — [audit logs](/platform/audit-logs) retained 365 days, exportable as CSV or JSON.
* **Retention statement** — every record carries its retention plan and an absolute expiry stamped when written.
## Where NeuralTrust stops
Clauses 4, 5, 7 and 10 are partly covered because the rest is organizational:
scoping and stakeholder analysis, writing your AI policy, competence records, and
the corrective-action process itself. Annex A.8 is not covered at all.
Clause and Annex A identifiers do not ship as tags on findings. This page is the
mapping.
See also [EU AI Act](/platform/compliance/eu-ai-act), [OWASP LLM Top 10](/platform/compliance/owasp-llm-top-10) and [NIST AI RMF](/platform/compliance/nist-ai-rmf).