T1601 Elastic Security · Elastic

Detect Modify System Image in Elastic Security

This detection identifies adversary attempts to modify the operating system image of embedded network devices such as routers, switches, and firewalls. Adversaries may replace or patch the monolithic OS binary to weaken defenses, implant backdoors, or add new capabilities. Detection focuses on unauthorized TFTP/SCP image transfers to network devices, unexpected system image version changes logged via syslog, privilege escalation events on device management interfaces, and anomalous file copy operations on network management hosts. Both live in-memory modifications and persistent storage-based changes (applied on next boot) are targeted.

MITRE ATT&CK

Tactic
Defense Evasion
Technique
T1601 Modify System Image
Canonical reference
https://attack.mitre.org/techniques/T1601/

Elastic Detection Query

Elastic Security (Elastic)
eql
any where event.dataset in ("system.syslog", "cisco.ios") and message : ("copy tftp*" or "copy ftp*" or "copy scp*" or "boot system flash*" or "boot system tftp*" or "install add file*" or "install activate*" or "INTEGRITY_FAILED*" or "SIGNATURE_FAILED*" or "FLASH-5-SIGNIFICANT_FLASH*")
high severity medium confidence

Elastic EQL translation of the T1601 detection logic. Detects network device OS image modification attempts by correlating syslog messages from network infrastructure (Cisco IOS/NX-OS, Juniper JunOS, etc.

Data Sources

Elastic Agent System integrationCisco IOS integration

Required Tables

logs-system.syslog-*logs-cisco.ios-*

False Positives & Tuning

  • Authorized network engineers performing scheduled firmware upgrades during maintenance windows via TFTP/SCP
  • Network management platforms (Cisco Prime, SolarWinds, Ansible AWX) performing automated image distribution and version compliance enforcement
  • Legitimate disaster recovery operations restoring a known-good baseline image after hardware failure
  • Vendor-assisted software update procedures conducted by authorized third-party contractors with change tickets
Download portable Sigma rule (.yml)

Other platforms for T1601


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Simulate Unauthorized IOS Image Copy via TFTP on Management Host

    Expected signal: DeviceNetworkEvents: UDP port 69 connection attempt to target IP. DeviceProcessEvents: atftp process with command line containing .bin filename. Syslog: copy tftp message.

  2. Test 2Inject Cisco IOS System Image Modification Syslog Messages

    Expected signal: Syslog table in Microsoft Sentinel (or Splunk syslog index) should receive entries with FILESYS, SYS-5-RELOAD, and SYS-6-BOOTTIME facility/message patterns from ROUTER-01.

  3. Test 3Network Device Image Downgrade Simulation via SNMP Write

    Expected signal: CommonSecurityLog or Syslog: SNMP write attempts to network device. Syslog: MGMTBOOTERROR and downgrade notification messages. DeviceNetworkEvents: SNMP (UDP 161/162) traffic to test device.

Unlock Pro Content

Get the full detection package for T1601 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections