Definition
Active logical link mapping sends and receives network traffic as a means to map the whole data link layer, where the links represent logical data flows rather than physical connection
How it works
Active logical link mapping establishes awareness of logical links in the network by sending data over the network to gather information about logical connections in the network.
Typically this will be achieved through network telemetry coordinated for network management and monitoring and will use a link layer discovery protocol such as LLDP and the information gathered and aggregated at higher levels using an application protocol such as SNMP. The information may be polled by network management software or configured once and then pushed from network sensors (or agents.)
Another means of establishing network connectivity is by means of sending traffic through the use of a tool such as traceroute, to determine the logical paths through the network architecture.
Considerations
- Best practice is to encrypt network monitoring data and require authentication for queries or admin/management functions.
- Push notifications reduce bandwidth necessary to capture and maintain information if reliable transport is used.
- Special consideration should be made before using of active scanning in OT networks and OT-safe options chosen where available.
Implementation perspective
Active Logical Link 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 Network Node.
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.
Technique hierarchy
Top-level family
Parent techniques
Direct child techniques
None listed at this level.
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
Show inferred artifact relationship paths (1)
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 (7)
ATT&CK for ICS (8)
Authoritative sources
- Open this technique on the official D3FEND website ↗
- Open the official ontology resources ↗
- Identification of traceroute nodes and associated devices ↗SolarWinds Worldwide LLC · Tomas KUBIK, Lan Li, Tomas RYBKA, Karlo ZATYLNY, Chris O'Brien · PatentReference
- SNMP - Network Auto Discovery ↗Device 42 · UserManualReference
Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by The MITRE Corporation. MITRE D3FEND™ and the D3FEND logo are trademarks of The MITRE Corporation. MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. Use of D3FEND source material is subject to the official Terms of Use.