# Tombstone lifetime configuration should be retrievable

The tombstone lifetime determines how long Active Directory retains “deleted but not yet purged” objects (for example, users, groups, and computer…

Source: https://maester.dev/docs/tests/AD-CFG-01

<!-- This file is generated by website/scripts/generate-test-docs.mjs. Do not edit manually. -->

<div class="test-byline"><div class="test-byline-avatars"><a class="test-byline-avatar test-byline-avatar--author" href="/contributors/soulemike" title="Michael Soule · Original author"><img src="https://github.com/soulemike.png" alt="Michael Soule" width="28" height="28" loading="lazy" decoding="async" /></a></div><div class="test-byline-meta"><span class="test-byline-text">Contributed by <a href="/contributors/soulemike">Michael Soule</a></span><a class="test-byline-link" href="/contributors">All contributors →</a></div></div>

<p class="test-part">Part of <a href="/docs/tests/ad">Active Directory</a> · Active Directory · Directory configuration · <a href="/docs/tests">All checks</a></p>

```powershell title="Run this check"
Invoke-Maester -TestId AD-CFG-01
```

## Overview

The **tombstone lifetime** determines how long Active Directory retains “deleted but not yet purged” objects (for example, users, groups, and computer accounts). This directly impacts your ability to recover from:

- **Accidental deletions** performed by admins or during automation
- **Incident response actions** that remove objects and later need restoration
- **Mis-scoped deprovisioning** (bulk removals, OU moves, scripted cleanup)

If tombstone lifetime is **too short**, recovery may fail before you notice the issue. If it is **too long**, AD can accumulate a larger tombstone dataset, increasing replication/database growth and operational overhead.

#### Control Type

**Operational**

#### Security Recommendation
- Align tombstone lifetime with your **operational recovery window** (common baselines are ~180 days or longer, but choose based on your incident response and retention requirements).
- Document and periodically review your **maximum time-to-detect** for directory changes.
- Ensure paired recovery controls are in place (for example, **Recycle Bin** where appropriate) so deleted objects can be restored safely.

#### How the Test Works
This test retrieves the environment’s configured tombstone lifetime value from AD configuration and reports it as an environment metric so you can verify it against your expected baseline.

#### Related Tests
- `Test-MtAdTombstoneLifetime` - Phase 5: Reviews tombstone lifetime in the context of overall AD recovery expectations.

## Details

<details>
<summary>Every attribute of this check</summary>

| Field | Value |
| --- | --- |
| Test ID | AD-CFG-01 |
| Severity | Info |
| Suite | Active Directory |
| Product | Active Directory |
| Feature | Directory configuration |
| Area | Infrastructure hardening |
| Resource type | Tenant |
| MITRE ATT&CK | None |
| PowerShell test | [Test-MtAdTombstoneLifetimeConfig](https://github.com/maester365/maester/blob/main/tests/ad/config/Test.AD-CFG-01.ps1) |
| Services | ActiveDirectory |
| Permissions | ActiveDirectory:Ldap:Configuration/*:ReadProperty |

</details>

## Source

- Test: [`tests/ad/config/Test.AD-CFG-01.ps1`](https://github.com/maester365/maester/blob/main/tests/ad/config/Test.AD-CFG-01.ps1)
- Documentation: [`tests/ad/config/Test.AD-CFG-01.md`](https://github.com/maester365/maester/blob/main/tests/ad/config/Test.AD-CFG-01.md)
