Compliance

This page captures the compliance posture Aurora MCP inherits from the wider Consilio platform, plus the MCP-specific controls a procurement team will want to confirm.

Inherited from the Consilio platform

Aurora MCP runs inside the same hosting environment as the Consilio portal and eDiscovery platform. It inherits the parent platform’s certifications and third-party attestations, including:

• SOC 2 Type II — annual report, available under NDA.
• ISO/IEC 27001 — Information Security Management System.
• HIPAA — Business Associate Agreements available where applicable.
• GDPR — EU data handling, DPA available.

For copies of the current reports and attestations, contact your Consilio account team.

MCP-specific controls

On top of the inherited posture, Aurora MCP adds:

Control	Detail
Auth protocol	OAuth 2.1 with PKCE (S256), RFC 8707 Resource Indicators, RFC 9728 Protected Resource Metadata
Identity provider	ConsilioId (Duende IdentityServer Enterprise)
Token validation	Envoy Gateway (audience, scope, signature) — token never reaches the MCP server
Network isolation	Kubernetes NetworkPolicy — only gateway data-plane pods can reach the MCP server
Tool posture	Read-only; no write/update/delete tools exist
Prompt retention	None
Tool-output retention	None
Operational logging	Tool name, latency, status, caller sub — short retention, used for abuse detection

What Aurora MCP doesn’t change

Using Aurora MCP doesn’t alter your data-processing agreement with Consilio, and it doesn’t alter your separate terms with your AI assistant provider. Data that leaves the MCP server to answer a prompt is subject to the processing terms of your chosen assistant’s plan.

Questions

For due-diligence questionnaires, SIG/CAIQ responses, or architecture deep-dives, email security@consilio.com with your organisation name and timeline.