Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Litigation Hold
Governance, Ownership & Risk

Litigation Hold

← Back to Glossary
By NHI Mgmt Group Updated October 30, 2026 Domain: Governance, Ownership & Risk

Litigation hold is the process of preserving potentially relevant records when an investigation, dispute, or legal proceeding is anticipated or underway. It suspends normal deletion or retention rules for specific data so organisations can retain evidence in a controlled, auditable manner.

What litigation hold means in practice

Litigation hold is more than a retention setting. It creates a temporary preservation obligation that overrides ordinary deletion workflows for the records that may matter to a dispute, investigation, or proceeding. The key distinction is that the organisation is no longer optimising for routine disposal, but for defensible preservation.

That shift matters because litigation hold usually spans multiple systems, content types, and custodians. Email, chat, collaboration content, file shares, and application records can all fall within scope, so the hold must be interpreted broadly enough to capture relevant evidence without freezing the entire environment.

How litigation hold changes records management

A normal retention programme asks when content should be deleted. A litigation hold asks what must not be deleted yet. In practice, that means retention schedules, auto-delete rules, and disposal processes need to pause or be selectively bypassed for the covered material while the matter remains active.

The hold should also be understood as a governance control, not just a technical action. Someone must determine scope, issue the notice, define what systems are covered, and keep the hold aligned to the legal matter as it evolves. If the scope is too narrow, relevant evidence can be lost. If it is too broad, the organisation may keep unnecessary data longer than needed.

For teams designing policy and workflow around retention, NHIMG’s Data Retention and Disposal Policy Template is useful because it places litigation holds alongside retention schedules, secure deletion, backups, and decommissioning controls.

Preserving evidence across modern collaboration systems

Litigation hold is especially important in modern environments because relevant records are no longer limited to files and email. Chat messages, meeting artefacts, shared documents, SaaS content, and AI-generated or AI-assisted material may all become discoverable records if they relate to the matter.

That creates a practical challenge: preservation has to work across systems with different retention semantics, export formats, and admin controls. Teams need to know where content lives, how deletion is enforced, and which platforms support hold functionality or equivalent preservation workflows.

NHIMG’s eDiscovery and Legal Hold Guide is the clearest companion resource for the operational side of this problem, including preservation of chat content, workspace records, and AI prompt material when those records are relevant to a legal matter.

Defensibility, auditability, and release of the hold

The value of litigation hold is not only that records are preserved, but that the preservation can be shown to have been controlled. Organisations need a clear audit trail for when the hold was issued, which data was in scope, who was notified, and when normal retention rules were restored.

That defensibility also depends on good release discipline. Once the matter ends, the hold should be lifted promptly and the affected content should return to the normal retention and disposal schedule. Leaving holds open indefinitely creates unnecessary storage, governance, and compliance burden, and can turn preservation into permanent over-retention.

For a broader policy view that connects retention, deletion, backups, and legal hold handling, NHIMG’s Data Retention and Secure Deletion Guide helps explain how preservation and disposal should coexist without undermining one another.

Risk and Threat Considerations

Litigation hold creates a real exposure window if it is not implemented precisely. The main risks are spoliation from premature deletion, over-retention of sensitive records, and inconsistent preservation across systems that handle the same matter differently.

Failure mechanism: If the hold does not reach every relevant repository, or if retention automation continues to purge covered content, the organisation can lose evidence and weaken its legal position. If the hold is too broad, it can retain unnecessary material and increase privacy, exposure, and discovery burden.

Impact: Poorly executed holds can trigger sanctions, adverse inferences, higher discovery costs, and unnecessary exposure of sensitive information that should no longer be retained.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 and GDPR define the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AU-9 — Protection of Audit InformationLitigation hold depends on preserving evidentiary records and audit trails.
SI-12 — Information Management and RetentionRetention and disposition controls directly govern when records are kept or removed.
Recommendation — Protect hold records and audit logs so preservation actions remain tamper-evident and reviewable. Apply retention and disposition controls to suspend deletion where legal preservation is required.
ISO/IEC 27001:2022A.5.33 — Protection of RecordsProtecting records under legal hold is a direct Annex A records-governance concern.
A.8.10 — Information DeletionLitigation hold temporarily overrides normal deletion decisions and deletion automation.
Recommendation — Define and enforce record-protection procedures that preserve held content for the required period. Pause deletion processes for in-scope records until the hold is formally released.
GDPRArticle 5(1)(e) — Storage limitationLitigation hold intersects with retention limits when records must be kept longer for legal claims.
Recommendation — Document the legal basis for extended retention and release data back to disposal rules when the hold ends.

Practitioner Guidance

Governance implication: Treat litigation hold as a matter-scoped preservation control with named ownership. Legal, records, and security or IT teams should share responsibility for scope definition, system coverage, and release decisions so that the hold is both defensible and operationally enforceable.

What to watch for: The most common failure is assuming that a legal notice alone is enough. A hold only works when the relevant systems, backup processes, collaboration tools, and deletion workflows are actually constrained in line with the matter scope.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org