Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Pave And Repave
Governance, Ownership & Risk

Pave And Repave

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

A restoration method that rebuilds a compromised system from a clean operating system image and then layers trusted data back on top. It is especially useful when malware may have embedded itself below the application layer or inside the original OS state.

What Pave And Repave Means in Practice

Pave and repave is a restoration pattern, not just a reinstall. The goal is to discard the untrusted operating system state, rebuild the system from a known-clean image, and then restore only the data that has been validated as trustworthy. That makes it especially useful when the compromise may have affected the OS itself, boot components, or persistence mechanisms below the application layer.

Because the method assumes the original host state cannot be trusted, it is most often used after serious compromise, not as a routine repair. The practical value is that it resets the system to a defensible baseline instead of trying to disinfect a potentially altered installation in place.

Why Pave And Repave Works

This approach works because it changes the trust anchor. Instead of relying on a potentially tampered endpoint to clean itself, the organisation rebuilds the host from an image that is treated as authoritative. That removes many forms of hidden persistence, including rootkit-style modification, malicious services, altered startup settings and other OS-level contamination that can survive ordinary cleanup.

It also reduces uncertainty. When malware may have manipulated local tooling, logs, or security controls, a clean rebuild is often more reliable than trying to prove every component is intact. In that sense, pave and repave is both a remediation method and a trust-restoration method.

What Must Be Rebuilt, Restored, or Revalidated

A successful repave is broader than reinstalling the OS. The rebuilt system needs a trusted base image, then a controlled return of configuration, applications, and data. That distinction matters because the recovery process itself can reintroduce the compromise if infected binaries, scripts, scheduled tasks, or unmanaged settings are copied back unchanged.

Trusted restoration is therefore selective. Data should be scanned or validated before it is reintroduced, and configuration drift should be corrected rather than blindly replayed. If the original environment contained scripts, automation, or credentials embedded in files, those artifacts deserve special scrutiny before they are moved onto the new host.

When Organisations Use It Instead of Traditional Cleanup

Pave and repave is usually chosen when the compromise is severe enough that confidence in the host is low. That includes suspected kernel or boot-level persistence, repeated reinfection after cleanup, or environments where the organisation cannot reliably prove which components were touched. In those cases, rebuilding is often faster and safer than attempting a forensic disinfection.

It is also common where standard remediation would take too long to verify. A rebuild can restore service predictably, while a forensic clean-up can leave lingering doubt about whether every malicious change was found. For high-value systems, the decision is often driven by confidence and speed as much as by the technical presence of malware.

Risk and Threat Considerations

The main risk is treating the rebuilt host as clean while restoring compromised data, settings, or secrets back onto it. If the compromise included persistence, token theft, or tampered automation, the threat can reappear immediately after rebuild.

Failure mechanism: The attacker’s foothold survives outside the operating system image, in copied files, restored configuration, remote management paths, or reused credentials and then re-establishes access after the system is repaved.

Impact: The organisation gets a fresh OS but not a fresh security posture, which can lead to reinfection, repeated compromise, or continued unauthorized access.

Standards & Framework Alignment

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

MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8, NIST SP 800-53 Rev 5 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
CIS Controls v8CIS-5 — Account ManagementPave and repave depends on re-establishing trusted host access and removing stale accounts.
Recommendation — Remove stale access, then reissue accounts and privileges only after the rebuilt system is validated.
NIST SP 800-53 Rev 5SI-2 — Flaw RemediationRebuild from a clean image is a remediation action for compromised or untrusted system state.
CM-2 — Baseline ConfigurationThe term relies on rebuilding to a known-good system image and configuration baseline.
IA-5 — Authenticator ManagementAfter repave, credentials and authenticators tied to the compromised host may need renewal.
Recommendation — Restore the host from a trusted baseline and verify it is free of known flaws before returning it to service. Recreate the system only from an approved baseline image and controlled configuration set. Rotate or reissue authenticators and secrets that may have been exposed during compromise.
NIST CSF 2.0RC.RP-01 — Recovery Plan ExecutedPave and repave is a concrete recovery action used to restore a system after compromise.
Recommendation — Execute the recovery plan by rebuilding the host from a trusted image and validating restored services.
MITRE ATT&CKT1105 — Ingress Tool TransferRepaving is often needed after hostile tooling or payloads have been introduced to the system.
Recommendation — Hunt for transferred tooling and rebuild affected hosts when unauthorized payloads have landed.

Practitioner Guidance

Why practitioners should care: Pave and repave is most effective when the recovery process is controlled as carefully as the rebuild itself. A clean image alone does not guarantee recovery if the organisation restores untrusted content or leaves the original access paths intact.

What to watch for: Pay special attention to identity material, remote admin access, startup automation, and any data source that may carry embedded execution paths. If those elements are not revalidated, the rebuilt system can inherit the original compromise through a different door.

Practitioner takeaway: Treat the repave as a trust reset, not a repair job, and restore only what can be independently justified as clean.

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 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org