Governance and Assurance
Governance and assurance are cross-stack architecture responsibilities. Controls must exist at enforceable identity, network, runtime, data, artifact, and administrative boundaries rather than relying on model behavior alone. Architecture owners define risk, approved policy, accountable authority, and acceptable evidence. Platform and operations owners implement, monitor, maintain, and recover the controls that satisfy them.
This layer defines what must be governed and assured across the architecture: risk, approved policy, compliance, control objectives, accepted evidence, and accountable identity and delegation decisions. Platform Services implement identity and trust, policy enforcement, supply-chain controls, observability, detection, and audit.
Explore security and governance ecosystem solutions.
Control Planes
Resolve the following decisions across each governance and assurance plane:
Enforcement Boundaries
Architecture-wide requirements must resolve to enforceable controls and named operators:
- Platform Services provide Identity and Trust Services, Policy and Enforcement, Delivery and Supply Chain, and Observability and Detection for approved requirements.
- Cloud-Native Platform provides admission, network policy, controlled egress, workload identity, tenant isolation, sandbox or virtualization boundaries, runtime telemetry, patching, and containment primitives.
- Operations and Resilience owns secure maintenance, vulnerability remediation, incident response, continuity, recovery, and the day-two lifecycle of every enforcement point.
- Capability Reference Designs compose those controls for a defined problem. Secure Agent Workspace, for example, requires an approved agent-isolation boundary, workspace identity, brokered credentials, network perimeter controls, and attributable audit.
Do not assign a named product to the public architecture until its role, boundary, dependencies, support model, and accountable owner are approved. This keeps the core stable while product-specific implementation guidance evolves.
Related Agent-Safety Reference Design
NVIDIA Open Agent Safety Platform is a related NVIDIA reference design for governing and monitoring autonomous agents across software and hardware boundaries. It combines NVIDIA OpenShell runtime controls with NVIDIA Sentry and supported NVIDIA infrastructure. It is linked guidance rather than a core element or Capability Reference Design in this publication. Use its technical architecture overview to assess applicable runtime-governance, out-of-band monitoring, and infrastructure-enforcement patterns.
Model and Inference Confidentiality
Define who can access model weights and disclose inference inputs, retrieved context, and outputs. Apply those decisions to model storage, delivery, serving, telemetry, and retirement. AI Platform owns the serving implementation; Platform Services mediates access and disclosure. Governance and Assurance defines protection objectives and accepted evidence.
Confidential computing can protect selected material in use when supported by the deployment and threat model. It complements access, disclosure, and lifecycle controls rather than replacing them.
Confidential Computing
Use confidential computing when the threat model requires stronger isolation or verifiable protection for selected data, models, credentials, or workloads while they are in use. It introduces platform-specific hardware, firmware, driver, attestation, key-release, monitoring, and recovery requirements. It is not a blanket security upgrade for every workload.
Use the following deployment boundaries to assess architecture requirements:
Begin with the NVIDIA Trusted Computing Solutions library for current deployment options, attestation, compatibility, and operational guidance. Do not rely on roadmap status or an unverified platform combination in an architecture approval.
Governance Outcomes
- Named owners for architecture, platform, security, data, application, and operations decisions.
- Approved exceptions with scope, risk, compensating controls, and review date.
- Traceable changes to policies, models, prompts, tools, connectors, and deployment state.
- Human-review gates proportional to workload authority and potential impact.
- Defined vulnerability-management, patch, containment, and recovery responsibilities for platform and workload owners.
- A clear statement of which organization owns compliance authorization and product support.