AI Security WikiEvidence before assurance.

DASF-27 — Pretrain a large language model (LLM)

Source: official compendium, Databricks AI Mitigation Controls, row 29. 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.

Intent and implementation

Data is your competitive advantage. Use it to customize large AI models to beat your competition by pretraining models with your data, imbuing the model with domain-specific knowledge, vocabulary and semantics. Pretrain your own LLM with MosaicML to own your IP.

Source metadata

  • Category: Model Management and MLOps
  • System component: ML algorithm,
  • Databricks responsibility: Databricks — Implementation
  • Product reference: Co-managed
  • Feature/control: Feature
  • Security Analysis Tool reference: Features available to implement control and manually verify
  • Novelty: Novel AI Control/Capability

Databricks responsibility labels do not establish who enforces this control on another platform. Name a local owner and verify it.

Implementation references

Risks linked by the risk table

The control table separately reports: DASF-R-1.8, DASF-R-7.3, DASF-R-9.8. See source issues for differences.

Verification

Project adaptation: get_control returns a concrete evidence request, a proposed test, and an acceptance condition. A control description or product feature is not evidence of deployment or effectiveness.

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 no mapping
OWASP ML Top 10 v0.3 no mapping
ISO 42001:2023 Controls Objectives and Controls (Annex A) A.4.3 Data resources<br>A.6.1.2 Objectives for responsible development of AI system<br>A.6.1.3 Processes for responsible design and development of AI systems<br>A.6.2.3 Documentation of AI system design and development
ISO 27001:2022 Information Security Control Reference (Annex A) no mapping
NIST - 800- 53 - Rev 5 no mapping
HITRUST Security for AI Systems AI legal and compliance -> ID and evaluate compliance & legal obligations for AI system development and deployment<br><br>AI legal and compliance -> ID and evaluate any constraints on data used for AI<br><br>Supply chain -> Verification of origin and integrity of AI assets
ENISA’s Securing ML Algorithms no mapping
EU AI ACT no mapping
NIST CSF 2.0 no clear mapping, but a case can be made for protecting data security, assets (AI models), and any software/hardware used to train:<br><br>PR.DS-01<br>PR.DS-02<br>PR.DS-11
AIUC-1 no mapping