--- title: "Security & Compliance" description: "Enterprise controls in Norcaster: MFA, SSO/OIDC, signed audit exports, and GDPR data subject rights endpoints." canonical: https://www.norcaster.com/docs/security-compliance --- # Security & Compliance The operational reference for the enterprise-facing security controls implemented in Norcaster today: identity and access, data protection, runtime evidence integrity, operational controls, signed audit exports, and GDPR data-subject rights. Contractual posture, subprocessors, and the disclosure policy live in the Trust Center. ## Identity & access - MFA (TOTP) per user with recovery codes and disable flow. - Organization MFA requirement to enforce MFA for org-scoped API access. - API key scopes, optional expiry, revoke timestamp, and last-used audit fields. - Scoped OIDC SSO with optional password-login enforcement by organization. ## Data protection posture On **supported runtime paths** (see [EU AI Act readiness](https://www.norcaster.com/docs/eu-ai-act-readiness)), teams can correlate policy decisions, enforcement events, and traces — including what was blocked or redacted before a model call. In workflow use cases, PII controls should run before model nodes. For self-hosted deployments, raw source data can remain inside the customer-controlled network boundary. Company and hosting note Norcaster is owned by Navego AB, Lillängsvägen 21, 131 41 Nacka, Stockholm, Sweden. Deployment options include managed operation and self-hosting. For strict data residency requirements, confirm the selected hosting region and provider configuration before production rollout. ## Runtime evidence integrity - Enforcement and run-seal events append to a per-tenant hash-chained trace store — each entry carries the digest of the prior entry, so undetected alteration breaks the chain. - Completed segments are batched into Merkle trees and their roots published to the public Sigstore Rekor log, so reviewers can confirm anchors independently — no Norcaster login or trust required. - Audit bundles export as manifest-led PDF / CSV / JSON with a HOW\_TO\_VERIFY guide and a standalone verification script. Verification steps and anchor lookup are documented on [Evidence integrity](https://www.norcaster.com/trust/integrity) in the Trust center; the model is explained on [How proof works](https://www.norcaster.com/evidence). ## Access & operational controls - Role-based access separates engineering, governance, leadership, and reviewer permissions per organization. - A scoped, time-boxed `external_reviewer` role gives auditors and buyers the AI register, evidence, and audit bundles, and is refused the member directory, access audit, projects, the organization's policies and retention settings, and provider, knowledge, alert, and data-plane configuration. - Deployment stop and resume are audited lifecycle controls — each action is recorded with actor identity. - Provider failover events are recorded on the enforcement spine, so per-request provider attribution survives routing shifts. Posture summary and current certification status: [Security & Trust posture](https://www.norcaster.com/security). ## Signed audit exports Enforcement-event JSONL can be exported with hash chain and trailing HMAC signature metadata. When per-tenant signing is enabled for your organization, the trailer also carries an ES256 signature from your organization's key over the chain tail, with the public key embedded, so a third party can verify it without a Norcaster secret. The verify endpoint reports both signatures separately; an export without the tenant block is valid but not tenant-signed. ``` curl "https://api.norcaster.com//enforcement-events/export?deployment_id=DEPLOYMENT_ID&format=jsonl&signed=true" \ -H "X-API-Key: YOUR_API_KEY" ``` ``` curl -X POST "https://api.norcaster.com//audit/verify-signed-export" \ -H "X-API-Key: YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"lines":["{...signed jsonl line 1...}","{...line 2...}","{...signature block...}"]}' ``` Note: signed export requires \`AUDIT\_SIGNING\_KEY\`. ## GDPR data subject rights Self-service export and erasure are available via authenticated auth endpoints. ``` curl "https://api.norcaster.com//auth/gdpr/export" \ -H "X-API-Key: YOUR_API_KEY" ``` ``` curl -X POST "https://api.norcaster.com//auth/gdpr/delete" \ -H "X-API-Key: YOUR_API_KEY" ``` Erasure is blocked with \`409\` when the user is the sole owner of any organization. Readiness, not legal compliance Norcaster provides runtime policy enforcement and exportable evidence on **supported production paths** to help teams build **EU AI Act readiness** and broader AI governance workflows. It is **not** legal advice, a conformity assessment, CE marking, or a guarantee of regulatory compliance. Risk classification, DPIAs, and legal interpretation remain your responsibility. [Supported paths & evidence APIs →](https://www.norcaster.com/docs/eu-ai-act-readiness) · [Trust center →](https://www.norcaster.com/trust) ## Trust center Hosting, subprocessors, SOC 2 / ISO posture, and audit evidence are summarized on the [Trust center](https://www.norcaster.com/trust) page (aligned with this document). The live subprocessor register is also available as [machine-readable JSON](https://www.norcaster.com/api/compliance/subprocessors). ## Common questions ### Does Norcaster store prompts? Norcaster stores execution and audit data needed for traces, enforcement events, and visibility. For privacy-sensitive workflows, use redaction before model calls and review retention settings for your deployment model. ### Can I export audit evidence? Yes. Enforcement exports and signed audit exports are available when signing is configured. Workflow analysis can also export compliance evidence for redaction proof. [Use traces and run history for investigations →](https://www.norcaster.com/docs/observability) ### What about subprocessors? Norcaster publishes a versioned subprocessor register for managed hosting and platform services. Customer- configured model providers (Anthropic, OpenAI, Azure OpenAI, Bedrock, Voyage AI, etc.) are listed when applicable but are part of your own data flow when you connect them. Live register: [Trust center](https://www.norcaster.com/trust/subprocessors) · [JSON API](https://www.norcaster.com/api/compliance/subprocessors) · [/subprocessors.json](https://www.norcaster.com/subprocessors.json)