Skip to main content

AI/ML / Multi Agent Refarch / Controls / DEV

Legal and Contractual Frameworks for AI Systems

CCC.MARefArc.CN05 · PREV

Establish contractual controls with model and MCP service providers covering data handling, retention and deletion, intellectual property, liability, and supply-chain integrity.

Related Capabilities

IDTitleDescription
CCC.MARefArc.CP21Human supervision and oversightMechanisms for human reviewers to inspect, approve, correct, or override agent outputs, supporting human-in-the-loop and human-over-the-loop workflows for sensitive or high-impact tasks.
CCC.MARefArc.CP05Agent-ingress zero-trust guardrailsTreats all inputs as untrusted and enforces authentication, authorization, input validation, content filtering, access control, rate limits, and dynamic policy before any request reaches an agent.
CCC.MARefArc.CP02Human-in-the-loop output reviewApplication-embedded controls that allow users to review, approve, or modify agent outputs before they are executed or shared.
CCC.MARefArc.CP01User-facing application surfacePresentation and orchestration surface (web, mobile, chatbot, workflow tool, or integrated enterprise system) that captures user intent, forwards requests to the agent layer, and returns agent outputs.
CCC.MARefArc.CP16Model-interaction zero-trust guardrailsEnforces authentication and authorization for every inference request and applies input validation against prompt injection, output filtering and redaction, access control, rate limits, and cost management before and after model execution.
CCC.MARefArc.CP14Approved-model registry and lifecycleCatalog of approved models with metadata, version information, configuration parameters, and usage constraints, ensuring agents access only models meeting organizational, regulatory, and security standards.
CCC.MARefArc.CP22Runtime protectionMonitors agent actions and model outputs during execution to detect unsafe, non-compliant, or anomalous behavior, enforcing constraints, blocking disallowed actions, or triggering escalation.

Related Threats

IDTitleDescription
CCC.MARefArc.TH25Non-compliant outputs and model-risk-management gapsAI-generated advice, marketing, or communications that fail KYC, suitability, disclosure, record-keeping, or model-risk-management expectations create regulatory exposure; weak supervision and accountability lines turn this into direct non-compliance.
CCC.MARefArc.TH26Intellectual-property leakage and licensing violationsOutputs may replicate copyrighted training material, employees may leak trade secrets into AI tools, and improper platform licensing or terms-of-service violations create contractual and legal liability.
CCC.MARefArc.TH01Model memorization leaks sensitive data across sessionsThe hosted models accessed through the LLM layer may memorize sensitive inputs or training data and later disclose customer PII, proprietary algorithms, or trading strategies, including cross-user leakage into unrelated sessions.
CCC.MARefArc.TH02Hosted-provider data-handling exposureSensitive data submitted through the LLM gateway to third-party hosted models is exposed when the provider lacks transparent encryption, retention limits, or secure-deletion guarantees, leaving the institution without control over data it no longer holds.
CCC.MARefArc.TH20Model supply-chain tamperingAdversaries tamper with training data, weights, GPU firmware and operating systems, cloud orchestration, or ML libraries in the provider pipeline, embedding manipulations that are difficult to detect downstream of the LLM gateway.
CCC.MARefArc.TH21Backdoor triggers and safety-mechanism disablementWhere weights are accessible, adversarial fine-tuning, engineered trigger phrases, or tampering disables alignment and content-moderation safeguards, causing targeted unsafe behaviour under specific conditions.
CCC.MARefArc.TH15Reputational harm from offensive or misleading outputsThe system generates offensive, misleading, or inappropriate outputs, or is manipulated into doing so, that are attributed to the organization, with reputational and regulatory impact when output filtering and human review are insufficient.

Assessment Requirements

IDTextApplicability
CCC.MARefArc.CN05.AR01Every approved model and MCP server provider MUST be governed by a contract specifying data handling, retention and deletion, and intellectual-property terms before it is added to the registry.tlp-clear, tlp-green, tlp-amber, tlp-red
CCC.MARefArc.CN05.AR02Provider contracts MUST include supply-chain integrity and breach-notification obligations.tlp-clear, tlp-green, tlp-amber, tlp-red

Guideline Mappings

FrameworkIDRemarks
finos-airAIR-PREV-007