Siemens S7 PLC security depends on more than the application logic running in a controller. The S7-1200 combines a bootloader, real-time operating system, networking services, web components and hardware interfaces. Research into this architecture highlights a broader lesson for industrial automation engineers: service features retained for diagnostics or maintenance can become a security concern when they provide powerful access outside the normal firmware update process.
Why PLC architecture matters to security
Programmable logic controllers connect sensor inputs to actuator outputs by executing control logic. In modern installations, however, a PLC is also a complex embedded computer. Its firmware must initialize hardware, manage memory, run communication stacks, provide configuration services and support application execution. Each component adds functionality, but it also increases the amount of software and interface behavior that must be understood and protected.
This matters because cyber-physical incidents have shown that attacks on industrial control systems can affect physical operations. A weakness in a controller’s low-level startup or maintenance path may therefore have consequences beyond conventional IT systems. The S7-1200 is a useful case study because its firmware and boot process can be examined as a connected system, from flash storage and startup checks to services exposed through the network.
Inside the S7-1200 boot and firmware design
The examined S7-1200 hardware uses an ARM Cortex-R4 processor, RAM and multiple forms of flash storage. A serial flash device stores the bootloader, while NAND flash holds firmware. During startup, the bootloader initializes hardware, checks integrity values and loads firmware into memory. It also establishes interrupt handling and memory mappings before transferring control to the main software.
The firmware runs on ADONIS, a real-time operating system, and includes a broad range of components. These include industrial communication and automation services, file-system support, a TCP/IP stack, and Siemens web-server functionality. The firmware also contains memory-management facilities and multiple execution modes, with memory regions configured through a memory protection unit.
That component diversity is operationally understandable: a PLC must support control, diagnostics, communications and configuration. From a security perspective, though, every parser, service and update path deserves attention. The research also examined the MiniWeb server and its scripting language, MWSL. Custom pages and request handlers are additional surfaces where input handling and output encoding matter. The general engineering principle is to assess these features as part of the controller’s attack surface, not as unrelated conveniences.
The legacy UART special access feature
The central finding concerned a special access feature in the bootloader, available through a UART interface. After hardware initialization, the bootloader briefly listens for a specific handshake string. If the handshake is accepted, it enters a command mode with handlers for diagnostic and maintenance operations.
Some commands perform checks or report information. Others relate to memory, flash storage and update operations. The researchers focused on two mechanisms: a handler that can write data to internal RAM, and another that dispatches through a secondary function-handler list. By combining these behaviors, they demonstrated a route to arbitrary code execution in the bootloader environment.
The initial write capability was limited to IRAM and described as slow and error-prone. A small stager payload could then extend the capability to arbitrary reads and writes across PLC memory, allowing further payload injection. The security significance is not simply that a UART connector exists. It is that a legacy interface, reachable during startup and operating with privileged access, exposed functionality that could bypass assumptions made about normal application-level controls.
Firmware integrity is important, but not the whole story
The startup and update design included integrity checks. The bootloader checked its own CRC and firmware CRC, while the firmware update format included an ECDSA signature over a SHA-256 hash of the compressed firmware contents. These mechanisms help protect the intended boot and update flows.
However, security controls around the standard update process do not automatically secure every alternate maintenance path. The research described a bootloader update function that skipped signature verification, as well as special access commands capable of interacting with memory and flash. The practical takeaway is that integrity protections must be evaluated across all routes that can alter or execute code—not only the documented firmware update mechanism.
Practical lessons for automation teams
For plant operators, system integrators and engineers responsible for PLC deployments, the findings support several practical review priorities:
- Inventory service interfaces. Identify UART and other maintenance or diagnostic connections, including those not used in normal operation.
- Assess legacy features. Determine whether retained bootloader functions are necessary and what level of access they provide.
- Review update paths end to end. Check that integrity and authenticity protections apply consistently to normal updates and alternate recovery or service mechanisms.
- Include firmware components in risk reviews. Web servers, scripting interpreters, network stacks and parsers are part of the PLC’s security boundary.
- Coordinate with the vendor. Confirm supported hardening and maintenance practices for the specific controller and firmware version in use.
These steps do not imply that every exposed interface is remotely reachable or exploitable in a given installation. They help teams understand the actual device configuration and avoid relying on assumptions about undocumented or rarely used features.
Conclusion: treat the whole controller as a security boundary
The S7-1200 case demonstrates how a complex PLC can combine robust elements—such as firmware integrity checks—with legacy access features that create a separate risk. For industrial automation teams, Siemens S7 PLC security should therefore be considered across the complete lifecycle: hardware, bootloader, firmware services, update mechanisms and physical maintenance interfaces. Reviewing and reducing unnecessary legacy access is a practical step toward making controller security more consistent with the protections expected elsewhere in the industrial control system.