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

AN2057: Analytic 2057

Monitor device alarms for program downloads, although not all devices produce such alarms.

Monitor for protocol functions related to program download or modification. Program downloads may be observable in ICS automation protocols and remote management protocols.

Consult asset management systems to understand expected program versions.

Monitor devices configuration logs which may contain alerts that indicate whether a program download has occurred. Devices may maintain application logs that indicate whether a full program download, online edit, or program append function has occurred.

ICSAN2057AnalyticObject v1.0 Modified
Glexia's Take

Analyst context for executives and security teams

Analyst confidence High

AN2057 is an ICS detection analytic focused on noticing when control-system programs are downloaded or modified. For business leaders, the practical issue is change assurance: unauthorized or unexpected logic changes can affect operational reliability and safety, but visibility is often uneven because not all devices generate alarms for these events.

Executive priority

Prioritize this analytic where operational continuity depends on trusted controller or automation logic. Leaders should ask whether the organization can prove what program version should be running, detect a download or online edit, and reconcile device activity against approved change records. This supports incident decision-making, compliance evidence, and cyber-physical risk governance, but the supplied ATT&CK object does not specify platforms, tactics, or guaranteed detection coverage.

Technical view

SOC, IR, OT engineering, and detection teams should validate whether device alarms, ICS automation protocol activity, remote management protocol activity, device configuration logs, and application logs expose program download or modification events. Key event types to confirm include full program download, online edit, and program append functions. Asset management data should be used as the baseline for expected program versions so alerts can be compared against authorized changes.

Likely telemetry

  • Device alarms indicating program downloads or related change activity
  • ICS automation protocol functions associated with program download or modification
  • Remote management protocol functions associated with program download or modification
  • Device configuration logs containing program download alerts
  • Device application logs showing full download, online edit, or program append events

Detection direction

  • Validate which devices actually produce alarms for program downloads; the official text notes that not all devices do.
  • Correlate protocol-observed download or modification functions with device logs and approved change windows.
  • Compare observed program versions or change events against asset management systems and expected program baselines.
  • Tune triage to distinguish approved engineering activity from unexpected modification events.
  • Document blind spots where devices, protocols, or logs do not expose program download evidence.

Mitigation priorities

  • Establish and maintain asset-management baselines for expected program versions.
  • Ensure operational change processes capture authorized program downloads, online edits, and appends.
  • Enable and retain available device configuration and application logs where supported.
  • Review monitoring coverage for ICS automation and remote management protocol functions related to program modification.
  • Use gaps identified by this analytic to prioritize logging, asset inventory, and change-control improvements.
Analyst notes and limits

This is an ATT&CK ICS detection analytic, not a technique description. Its value is strongest as a coverage validation checklist for OT monitoring and engineering change assurance. There are no supplied relationships, tactics, labels, aliases, or platforms, so interpretation should remain focused on the official description.

Official detection logic is not provided, and the object states that not all devices produce relevant alarms. Local device capabilities, protocol visibility, log retention, asset inventory quality, and change-management records are required to determine practical coverage.

Official MITRE ATT&CK definition

Analytic 2057

Monitor device alarms for program downloads, although not all devices produce such alarms.

Monitor for protocol functions related to program download or modification. Program downloads may be observable in ICS automation protocols and remote management protocols.

Consult asset management systems to understand expected program versions.

Monitor devices configuration logs which may contain alerts that indicate whether a program download has occurred. Devices may maintain application logs that indicate whether a full program download, online edit, or program append function has occurred.

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.

Relationship explorer

All related ATT&CK context

No relationships are available in the current normalized data for this object.

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
c5ab1e9ae3a54e3c...
Imported snapshots across ATT&CK releases (1)
Release Bundle imported Object version Modified Status Raw hash
19.1 1.0 Current bundle c5ab1e9ae3a5…
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 AN2057
    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.