LiveActive security incident?Get immediate response
MITRE ATT&CK® ICS Asset

A0010: Safety Controller

Safety controllers are typically a type of field device used to perform the safety critical function. Safety controllers often support the deployment of custom programs/logic, similar to a PLC, but can also be tailored for sector specific functions/applications. The safety controllers typically utilize redundant hardware and processors to ensure they operate reliably if a component fails.

ICSA0010ICS AssetObject v1.1Modified
Glexia's Take · Automated analysis

Security context for executives and security teams

Automation confidenceHigh

A safety controller is an embedded ICS asset responsible for safety-critical functions, often using custom logic and redundant hardware to keep operating during component failure. Its business importance is that compromise, misconfiguration, or unauthorized change can affect the last line of automated protection for industrial operations. The ATT&CK relationship context shows this asset is relevant to behaviors such as program download/upload, I/O manipulation, alarm modification, denial of service, restart/shutdown, firmware update mode abuse, process-state monitoring, network discovery/sniffing, and removable media movement.

Executive priority

Treat safety controllers as high-priority cyber-physical risk assets, not ordinary controllers. Leaders should ask whether these devices are inventoried, change-controlled, segmented, monitored, and included in incident response and safety assurance processes. Budget and audit focus should prioritize evidence that only authorized engineering activity can modify safety logic, that unauthorized discovery or network access would be noticed, and that response plans account for scenarios where safety functions may be unavailable, altered, or placed into maintenance/update states.

Technical view

For SOC, OT engineering, and IR teams, the key validation question is whether you can distinguish approved safety-controller maintenance from unauthorized interaction. ATT&CK provides no official detection text for this asset, so coverage must be derived from local architecture and the related techniques targeting it. Validate monitoring around engineering workstations and vendor tools used for program upload/download, online edits, program append, controller tasking changes, firmware/update modes, restart/shutdown events, I/O and alarm setting changes, process state access, and unusual discovery or sniffing near safety networks. Because the asset platform is Embedded, host-level telemetry may be limited; network, engineering-station, controller audit, historian, and operator-console evidence often decide visibility.

Likely telemetry

  • Safety controller inventory, firmware/version, configuration, and logic baselines where available
  • Engineering workstation logs and vendor software activity for upload, download, online edit, append, and tasking changes
  • Controller event/audit logs for mode changes, restart/shutdown, firmware update mode, alarms, overrides, and configuration changes where supported
  • OT network traffic metadata and packet captures for controller communications, discovery, broadcast/multicast, port scanning, and possible adversary-in-the-middle conditions
  • Historian, OPC, HMI, alarm, and process-state records showing reads, writes, alarm changes, and abnormal I/O behavior

Detection direction

  • Build allowlists of expected engineering stations, protocols, maintenance windows, and accounts that may communicate with safety controllers.
  • Alert on program upload/download, online edit, program append, controller tasking changes, alarm setting changes, I/O overrides, restart/shutdown, or firmware/update mode activity outside approved change windows.
  • Correlate network discovery, port scans, broadcast or multicast discovery, and sniffing indicators with asset criticality; these may be early-stage behaviors before controller modification.
  • Compare controller logic/configuration and alarm settings against known-good baselines after maintenance, incidents, or unexplained process anomalies.
  • Tune false positives around legitimate commissioning, testing, vendor maintenance, and safety proof-test activities; require change-ticket correlation rather than treating all engineering activity as malicious.

Mitigation priorities

  • Maintain an authoritative inventory of safety controllers, their network locations, approved engineering paths, firmware/configuration state, and responsible process owners.
  • Enforce strict change management for safety logic, alarm settings, firmware/update modes, and controller tasking, with independent review for safety-critical changes.
  • Limit access to safety controllers to approved engineering workstations, accounts, and maintenance windows; separate safety-system access from general enterprise and control-network access where architecture permits.
  • Baseline and periodically verify controller programs, configurations, alarm settings, and I/O-related settings against approved versions.
  • Monitor and control removable media and third-party/contractor access for environments where safety controllers are isolated but physically reachable.
Additional notes and limits

This object is an ATT&CK for ICS asset, not a technique. The practical value comes from treating it as a critical target class and mapping the related techniques to defensive validation. The supplied relationships indicate a broad set of adversary behaviors that may target safety controllers, especially engineering changes, network discovery, process-state observation, I/O and alarm manipulation, device disruption, and removable media movement.

MITRE provides no official detection guidance for A0010, no tactics for the asset itself, and only the Embedded platform. This take does not assert active exploitation, specific vendor exposure, or guaranteed detection. Local safety architecture, controller capabilities, logging support, engineering workflows, and process hazard analysis are required to determine actual risk and coverage.

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Official MITRE ATT&CK definition

Safety Controller

Safety controllers are typically a type of field device used to perform the safety critical function. Safety controllers often support the deployment of custom programs/logic, similar to a PLC, but can also be tailored for sector specific functions/applications. The safety controllers typically utilize redundant hardware and processors to ensure they operate reliably if a component fails.

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.

60 rows
DomainIDNameRelationship / procedure
ICST0846.003Multicast DiscoverySub-techniqueMulticast Discovery targets this object.
ICST1693.002Module FirmwareSub-techniqueModule Firmware targets this object.
ICST0859Valid AccountsValid Accounts targets this object.
ICST0846.001Port ScanSub-techniquePort Scan targets this object.
ICST0884Connection ProxyConnection Proxy targets this object.
ICST1691Block Operational Technology MessageBlock Operational Technology Message targets this object.
ICST0890Exploitation for Privilege EscalationExploitation for Privilege Escalation targets this object.
ICST0834Native APINative API targets this object.
ICST0801Monitor Process StateMonitor Process State targets this object.
ICST1694Insecure CredentialsInsecure Credentials targets this object.
ICST1692.002Reporting MessageSub-techniqueReporting Message targets this object.
ICST0871Execution through APIExecution through API targets this object.
ICST0842Network SniffingNetwork Sniffing targets this object.
ICST0877I/O ImageI/O Image targets this object.
ICST0851RootkitRootkit targets this object.
ICST0809Data DestructionData Destruction targets this object.
ICST0845Program UploadProgram Upload targets this object.
ICST0821Modify Controller TaskingModify Controller Tasking targets this object.
ICST1693.001System FirmwareSub-techniqueSystem Firmware targets this object.
ICST0866Exploitation of Remote ServicesExploitation of Remote Services targets this object.
ICST0843.001Download AllSub-techniqueDownload All targets this object.
ICST0874HookingHooking targets this object.
ICST0878Alarm SuppressionAlarm Suppression targets this object.
ICST0830Adversary-in-the-MiddleAdversary-in-the-Middle targets this object.
ICST0814Denial of ServiceDenial of Service targets this object.
ICST1692.001Command MessageSub-techniqueCommand Message targets this object.
ICST1695.002EthernetSub-techniqueEthernet targets this object.
ICST0835Manipulate I/O ImageManipulate I/O Image targets this object.
ICST0843.002Online EditSub-techniqueOnline Edit targets this object.
ICST0843.003Program AppendSub-techniqueProgram Append targets this object.
ICST0868Detect Operating ModeDetect Operating Mode targets this object.
ICST0820Exploitation for EvasionExploitation for Evasion targets this object.
ICST1694.001Default CredentialsSub-techniqueDefault Credentials targets this object.
ICST0889Modify ProgramModify Program targets this object.
ICST0840Network Connection EnumerationNetwork Connection Enumeration targets this object.
ICST0885Commonly Used PortCommonly Used Port targets this object.
ICST0843Program DownloadProgram Download targets this object.
ICST0800Activate Firmware Update ModeActivate Firmware Update Mode targets this object.
ICST0869Standard Application Layer ProtocolStandard Application Layer Protocol targets this object.
ICST0846Remote System DiscoveryRemote System Discovery targets this object.
ICST1693Modify FirmwareModify Firmware targets this object.
ICST1691.001Command MessageSub-techniqueCommand Message targets this object.
ICST0861Point & Tag IdentificationPoint & Tag Identification targets this object.
ICST1692Unauthorized MessageUnauthorized Message targets this object.
ICST0892Change CredentialChange Credential targets this object.
ICST1691.002Reporting MessageSub-techniqueReporting Message targets this object.
ICST1695Block CommunicationsBlock Communications targets this object.
ICST0846.002Broadcast DiscoverySub-techniqueBroadcast Discovery targets this object.
ICST0881Service StopService Stop targets this object.
ICST0872Indicator Removal on HostIndicator Removal on Host targets this object.
ICST0838Modify Alarm SettingsModify Alarm Settings targets this object.
ICST0862Supply Chain CompromiseSupply Chain Compromise targets this object.
ICST0847Replication Through Removable MediaReplication Through Removable Media targets this object.
ICST0888Remote System Information DiscoveryRemote System Information Discovery targets this object.
ICST1695.003Wi-FiSub-techniqueWi-Fi targets this object.
ICST0858Change Operating ModeChange Operating Mode targets this object.
ICST0806Brute Force I/OBrute Force I/O targets this object.
ICST0816Device Restart/ShutdownDevice Restart/Shutdown targets this object.
ICST0848Rogue MasterRogue Master targets this object.
ICST1695.001Serial COMSub-techniqueSerial COM targets this object.
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.1
Created
Modified
Raw hash
daf468fa75f8e253...
Imported snapshots across ATT&CK releases(1)
ReleaseBundle importedObject versionModifiedStatusRaw hash
19.11.1Current bundledaf468fa75f8…
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]
    Guidance - NIST SP800-82

    Keith Stouffer. (2015, May). Guide to Industrial Control Systems (ICS) Security. Retrieved March 28, 2018.

    Open source URL
  2. [2]
    SIGTTO ESD 2021

    Society of International Gas Tanker & Terminal Operators Ltd. (2021). ESD Systems: Recommendations for Emergency Shutdown and Related Safety Systems (Second Edition). Retrieved September 28, 2023.

    Open source URL
  3. [3]
    mitre-attackA0010
    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.