Microsoft and NVIDIA publish 'Risk Management for Open-Weight Models in Enterprise': a shared five-category risk taxonomy mapped to evaluations, arguing that weight openness alone does not decide an AI system's risk
Microsoft and NVIDIA published a joint paper, Risk Management for Open-Weight Models in Enterprise, on 16 October 2026, the first in a planned series of joint resources. Its core argument is that whether a model's weights are open does not by itself set an AI system's risk: risk depends on the model, the use case, the deployment and the safeguards around it. A model drafting internal documents carries different risk from the same model in a customer-facing workflow or connected to external data and tools, and the best control may sit in the inference environment or application rather than the model. The paper offers a shared taxonomy with five risk categories (cybersecurity, data protection, content, human-AI interaction, and bias), grounded in ISO standards and the NIST AI Risk Management Framework, and maps evaluations to selected risks so teams can produce evidence for the risks that matter in their deployment. Microsoft stresses the taxonomy is not a policy or deployment checklist. The paper also notes that organisations running their own open-weight deployments may take on safeguards that a managed service would otherwise provide. This first paper covers mainly the model layer; Microsoft says evaluating a model alone does not establish that an agent or application is safe, and later papers are meant to cover the runtime, harness and application layers. A companion GitHub repository in NVIDIA's organisation, co-maintained by both companies, will collect further evaluations, including community contributions. Primary: Microsoft Security blog; paper and repository: NVIDIA GitHub.
- Product
- Open-weight AI models in enterprise deployments (guidance)
- Exploited in Australia?
- unknown
- Patch to
- Before deploying an open-weight model, record its provenance, intended use, users and the data and tools it can reach; map each relevant risk in the five categories to an evaluation, a control and a named owner; and if you self-host, list the safeguards a managed service would have given you (content filtering, abuse monitoring, patching) and who now runs each one. Re-run the assessment when the model, its permissions or its tools change.
Primary: Microsoft Security blog — Managing open-weight model risk in enterprise deployments (16 Oct 2026) · Vendor: NVIDIA / Microsoft — OpenEnterpriseRiskManagementGuidance companion repository · Risk Management for Open-Weight Models in Enterprise — joint Microsoft–NVIDIA paper (PDF)