Knowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search courses, individual lessons, wiki entries, books, podcasts, magazine articles, Daily Cyber News, and Darwin.

MITRE D3FEND™ Learning Center

D3-PS — Process Suspension

Suspending a running process on a computer system.

14Enterprise inferred
7ICS inferred
1Parent technique
1Related artifact

Evict · D3FEND ontology 1.6.0 · Active

Open official technique ↗
Official D3FEND definition

Definition

Suspending a running process on a computer system.

Official D3FEND knowledge-base content

How it works

A running process might be suspended to mitigate its immediate effects if it is exhibiting anomalous, unauthorized, or malicious behavior. Defenders may choose to suspend rather than terminate to analyze the process first and resume the process if deemed benign.

System-provided functions

Windows tools

In Windows, the `PsSuspend` command line utility from the SysInternals Suite provides functionality to suspend processes on a local or remote system.

Bare Metal Cyber interpretation

Implementation perspective

Process Suspension should be treated as a technical defensive capability rather than a product checkbox. In practice, teams should define the protected scope, the conditions under which the technique acts, and the observable evidence that demonstrates the intended behavior. For this technique, likely engineering context includes Process.

Use the technique to remove adversary access, malicious objects, processes, credentials, or persistence from the defended environment.

Questions to ask

  • What evidence or decision threshold authorizes eviction?
  • Which sessions, credentials, processes, objects, or dependencies must be removed together?
  • How is business impact controlled while preventing the adversary from retaining access?
  • What validation confirms that persistence and alternate access paths no longer remain?

Evidence and validation

  • Approved containment and eviction procedures
  • Case records showing the trigger, authorization, and actions taken
  • Credential, session, object, or process invalidation records
  • Post-action scans and monitoring showing that access did not recur

Common failure patterns

  • Visible symptoms are removed while credentials, persistence, or alternate paths remain.
  • Eviction begins before the scope is understood and causes the adversary to change behavior prematurely.
  • Recovery and business restoration occur without post-eviction validation.

This implementation perspective is original Bare Metal Cyber educational content. It does not replace the official D3FEND definition or establish that a specific product implements the technique.

Ontology hierarchy

Technique hierarchy

Top-level family

Parent techniques

Direct child techniques

None listed at this level.

D3FEND graph relationships

Artifacts and ontology entities

These relationships describe how D3FEND connects a defensive technique to artifacts or other ontology entities. They describe graph semantics, not a product certification.

Explicit technique relationships

suspendsProcess
Show inferred artifact relationship paths (1)
Process SuspensionsuspendsProcess
Inferred and experimental

Offensive-technique relationships

These relationships are generated from D3FEND graph paths and are explicitly experimental. They should be treated as hypotheses for defensive analysis—not as proof that the technique prevents, detects, or removes an offensive behavior.

ATT&CK Enterprise (14)
ATT&CK for ICS (7)
T0806Brute Force I/OImpair Process Control
T0813Denial of ControlImpact
T0814Denial of ServiceInhibit Response Function
T0819Exploit Public-Facing ApplicationInitial Access
T0821Modify controller TaskingExecution
T0823Graphical User InterfaceExecution
T0878Alarm SuppressionInhibit Response Function
Source record

Authoritative sources