Live Active security incident? Get immediate response
MITRE ATT&CK® Detection Strategy

DET0767: Detection of Exploitation of Remote Services

DET0767 is an ATT&CK for ICS detection strategy for recognizing exploitation of remote services. Its business significance is that remote service vulnerabi...

ICSDET0767Detection StrategyObject v1.0 Modified
Glexia's Take

Analyst context for executives and security teams

Analyst confidence Medium

DET0767 is an ATT&CK for ICS detection strategy for recognizing exploitation of remote services. Its business significance is that remote service vulnerabilities can become the path into or across an industrial environment, potentially affecting operational resilience when attackers use them for initial access or lateral movement toward targeted systems.

Executive priority

Treat this as a control-validation priority for ICS environments that expose or depend on remote services. Leaders should ask which remote services exist in or connected to the ICS environment, whether vulnerability and patch decisions are risk-ranked for operational systems, and whether SOC and incident response teams can produce evidence of attempted or successful exploitation. This is especially relevant for resilience planning, audit evidence, segmentation decisions, and incident triage involving remote access paths.

Technical view

The supplied ATT&CK object provides no official detection logic, platforms, or tactics, but it detects ICS technique T0866: Exploitation of Remote Services. SOC, detection engineering, and IR teams should validate visibility around remote services that could enable initial access or lateral movement in ICS environments. Practical validation should focus on correlating remote service exposure, vulnerability context, authentication/session activity, network connections, service crashes or anomalous behavior, and host or appliance logs where available.

Likely telemetry

  • Remote service authentication and session logs where available
  • Network traffic metadata between enterprise, remote access, and ICS segments
  • Asset inventory and service exposure records for ICS-connected systems
  • Vulnerability scan or vulnerability management records for remotely reachable services
  • Endpoint, server, or appliance logs showing service errors, crashes, or abnormal process/service behavior

Detection direction

  • Start by mapping which remote services exist in the ICS environment and which logs are actually collected from those services and network paths.
  • Correlate vulnerability exposure with unusual remote service activity rather than relying on vulnerability presence alone.
  • Tune detections to distinguish authorized maintenance, vendor access, and routine administration from anomalous remote connections or service behavior.
  • Validate coverage across boundaries where blind spots commonly occur: remote access gateways, jump hosts, segmented ICS networks, legacy systems, and unmanaged appliances.
  • Because MITRE provides no official analytic text for this detection strategy, local baselining and environment-specific engineering are required.

Mitigation priorities

  • Prioritize inventory of remotely reachable services that can reach or influence ICS systems.
  • Risk-rank vulnerabilities on remote services by reachability, operational criticality, and role in initial access or lateral movement paths.
  • Reduce unnecessary exposure and enforce controlled remote access paths, segmentation, and least privilege where applicable.
  • Ensure logging is retained from remote access infrastructure, network controls, and relevant hosts or appliances before an incident occurs.
  • Exercise IR playbooks for suspected remote service exploitation, including containment decisions that account for operational safety and continuity.
Analyst notes and limits

This take is based on the DET0767 detection strategy object and its relationship to T0866, Exploitation of Remote Services, in the ICS ATT&CK domain. The object itself has no official description, detection text, platforms, or tactics, so the guidance is framed as validation direction rather than a prescribed analytic.

ATT&CK supplied sparse fields for this detection strategy. No platform list, official detection logic, data sources, or vendor-specific controls were provided. Any final detection content must be derived from the organization’s ICS architecture, remote service inventory, available telemetry, and risk tolerance.

Official MITRE ATT&CK definition

Detection of Exploitation of Remote Services

No official description is available in the imported ATT&CK source object.

View the same entry on attack.mitre.org (MITRE-hosted reference; in-page links above use the Glexia ATT&CK library.)

Glexia analysis

How security teams should use this page

Treat this object as behavior context, not an attribution claim. Validate the related groups, software, data sources, and mitigations against official ATT&CK relationships and your own telemetry before making control-coverage decisions.

ATT&CK relationship table

Techniques used

This mirrors the MITRE pattern of making group, software, campaign, and technique relationships scannable. Relationship notes come from mirrored ATT&CK relationship text when available.

1 rows
Domain ID Name Relationship / procedure
ICS T0866 Exploitation of Remote Services This object detects Exploitation of Remote Services.
Relationship explorer

All related ATT&CK context

Change history

Object version and sync metadata

The fields below describe the current mirrored snapshot. When Glexia retains multiple ATT&CK source imports, you can open the table to compare the same object across releases (hashes and MITRE timestamps). For MITRE’s own release notes and roadmap, see ATT&CK resources — Updates .

ATT&CK release
19.1
Object version
1.0
Created
Modified
Raw hash
d49a0762fc3f8817...
Imported snapshots across ATT&CK releases (1)
Release Bundle imported Object version Modified Status Raw hash
19.1 1.0 Current bundle d49a0762fc3f…
Raw source

Mirrored ATT&CK source object

The raw object is retained through the mirrored ATT&CK source bundle and object hash. The raw endpoint returns the exact object from the mirrored bundle when available.

Source references

External references and citations

MITRE external references are preserved separately from Glexia analysis so citations remain traceable to their original source records.

  1. [1]
    mitre-attack DET0767
    Open source URL
Source and licensing

Source: MITRE ATT&CK®. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation. MITRE ATT&CK and ATT&CK are registered trademarks of The MITRE Corporation. Glexia is not affiliated with or endorsed by MITRE.