See how Keycard's public claims connect to security requirements and NIST AI RMF Playbook references.
What this page shows
Requirements connected to Keycard'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.
VersionAI RMF 1.0 PlaybookCurrent source
Related requirements10security questions in this research
Security requirements with public support7strong or limited public support
References30identifiers, 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.
Closely aligned
5
Contributes
5
Requirement connections
From Keycard's public claims to questions to verify
Each row starts with a security requirement that has public support, then shows the connected framework references and the next question to verify.
Closely alignedSpecific reference
AI usage inventory
Maintain an inventory of AI tools, services, models, agents, software as a service (SaaS) AI capabilities, data flows, and provider relationships.
Framework references
GOVERN 1.6 · MAP 1.1 · MAP 1.4
Lifecycle
Govern · Identify · Monitor
Security requirements with public support
1 requirement with public support
Limited 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
MEASURE 2.4 · MEASURE 3.1 · MANAGE 4.1
Lifecycle
Monitor · Detect · Operate
Security requirements with public support
2 requirements with public support
Limited 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
MEASURE 2.7 · MEASURE 2.10 · MANAGE 4.1
Lifecycle
Protect · Operate · Monitor
Security requirements with public support
1 requirement with public support
Limited 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.
Secure large language model (LLM) applications, retrieval-augmented generation (RAG) systems, prompts, tool calls, application programming interfaces (APIs), model interactions, and runtime behavior.
Framework references
MEASURE 2.7 · MEASURE 2.13 · MANAGE 4.1
Lifecycle
Develop · Test · Release · Deploy · Operate
Security requirements with public support
1 requirement with public support
Strong public supportAI gateway, tool-connection, and runtime controls
Mediate model, agent, tool, application programming interface (API), connector, and Model Context Protocol (MCP) traffic through an enforcement point that applies identity-aware policy, content controls, routing, rate limits, and auditable allow or deny decisions.
Public claims reviewed
1
Next question to verify
A model, agent, tool, or Model Context Protocol (MCP) request passes through a named policy enforcement point.
Maintain accountable AI inventory, policy, risk assessments, approvals, exceptions, regulatory mappings, third-party oversight, and audit evidence across the AI lifecycle.
Framework references
GOVERN 1.2 · GOVERN 1.6 · MANAGE 3.1
Lifecycle
Govern · Identify · Assess · Approve · Monitor
Security requirements with public support
1 requirement with public support
Limited 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.
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
MEASURE 2.7 · MEASURE 2.13 · MANAGE 4.1
Lifecycle
Develop · Test · Release · Monitor
Security requirements with public support
1 requirement with public support
Strong public supportAI coding-agent and workstation security
Discover and govern AI coding agents, integrated development environment (IDE) assistants, command-line agents, skills, hooks, extensions, Model Context Protocol (MCP) tools, filesystem access, commands, network activity, secrets, and software-supply-chain actions on developer workstations and build environments.
Public claims reviewed
1
Next question to verify
A test coding agent and its skills, hooks, extensions, or Model Context Protocol (MCP) tools appear in an attributable inventory.
Authorize, log, and control agent-to-agent, agent-to-tool, Model Context Protocol (MCP), connector, and tool-chain handoffs.
Public claims reviewed
1
Next question to verify
An agent, tool, connector, or Model Context Protocol (MCP) handoff logs source identity, destination, and authorization decision.
Review source claims →Strong public supportNon-human identity and service-account security
Inventory, least privilege, credential hygiene, monitoring, and lifecycle management for non-human identities, workloads, service accounts, application programming interface (API) keys, and machine credentials.
Public claims reviewed
1
Next question to verify
A test service account, agent identity, or non-human identity appears in inventory with owner and privileges.
Secure trust, authorization, message flows, tool access, and communication between agents, tools, application programming interfaces (APIs), and external services.
Framework references
MEASURE 2.7 · MAP 4.2 · MANAGE 4.1
Lifecycle
Identify · Protect · Deploy · Monitor
Security requirements with public support
3 requirements with public support
Limited public supportAgent-to-agent communication security
Authorize, log, and control agent-to-agent, agent-to-tool, Model Context Protocol (MCP), connector, and tool-chain handoffs.
Public claims reviewed
1
Next question to verify
An agent, tool, connector, or Model Context Protocol (MCP) handoff logs source identity, destination, and authorization decision.
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.
Review source claims →Strong public supportAI gateway, tool-connection, and runtime controls
Mediate model, agent, tool, application programming interface (API), connector, and Model Context Protocol (MCP) traffic through an enforcement point that applies identity-aware policy, content controls, routing, rate limits, and auditable allow or deny decisions.
Public claims reviewed
1
Next question to verify
A model, agent, tool, or Model Context Protocol (MCP) request passes through a named policy enforcement point.
non-human identity (NHI) and AI-agent identity governance
Manage identities, credentials, privileges, secrets, service accounts, and lifecycle for AI agents and other non-human identities.
Framework references
GOVERN 6.1 · MAP 4.2 · MANAGE 3.1
Lifecycle
Govern · Protect · Deploy · Operate
Security requirements with public support
3 requirements with public support
Strong public supportNon-human identity and service-account security
Inventory, least privilege, credential hygiene, monitoring, and lifecycle management for non-human identities, workloads, service accounts, application programming interface (API) keys, and machine credentials.
Public claims reviewed
1
Next question to verify
A test service account, agent identity, or non-human identity appears in inventory with owner and privileges.
Register AI agents as accountable identities, bind them to owners and delegating users, authorize task- and tool-level access, issue short-lived credentials, review access, and revoke or suspend agent authority.
Public claims reviewed
1
Next question to verify
A test agent is registered with a unique identity, accountable owner, purpose, and permitted resources.
Attribute AI usage and spend to accountable owners, workflows, agents, models, and business units while enforcing budget, rate-limit, and routing controls.
Framework references
GOVERN 1.6 · MAP 1.4 · MANAGE 3.2
Lifecycle
Govern · Operate · Optimize
Security requirements with public support
3 requirements with public support
Limited 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.
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.
Review source claims →Strong public supportNon-human identity and service-account security
Inventory, least privilege, credential hygiene, monitoring, and lifecycle management for non-human identities, workloads, service accounts, application programming interface (API) keys, and machine credentials.
Public claims reviewed
1
Next question to verify
A test service account, agent identity, or non-human identity appears in inventory with owner and privileges.
This page organizes research. Audit conclusions, certification assessments, control implementation statements, and vendor endorsements require separate evidence.