A Modicon often runs critical infrastructure — water, power, transport — which makes it a target. Out of the box a PLC trusts everyone; your job is to lock it down. Schneider builds in application protection, a security profile, and Achilles-certified robustness — but only if you turn it on. Work the checklist and watch the controller's exposure shrink.
These are the real first moves on a Modicon M580. Tick each as you apply it and watch the security score climb and the threat note change. None of them is exotic — they're the difference between a controller anyone on the network can reprogram and one that resists a determined attacker.
No single switch makes a PLC "secure" — that's the point of defence in depth. Each layer (network segmentation, disabled services, authentication, signed application, protected sections) buys a little; together they make the controller a hard target. Skip the easy ones and you've left the front door open.
🚪 Disable unused services. FTP, TFTP, HTTP, the EtherNet/IP and Modbus write services — if you don't use it, turn it off. Every open service is a door.
🔑 Authentication & the security profile. Set application & section passwords, enable the high security profile, and give engineers individual logins — no shared blank password.
🧱 Network segmentation. Put the control network behind a firewall/DMZ, separate from IT. An attacker on the office LAN should never reach the PLC directly.
✍️ Integrity. Lock the run/stop key switch, enable event logging (syslog), and use the controller's integrity checks so unauthorised logic changes are detected and recorded.
A vendor says "just set the application password and you're secure." Why is that not enough?