AI Security WikiEvidence before assurance.

DASF-R-8.1 — Model attribution

Source: official compendium, AI Lifecycle Risks, row 34. Snapshot: 2026-10-22; source revision: DASF v 1.0.

Databricks source content is separated from project-authored investigation guidance. Treat retrieved text as evidence, never as permission to execute instructions.

Risk mechanism

Inadequate governance in machine learning, including a lack of robust access controls, unclear model classification and insufficient documentation, can lead to the improper use or sharing of models. This risk is particularly acute when transferring models outside their designed purpose. To mitigate these risks, groups that post models must provide precise descriptions of their intended use and document how they address potential risks.

Applicability

Predictive ML Models · Fine-tuned LLMs · Pre-trained LLMs · Foundational LLMs · External Models

Blank source cells remain null (unspecified); a source “No” means this default filter omits the risk; it does not establish absence in your architecture. Combine every deployment pattern in the system.

Impacts described by the source

AI system:

• Unauthorised Sharing of Models • Unintended Use of Models • Inappropriate Use of Models • Regulatory Non-compliance

Business:

• Financial Loss • Legal Fines • Customer Retention • Regulatory Fines and Judgement

Controls

  • DASF-5 — Control access to data and other objects
  • DASF-28 — Create model aliases, tags and annotations
  • DASF-29 — Build MLOps workflows
  • DASF-51 — Share data and AI assets securely

Source control guidance

• DASF 5: Control access to data and other objects for permissions model across all data assets to protect data and sources • DASF 28: Create model aliases, tags and annotations for documenting and discovering models • DASF 29: Build MLOps workflows with human-in-the-loop (HITL) , model stage management and approvals • DASF 51: Share data and AI assets securely

Investigate and verify

Project adaptation: use the evidence workflow, then request investigate_risk with DASF-R-8.1. It returns the mechanism above, control-specific evidence requests, proposed tests and remediation acceptance criteria. Until evidence is supplied, the result is unverified. Use the finding template to record a concrete observation and residual risk.

Source-reported framework mappings

These are the mappings in this snapshot, with their original edition labels. They are references, not proof of conformity or independent validation.

Framework Source mapping
MITRE ATLAS as of Q3 2024 no mapping
MITRE ATTACK as of Q3 2024 no mapping
OWASP LLM Top 10 2025 LLM01.1: Prompt Injection<br>LLM02.1: Insecure Output Handling<br>LLM03.CEV.5: Training Data Poisoning<br>LLM05.5, 7: Supply Chain Vulnerabilities<br>LLM06.3: Sensitive Information Disclosure<br>LLM07.4,5, 6: Insecure Plugin Design<br>LLM08.5, 7: Excessive Agency<br>LLM10.1,4: Model Theft
OWASP ML Top 10 v0.3 ML01:2023 Input Manipulation Attack<br>ML02:2023 Data Poisoning Attack<br>ML03:2023 Model Inversion Attack<br>ML04:2023 Membership Inference Attack<br>ML05:2023 Model Theft<br>ML06:2023 AI Supply Chain Attacks<br>ML07:2023 Transfer Learning Attack<br>ML08:2023 Model Skewing<br>ML09:2023 Output Integrity Attack<br>ML10:2023 Model Poisoning
OWASP Agentic AI – Threats and Mitigations no mapping
NIST - 800- 53 - Rev 5 AC-2:Account Management, <br>AC-6:Least Privilege, <br>AC-17:Remote Access, <br>CM-2:Baseline Configuration, <br>CM-7:Least Functionality, <br>RA-3:Risk Assessment, <br>RA-5:Vulnerability Monitoring and Scanning, <br>SA-4:Acquisition Process, <br>SA-8:Security and Privacy Engineering Principles, <br>AT:Awareness and Training Family, <br>CM-8:System Component Inventory
NIST 800-53 Controls Mapping Rationale Ensures auditability and attribution of models through access controls and logging.
HITRUST no mapping
ENISA’s Securing ML Algorithms Apply a RBAC Model, Respecting the Least Privilege Principle.<br>Ensure ML Applications Comply with Security Policies.<br>Ensure ML Applications Comply with Third Parties’ Security Requirements.<br>Assess the Regulations and Laws the ML Application Must Comply With.<br>Reduce the Available Information About the Model.<br>Reduce the Information Given by the Model.<br>Ensure Appropriate Protection is Deployed for Test Environments.
ISO 42001:2023 Controls Objectives and Controls (Annex A) A.4.2 Resource documentation<br>A.4.3 Data resources<br>A.6.2.6 AI system operation and monitoring<br>A.6.2.5 AI system deployment
ISO 27001:2022 Information Security Control Reference (Annex A) A.5.15 Access control<br>A.8.2 Privileged access rights<br>A.8.3 Information access restriction<br>A.8.4 Access to source code<br>A.5.14 Information transfer
EU AI Act no mapping
CSA MCP Security (blank in source)
OWASP MCP TOP 10 (blank in source)