MITRE ATT&CK T0840: Network Connection Enumeration
When to use this skill
Use this skill when the task involves T0840, Network Connection Enumeration, ics ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.
Technique context
- ATT&CK domain: ics
- ATT&CK ID: T0840
- Technique name: Network Connection Enumeration
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T0840
- Tactics: discovery
- Platforms: None
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may perform network connection enumeration to discover information about device communication patterns. If an adversary can inspect the state of a network connection with tools, such as Netstat(Citation: Netstat), in conjunction with System Firmware, then they can determine the role of certain devices on the network (Citation: MITRE). The adversary can also use Network Sniffing to watch network traffic for details about the source, destination, protocol, and content.
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
templates/detection-brief.md: detection engineering brief template.
templates/hunt-plan.md: threat hunt plan template.
templates/incident-response-note.md: incident response note template.
templates/coverage-assessment.md: ATT&CK coverage assessment template.
scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- Mitigation Limited or Not Effective
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- 2025 Poland Wiper Attacks (campaign)
- EKANS (malware)
- Industroyer (malware)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
1---2name: attack-ics-t0840-network-connection-enumeration3description: "Analyze MITRE ATT&CK T0840 Network Connection Enumeration in the ics matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T0840, Network Connection Enumeration, or ics ATT&CK. Adversaries may perform network connection enumeration to discover information about device communication patterns."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ics-t0840-network-connection-enumeration7 upstream: mitre-attack/attack-stix-data8 domain: ics9 attack_id: T084010 attack_stix_id: attack-pattern--ea0c980c-5cf0-43a7-a049-59c4c207566e11 attack_version: "1.2"12 attack_modified: "2025-04-15T19:59:18.381Z"13---1415# MITRE ATT&CK T0840: Network Connection Enumeration1617## When to use this skill1819Use this skill when the task involves T0840, Network Connection Enumeration, ics ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.2021## Technique context2223- ATT&CK domain: ics24- ATT&CK ID: T084025- Technique name: Network Connection Enumeration26- Type: technique27- ATT&CK URL: https://attack.mitre.org/techniques/T084028- Tactics: discovery29- Platforms: None30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may perform network connection enumeration to discover information about device communication patterns. If an adversary can inspect the state of a network connection with tools, such as Netstat(Citation: Netstat), in conjunction with [System Firmware](https://attack.mitre.org/techniques/T0857), then they can determine the role of certain devices on the network (Citation: MITRE). The adversary can also use [Network Sniffing](https://attack.mitre.org/techniques/T0842) to watch network traffic for details about the source, destination, protocol, and content.3738## Agent workflow39401. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.412. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.423. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.434. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.445. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.456. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.4647## Bundled resources4849- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.50- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.51- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.52- `templates/detection-brief.md`: detection engineering brief template.53- `templates/hunt-plan.md`: threat hunt plan template.54- `templates/incident-response-note.md`: incident response note template.55- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.56- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.57- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.5859To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6061## Detection guidance6263No ATT&CK detection guidance was present in the source STIX object.6465## Useful telemetry and data sources6667- Not specified in the STIX object.6869## Mitigations to consider7071- Mitigation Limited or Not Effective7273## Known threat context7475Use these examples only as contextual leads, not as proof that an observed event is this technique:7677- 2025 Poland Wiper Attacks (campaign)78- EKANS (malware)79- Industroyer (malware)8081## Recommended output pattern8283When responding with this skill, structure the answer as:8485- Assessment: whether the evidence supports this ATT&CK mapping and why.86- Evidence: specific indicators, logs, behaviors, and assumptions.87- Detection: telemetry sources, analytic logic, and tuning considerations.88- Response: containment, eradication, recovery, and validation actions.89- Coverage gaps: missing logs, sensors, controls, or environmental details.90- References: include the ATT&CK URL and any user-provided evidence references.