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-OAM — Operational Activity Mapping

Operational activity mapping identifies activities of the organization and the organization's suborganizations, groups, roles, and individuals that carry out the activities and then establishes the dependencies of the activities on the systems and people that perform those activities.

24Enterprise inferred
2ICS inferred
4Direct children
2Related artifacts

Model · D3FEND ontology 1.6.0 · Active

Open official technique ↗
Official D3FEND definition

Definition

Operational activity mapping identifies activities of the organization and the organization's suborganizations, groups, roles, and individuals that carry out the activities and then establishes the dependencies of the activities on the systems and people that perform those activities.

Bare Metal Cyber interpretation

Implementation perspective

Operational Activity Mapping 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 Access Control Configuration, User Account.

Use the technique to improve the shared model of systems, activities, dependencies, threats, or risk before making defensive decisions.

Questions to ask

  • What system, activity, relationship, or risk is being modeled, and where is the scope boundary?
  • Which authoritative data sources populate the model, and how is their quality assessed?
  • How often is the model refreshed after architectural, operational, or threat changes?
  • Which decisions, analyses, or engineering actions are expected to use the model?

Evidence and validation

  • Documented model scope, assumptions, and ownership
  • Source inventories, data-quality checks, and refresh records
  • Version history showing material changes to the model
  • Examples of decisions or analyses that used the model

Common failure patterns

  • The model is treated as a one-time diagram rather than a maintained decision aid.
  • Unverified or stale source data is accepted without recording uncertainty.
  • The model is comprehensive in appearance but disconnected from engineering or operational decisions.

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

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.

Show inferred artifact relationship paths (2)
Access ModelingmapsAccess Control Configuration
Access ModelingmapsUser Account
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 (24)
ATT&CK for ICS (2)
T0812Default CredentialsLateral Movement
T0859Valid AccountsLateral Movement, Persistence
Source record

Authoritative sources