Join our Newsletter — 33% off our NHI Course
Home› Glossary› Cyber Security› Maintaining Access
Cyber Security

Maintaining Access

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Cyber Security

Maintaining access is the stage where a tester attempts to keep a foothold after initial compromise, often to evaluate escalation and lateral movement opportunities. In real attacks, this mirrors the persistence an adversary seeks inside a network. It helps reveal segmentation weaknesses and privilege control failures.

What Maintaining Access Means in an Attack Chain

Maintaining access is the phase where an attacker, or a tester simulating one, tries to preserve a foothold after initial compromise. The goal is to avoid losing entry when credentials are reset, systems are rebooted, or defenders begin responding, so the activity reveals how durable the environment is under pressure.

In practice, this stage tests whether an intrusion can survive basic cleanup and whether access paths are too easy to re-establish. It is useful because persistence often depends on weak segmentation, overbroad permissions, exposed remote access, or fragile account and session controls.

Why Maintaining Access Matters

This phase matters because the first compromise is often only the start of the security problem. If an attacker can remain present, they can observe internal systems, wait for higher-value credentials, and move from one compromised host or account to another. A well-contained environment should make that difficult.

Maintaining access also exposes whether defensive assumptions hold after the initial breach. If a reset, logoff, or host rebuild does not truly sever the attacker’s route back in, the organisation may have a hidden persistence problem rather than a one-time incident.

Common Persistence Patterns

Maintaining access can involve many mechanisms, from creating new accounts or adding authorised keys to abusing scheduled tasks, startup items, remote management tools, or long-lived sessions. The exact method depends on the environment, but the security meaning is the same: the attacker is trying to preserve a reliable return path.

It is also closely related to privilege escalation and lateral movement. A foothold that starts on one system may become durable only after the attacker discovers broader trust relationships, shared credentials, or management channels that were never intended to remain available after compromise.

For defenders, frameworks such as MITRE ATT&CK Enterprise Matrix help map persistence and lateral movement behaviours into a huntable attack chain, while NIST Cybersecurity Framework 2.0 is useful for organising the broader govern, protect, detect, respond and recover lifecycle around that exposure.

How Organisations Validate Exposure and Recovery

Teams usually validate maintaining-access exposure by asking a simple question: after a compromise, what still allows the attacker to return? That means reviewing account inventory, remote administration paths, privileged access, token and key lifecycle, and whether access is tied to a single endpoint, user, or service account that can be cleaned up quickly.

Testing should also cover segmentation and monitoring. If an attacker can move laterally after the first foothold, or if defenders cannot see that movement, then the environment has not only an access problem but a containment problem. Guidance such as NIST AI Risk Management Framework is not about this tactic specifically, but it can still support organisations that use automated tooling to reason about attack exposure and response decisions consistently.

Operational control standards are also relevant. CIS Controls v8 supports the practical work of reducing the attack surface through asset, account, logging and vulnerability discipline, while NIST SP 800-53 Rev 5 Security and Privacy Controls gives a control catalogue for access control, identification and authentication, audit, and configuration management.

Detection and Removal After Compromise

Maintaining access is often discovered only when logs, endpoint telemetry, or identity events show that the attacker returned after an apparent cleanup. That is why post-incident review should look for repeated logins, unexpected new access paths, abnormal privileged activity, and changes that would let the same foothold survive remediation.

When a persistence mechanism is found, remediation must do more than delete a single artefact. Organisations should verify that the original entry point is closed, the access path is revoked, and any reused trust material is replaced, because a surviving credential, session, or management channel can keep the compromise alive even after the visible malware or implant is gone.

Risk and Threat Considerations

Maintaining access is dangerous because it converts a single intrusion into an ongoing presence. The main risk is not just initial compromise, but the attacker’s ability to stay embedded long enough to escalate privileges, move laterally, and repeatedly revisit targets even after defenders believe the incident is contained.

Failure mechanism: Defenders remove one foothold, but another persistence path, reused credential, or trusted administrative channel remains available, allowing the attacker to re-enter or survive cleanup.

Impact: The organisation may face prolonged exposure, deeper internal discovery by the attacker, repeated compromise after remediation, and a higher likelihood of data theft or operational disruption.

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 NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
MITRE ATT&CKTA0003 — PersistenceMaintaining access is the persistence phase of an intrusion.
Recommendation — Map observed footholds to Persistence techniques and hunt for repeat entry paths.
NIST CSF 2.0DE.CM-09 — Monitoring for unauthorized personnel, connections, devices, and softwareDetecting continued footholds depends on monitoring for unauthorized activity and access paths.
Recommendation — Track unauthorized access signals and investigate recurring footholds promptly.
NIST SP 800-53 Rev 5AC-2 — Account ManagementMaintaining access often exploits weak account lifecycle control and unauthorized accounts.
IA-5 — Authenticator ManagementPersistent access frequently survives through reused or long-lived credentials and authenticators.
AU-6 — Audit Record Review, Analysis, and ReportingPost-compromise review relies on log analysis to detect recurring access and persistence.
Recommendation — Review, disable, and govern accounts so compromised access cannot persist. Rotate and revoke authenticators to remove surviving access paths after compromise. Correlate audit data to confirm whether the attacker returned after cleanup.

Practitioner Guidance

What to watch for: Treat unexplained reappearance of access, repeated authentication from the same source, or lingering privileged changes as a sign that the compromise was not fully removed. Maintaining access is a lifecycle problem, so incident responders should think in terms of revocation, containment, and validation, not just eradication.

Practitioner takeaway: A clean endpoint does not prove a clean environment if the attacker can still authenticate, re-establish trust, or reuse an access path elsewhere.

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