Siemens SIMATIC S7-1200 and S7-1500 controllers ship with strong protection features that are mostly optional, so a CPU commissioned with defaults will accept program downloads from anyone who can reach TCP port 102. Siemens ProductCERT advisories for these CPU families repeat the same mitigations: password-protect S7 communication, allow only secure PG/PC and HMI communication, protect the TIA Portal project and keep port 102 off untrusted networks. This guide turns those mitigations into a hardening baseline: how access works in the CPU and in TIA Portal, who should hold privileged rights, how HMIs, OPC UA clients and scripts connect, what to log, and the misconfigurations seen most often. It is for automation engineers, OT security leads and integrators who build or maintain Siemens S7 systems. Feature names and firmware dependencies change between versions, so confirm each setting against the manual for your CPU firmware and TIA Portal version.
This is an independent guide from NHI Mgmt Group, based on Siemens's public documentation as of November 2026. It is not sponsored or reviewed by Siemens. Product features change, so confirm settings against Siemens's current documentation.
Key takeaways
- Set an access level and a password on every CPU. Without one, any host on the network can read, change and download the program; the advisories call this "password protection for S7 communication".
- Turn on "Only allow secure PG/PC and HMI communication". Siemens recommends this setting in its ProductCERT advisories, together with an individual password for confidential PLC configuration data, both introduced with TIA Portal V17 and matching firmware.
- Protect the TIA Portal project as a privileged asset. UMAC project protection, roles and function rights such as "Download to PLC" control who can change production logic, and protection cannot be removed once enabled.
- Layer network controls on top. Siemens advisories recommend restricting access to port 102 alongside CPU settings, so keep network restriction in place however well the CPU is configured.
- Monitor program downloads and mode changes. Stuxnet modified Siemens PLC logic by downloading code blocks; unexpected downloads, uploads and RUN/STOP changes are the events that matter.
How identity and access work in Siemens S7 and TIA Portal
Access control sits in three places, and hardening needs all three.
- The CPU: S7-1200 and S7-1500 CPUs have configurable access levels, typically Full access including fail-safe, Full access, Read access, HMI access and No access, each protected by its own password. The level you choose decides what an unauthenticated client can do; the password unlocks higher levels. Siemens advisories also describe the
ENDIS_PWinstruction, which can disallow client connections even when the correct password is supplied, and, on the S7-1500, additional access protection set from the CPU display. - The communication channel: TIA Portal V17 and corresponding firmware introduced TLS-protected PG/PC and HMI communication with device-specific certificates, and an individual password protecting confidential PLC configuration data such as private keys. Siemens advisory SSA-568427 explains why this matters: the built-in global private key that protected legacy configuration data and legacy PG/PC and HMI communication can be recovered offline from a single CPU of the family.
- The engineering project: TIA Portal User Management and Access Control (UMAC) protects the project with users, roles and function rights. Users can be local to the project or central users and groups held in the User Management Component (UMC), which also supports single sign-on.
| Layer | Control | What it stops | Limits |
|---|---|---|---|
| CPU access level | Access level plus passwords per level | Unauthenticated read, write and program download over port 102 | Guessable or shared passwords; advisories show some attacks reach port 102 without valid credentials |
| CPU connection control | ENDIS_PW instruction; S7-1500 display access protection | Remote client connections even with a correct password, during production | Must be designed into the program and operating procedure |
| Secure communication | "Only allow secure PG/PC and HMI communication", certificates | Interception and tampering of engineering and HMI traffic; reliance on the global key | Needs TIA Portal V17 or later, updated firmware and updated HMIs |
| Confidential configuration data | Individual password for PLC configuration data | Extraction of private keys and protected data from project or memory card | Password must be stored and recovered securely |
| Project protection (UMAC) | Users, roles, function rights, password policies | Unauthorised edits and downloads from the engineering project | Cannot be removed once enabled; project files still need protection at rest |
| Know-how and copy protection | Block passwords, binding to CPU or memory card serial | Casual viewing and copying of intellectual property | An IP protection feature, not a security boundary |
Admin roles and privileged access
Treat every right that changes controller behaviour as privileged. TIA Portal function rights make this explicit: "Download to PLC", "Control PLC program online", "Edit PLC program", "Edit safety-related project data", "Edit hardware configuration", "Edit security module configuration" and "Edit project via Openness API" are separate rights that can be assigned to roles.
- Use the system roles as a starting point only: "Engineering-Administrator" holds all engineering rights; "Engineering-Standard" holds all except sensitive ones such as managing users and roles. Build narrower roles, for example a maintenance role with "Monitor PLC program" but not "Download to PLC".
- Separate safety rights: restrict "Edit safety-related project data" and the fail-safe CPU access level to the small group responsible for the safety programme.
- Prefer central users for teams: UMC central users and groups give one place to remove leavers; UMC requires a licence beyond 10 accounts. Keep local project users for small or isolated projects, with a password policy set in the project.
- Disable the Anonymous user: it needs no password, is disabled by default and cannot be deleted; giving it rights undoes project protection.
- Vault CPU passwords: access level passwords and the configuration data password are shared secrets; hold them in a vault, record who retrieves them, and rotate after staff or integrator changes. See the Engineering Workstation Security Guide and OT and ICS Identity and Access Guide.
- Control the engineering workstation: the person at TIA Portal with a vaulted password is the most privileged identity in the cell; engineering workstations need dedicated hardening, no email or browsing, and brokered remote access.
Integrations, API tokens and service accounts
S7 CPUs talk to many non-human clients, and each one is a credential or a trust relationship to manage.
- HMIs and SCADA: WinCC panels and SCADA servers connect with the HMI access level or higher. Use secure HMI communication where all devices support it, and give HMIs the lowest level that works.
- PUT/GET communication: the CPU option that permits PUT/GET access from remote partners lets other devices read and write data without the optimised access model. Leave it disabled unless a specific legacy partner needs it, and document the partner.
- OPC UA server: where the CPU's OPC UA server is used, disable the "None" security policy, require Sign or SignAndEncrypt, require user authentication rather than anonymous access, and manage the server and client certificates as machine identities with renewal dates. See the OPC UA Security Guide.
- Web server: enable it only when needed, restrict it to HTTPS, and create named web server users with the minimum rights instead of granting rights to "Everybody".
- TIA Portal Openness scripts: automation scripts and CI-style build tools that use the Openness API act with the rights of the user running them; grant "Edit project via Openness API" only to service users created for that purpose, and keep scripts in version control with review.
- Multiuser engineering and TIA Project Server: the project server holds the master copy of production logic; restrict server access to engineering roles and back it up offline.
Machine credentials in OT (HMI passwords, OPC UA certificates, service users) rarely expire and are seldom inventoried. See the Device and IoT Identity Guide.
Logging and detection
Siemens PLCs record events locally, but most detection value comes from watching the network and the engineering estate.
| Event | Where to see it | ATT&CK for ICS | Response |
|---|---|---|---|
| Program download to CPU | Network monitoring of S7 traffic on TCP 102; CPU diagnostic buffer; TIA Project Server history | T0843 Program Download, T0889 Modify Program | Confirm a change ticket; compare online and offline blocks |
| Program upload from CPU | Network monitoring | T0845 Program Upload | Check source host; uploads from unknown hosts suggest reconnaissance |
| RUN to STOP or mode change | Diagnostic buffer, HMI alarms, network monitoring | T0858 Change Operating Mode | Treat as an operational incident until explained |
| Failed access level password attempts | Diagnostic buffer and security events, where supported by firmware | T0866 Exploitation of Remote Services (attempts) | Identify the source; block at the conduit |
| New host talking to port 102 | Firewall and passive OT monitoring | T0866 Exploitation of Remote Services | Investigate; only engineering workstations and HMIs should connect |
| Changes to project files | File integrity monitoring on engineering workstations and project server | T0873 Project File Infection | Verify against version history |
- Collect the diagnostic buffer: read it regularly through TIA Portal, the web server or SCADA diagnostics, and keep copies, because the buffer is a ring and older entries are overwritten.
- Compare online and offline programs: scheduled comparisons between the CPU and the approved project version catch unauthorised changes. Siemens notes in SSA-232418 that the code running on a device can be made to differ from the stored source, so pair comparisons with network monitoring rather than relying on them alone.
- Remember Stuxnet: it downloaded altered code and data blocks to Siemens PLCs and manipulated the operator's view, including through a rootkit in a replaced Step 7 communication library. Integrity of the engineering workstation is part of PLC integrity. See the PLC Security Guide.
Hardening baseline
- Update firmware and TIA Portal: apply Siemens security updates promptly and move CPUs at least to the fixed versions in current Siemens ProductCERT advisories (for example S7-1500 V2.9.2 and S7-1200 V4.5.0), migrate the project to the matching TIA Portal version and redeploy. Test on a spare CPU or PLCSIM Advanced first, and keep the previous project version and firmware for rollback.
- Set access protection: choose HMI access or No access as the unauthenticated level, set strong unique passwords per level (Siemens guidelines suggest at least 12 mixed characters where possible), and vault them.
- Enable secure communication: set "Only allow secure PG/PC and HMI communication" and configure the confidential PLC configuration data password; plan HMI and SCADA updates before enforcing, because legacy clients will stop connecting.
- Close optional services: disable PUT/GET, the web server, OPC UA and unused interfaces unless needed; where needed, harden them as above.
- Use run-time connection controls: where operations allow, use ENDIS_PW or S7-1500 display access protection to block remote connections during production, with a documented procedure to allow them for maintenance.
- Protect the project: enable UMAC project protection, define roles, disable Anonymous, set password policies, and protect project files and memory cards at rest.
- Segment: place CPUs in cells behind firewalls following Siemens' cell protection concept, allow TCP 102 only from named engineering workstations and HMIs, and broker all remote access. See the OT Network Segmentation, Purdue Model and IEC 62443 Zones and Conduits Guide.
- Physical controls: lock cabinets, control memory card handling and keep CPUs in RUN with documented procedures for mode changes.
Brownfield versus greenfield: new projects should start with secure communication and project protection on day one. For installed S7-300 and S7-400 systems, which predate these features, the realistic controls are segmentation, network monitoring, engineering workstation hardening and a migration plan; follow the mitigations in each Siemens advisory for legacy products. For S7-1200 and S7-1500 fleets, prioritise CPUs controlling high-consequence processes and those reachable from wider networks.
Framework mapping
| Baseline area | NIST SP 800-53 Rev. 5 | NIST CSF 2.0 | ISA/IEC 62443-3-3 |
|---|---|---|---|
| CPU access levels and passwords | AC-3, IA-5 | PR.AA | FR1 Identification and authentication control, FR2 Use control |
| Project roles and function rights | AC-2, AC-6, CM-5 | PR.AA | FR2 Use control |
| Secure PG/PC and HMI communication | SC-8, SC-23, IA-3 | PR.DS | FR3 System integrity, FR4 Data confidentiality |
| Disabling optional services | CM-7 | PR.PS | FR7 Resource availability (least functionality) |
| Segmentation of port 102 | SC-7 | PR.IR | FR5 Restricted data flow |
| Download and mode change monitoring | SI-4, AU-6 | DE.CM | FR6 Timely response to events |
| Firmware updates and legacy CPUs | RA-5, SA-22 | ID.RA | 62443-2-3 patch management |
Detection and measurement
- Protected CPUs: percentage of S7-1200 and S7-1500 CPUs with an access level other than Full access for unauthenticated clients.
- Secure communication coverage: percentage of CPUs enforcing "Only allow secure PG/PC and HMI communication".
- Advisory exposure: CPUs running firmware below the fixed versions in open ProductCERT advisories, weighted by process consequence.
- Unexplained downloads: program downloads detected on the network without a matching change record (target zero).
- Port 102 exposure: hosts other than approved engineering workstations and HMIs seen connecting to CPUs.
- Project protection: percentage of production TIA Portal projects with UMAC enabled and Anonymous disabled.
Common misconfigurations
- Full access left as default: CPUs commissioned without an access level password, so any host on the cell network can download a program.
- One password everywhere: the same access level password on every CPU in a plant, known to every integrator who has worked there.
- Legacy communication kept for one old HMI: secure communication never enforced because a single panel was not updated, leaving all traffic dependent on the global key described in SSA-568427.
- PUT/GET and web server enabled by template: options switched on in a library project and copied to every CPU.
- Know-how protection treated as security: block passwords used instead of access protection, though they protect intellectual property rather than control access.
- Unprotected project archives: TIA Portal archives and memory card images on shared drives or laptops, exposing logic and, before V17 protection, confidential configuration data.
Practitioner checklist
- Inventory CPUs with model, firmware and open ProductCERT advisories; plan updates to fixed versions.
- Set an access level and unique vaulted passwords on every S7-1200 and S7-1500 CPU.
- Enforce "Only allow secure PG/PC and HMI communication" and set the PLC configuration data password.
- Disable PUT/GET, web server, OPC UA and unused interfaces unless documented as required.
- Enable UMAC project protection with narrow roles; disable the Anonymous user; restrict "Download to PLC" and safety rights.
- Restrict TCP 102 to approved engineering workstations and HMIs through cell firewalls.
- Use ENDIS_PW or S7-1500 display access protection to block remote connections during production where feasible.
- Monitor downloads, uploads and mode changes on the network and compare online and offline programs.
- Harden engineering workstations and protect project archives and memory cards.
Standards and references
- Siemens ProductCERT: SSA-568427 Weak Key Protection Vulnerability in SIMATIC S7-1200 and S7-1500 CPU Families
- Siemens ProductCERT: SSA-434534 Memory Protection Bypass Vulnerability in SIMATIC S7-1200 and S7-1500 CPU Families
- Siemens ProductCERT: SSA-232418 Vulnerabilities in SIMATIC S7-1200 and SIMATIC S7-1500 CPU Families
- Siemens: Operational Guidelines for Industrial Security
- Siemens: TIA Portal V20 documentation, managing users and roles
- MITRE ATT&CK: Stuxnet (S0603)
- MITRE ATT&CK: Program Download (T0843)
- CISA: Primary Mitigations to Reduce Cyber Threats to Operational Technology
Related NHI Mgmt Group resources: PLC Security Guide · Engineering Workstation Security Guide · OT Security Guide · ICS Advisory Triage and OT Vulnerability Management Guide · Manufacturing Cybersecurity Programme Guide