See how ModelOp's public claims connect to security requirements and CIS Critical Security Controls references.
What this page shows
Requirements connected to ModelOp's public claims
Only requirements with strong or limited public support appear. The framework references identify what to investigate; they do not establish implementation, conformance, certification, or product effectiveness.
Versionv8.1 with 2026 AI Companion GuidesCurrent source
Related requirements7security questions in this research
Security requirements with public support4strong or limited public support
References35identifiers, clauses, safeguards, or categories
How to use this map
Framework connections help structure your evaluation
Each connection shows how a security requirement relates to this framework. Public vendor claims are shown separately, and deployed effectiveness still requires confirmation or testing.
Contributes
6
Related context
1
Official companion guidance
Use the guide for the AI technology being assessed
These guides interpret CIS Controls v8.1 for large language model (LLM), AI agent, and Model Context Protocol (MCP) environments. They are not vendor scorecards.
Maintain an inventory of AI tools, services, models, agents, software as a service (SaaS) AI capabilities, data flows, and provider relationships.
Framework references
2.1Establish and Maintain a Software InventoryIG1+
3.8Document Data FlowsIG2+
15.1Establish and Maintain an Inventory of Service ProvidersIG1+
Lifecycle
Govern · Identify · Monitor
Security requirements with public support
1 requirement with public support
Companion-guide relevanceLLMAgentMCP
Project-curated baseline alignment. CIS inventories software, data flows, and service providers; the AI-specific asset model comes from the linked large language model (LLM), Agent, and Model Context Protocol (MCP) companion guides.
Strong public supportApproved AI usage monitoring
Monitor approved AI workspaces, tenants, gateways, and model platforms such as ChatGPT Enterprise, Claude Enterprise, Gemini, Microsoft Copilot, Vertex AI, Elvex, or internal AI gateways.
Public claims reviewed
1
Next question to verify
Approved AI workspace activity appears with user, workspace or tenant, model or provider, and timestamp.
Monitor AI usage, user activity, prompts, responses, provider calls, runtime actions, and anomalous behavior.
Framework references
8.2Collect Audit LogsIG1+
8.5Collect Detailed Audit LogsIG2+
8.9Centralize Audit LogsIG2+
8.11Conduct Audit Log ReviewsIG2+
Lifecycle
Monitor · Detect · Operate
Security requirements with public support
2 requirements with public support
Companion-guide relevanceLLMAgentMCP
Project-curated baseline alignment. These safeguards establish audit-log collection, detail, centralization, and review; AI telemetry scope must still be confirmed.
Strong public supportApproved AI usage monitoring
Monitor approved AI workspaces, tenants, gateways, and model platforms such as ChatGPT Enterprise, Claude Enterprise, Gemini, Microsoft Copilot, Vertex AI, Elvex, or internal AI gateways.
Public claims reviewed
1
Next question to verify
Approved AI workspace activity appears with user, workspace or tenant, model or provider, and timestamp.
Prevent sensitive data exposure through prompts, responses, files, retrieval, memory, embeddings, or AI-connected workflows.
Framework references
3.2Establish and Maintain a Data InventoryIG1+
3.3Configure Data Access Control ListsIG1+
3.8Document Data FlowsIG2+
3.10Encrypt Sensitive Data in TransitIG2+
3.11Encrypt Sensitive Data at RestIG2+
3.13Deploy a Data Loss Prevention SolutionIG3+
3.14Log Sensitive Data AccessIG3+
Lifecycle
Protect · Operate · Monitor
Security requirements with public support
1 requirement with public support
Companion-guide relevanceLLMAgentMCP
Project-curated baseline alignment. CIS data safeguards provide the operational baseline; AI prompt, response, retrieval, memory, and embedding coverage still requires product-specific evidence.
Strong public supportApproved AI usage monitoring
Monitor approved AI workspaces, tenants, gateways, and model platforms such as ChatGPT Enterprise, Claude Enterprise, Gemini, Microsoft Copilot, Vertex AI, Elvex, or internal AI gateways.
Public claims reviewed
1
Next question to verify
Approved AI workspace activity appears with user, workspace or tenant, model or provider, and timestamp.
Related contextSpecific reference · research-team interpretation
AI governance, risk, and compliance operations
Maintain accountable AI inventory, policy, risk assessments, approvals, exceptions, regulatory mappings, third-party oversight, and audit evidence across the AI lifecycle.
Framework references
2.1Establish and Maintain a Software InventoryIG1+
14.1Establish and Maintain a Security Awareness ProgramIG1+
15.2Establish and Maintain a Service Provider Management PolicyIG2+
17.1Designate Personnel to Manage Incident HandlingIG1+
Lifecycle
Govern · Identify · Assess · Approve · Monitor
Security requirements with public support
2 requirements with public support
Companion-guide relevanceLLMAgentMCP
Project-curated operational baseline only. CIS supports inventory, awareness, provider policy, and incident ownership, but it does not replace an AI management system or regulatory assessment workflow.
Strong public supportAI governance, risk, and compliance
Inventory AI systems and owners, translate policy and regulatory obligations into governed workflows, assess risk, manage approvals and exceptions, and retain audit evidence across the AI lifecycle.
Public claims reviewed
1
Next question to verify
A test AI system is registered with owner, intended use, risk tier, lifecycle state, and applicable obligations.
Monitor approved AI workspaces, tenants, gateways, and model platforms such as ChatGPT Enterprise, Claude Enterprise, Gemini, Microsoft Copilot, Vertex AI, Elvex, or internal AI gateways.
Public claims reviewed
1
Next question to verify
Approved AI workspace activity appears with user, workspace or tenant, model or provider, and timestamp.
AI assurance, red teaming, and supply-chain security
Test models, applications, retrieval-augmented generation (RAG) systems, agents, coding workflows, and AI artifacts before release and continuously thereafter, with reproducible findings and remediation gates.
Framework references
16.1Establish and Maintain a Secure Application Development ProcessIG2+
16.2Establish and Maintain a Process to Accept and Address Software VulnerabilitiesIG2+
16.4Establish and Manage an Inventory of Third-Party Software ComponentsIG2+
16.6Establish and Maintain a Severity Rating System and Process for Application VulnerabilitiesIG2+
16.10Apply Secure Design Principles in Application ArchitecturesIG2+
16.12Implement Code-Level Security ChecksIG3+
16.13Conduct Application Penetration TestingIG3+
Lifecycle
Develop · Test · Release · Monitor
Security requirements with public support
1 requirement with public support
Companion-guide relevanceLLMAgentMCP
Project-curated baseline alignment. Secure development, component inventory, code checks, and penetration testing support assurance; AI red-team methods and model artifacts require additional evidence.
Limited public supportAI assurance and adversarial testing
Test models, applications, retrieval-augmented generation (RAG) systems, and agents before release and continuously thereafter using adversarial probes, evaluation suites, attack simulation, and security release gates.
Public claims reviewed
1
Next question to verify
A controlled test campaign exercises an AI model, application, or agent against named AI attack classes.
Observe agent steps, plans, goals, memory, delegation, tool use, and anomalies during runtime.
Framework references
8.2Collect Audit LogsIG1+
8.5Collect Detailed Audit LogsIG2+
8.9Centralize Audit LogsIG2+
8.11Conduct Audit Log ReviewsIG2+
Lifecycle
Operate · Monitor · Detect
Security requirements with public support
1 requirement with public support
Companion-guide relevanceAgentMCP
Project-curated baseline alignment. Audit-log safeguards support telemetry operations; the Agent and Model Context Protocol (MCP) guides supply the relevant AI runtime interpretation.
Limited public supportAction-taking agent monitoring
Observe and govern agent plans, memory, tool calls, delegated tasks, autonomy, runtime decisions, and outcomes.
Public claims reviewed
1
Next question to verify
A test agent run captures plan, steps, tool calls, outcome, and timestamps.
Secure trust, authorization, message flows, tool access, and communication between agents, tools, application programming interfaces (APIs), and external services.
Framework references
5.1Establish and Maintain an Inventory of AccountsIG1+
6.1Establish an Access Granting ProcessIG1+
6.2Establish an Access Revoking ProcessIG1+
6.5Require MFA for Administrative AccessIG1+
6.8Define and Maintain Role-Based Access ControlIG3+
8.2Collect Audit LogsIG1+
Lifecycle
Identify · Protect · Deploy · Monitor
Security requirements with public support
1 requirement with public support
Companion-guide relevanceAgentMCP
Project-curated baseline alignment. Account, access, administrative MFA, role, and log safeguards support agent-to-tool trust; protocol-specific authorization still requires Model Context Protocol (MCP) and product evidence.
Limited public supportAction-taking agent monitoring
Observe and govern agent plans, memory, tool calls, delegated tasks, autonomy, runtime decisions, and outcomes.
Public claims reviewed
1
Next question to verify
A test agent run captures plan, steps, tool calls, outcome, and timestamps.
This page organizes research. Audit conclusions, certification assessments, control implementation statements, and vendor endorsements require separate evidence.