Skip to content

Secure PLC coding

The Top 20 Secure PLC Coding Practices. Part 19 - Log PLC hard stops and trend them on the HMI

Fault events indicate why a PLC shuts down so that the issue can be addressed before a restart.

Eugen WypiorEugen Wypior

Published 3 min read

PLCsecure codingOT securityIEC 62443ICS
Contents
  1. Guidance
  2. Why?
  3. References
  4. What’s next?
  5. Do you require help with secure coding of your PLCs?
  6. If you have any questions or require help in securely coding your PLCs, please contact SEQRED. SEQRED specialises in providing bespoke OT and IoT cybersecurity solutions. Our services cover such areas as Critical Infrastructure Protection, Cloud Services Security or Audits, and Threat Intelligence. For a full list of our services visit our services page – https://seqred.pl/en/services/
  7. About this article

Part 19 of the Top 20 Secure PLC Coding Practices series, originally published by admeritia GmbH (Langenfeld, Germany). SEQRED reproduces the series under the open license granted by the copyright holder. Full specification: plc-security.com.

**Store PLC hard stop events from faults or shutdowns for retrieval by HMI alarm systems to consult before PLC restarts. Time sync for more accurate data. **

Security Objective Target Group
Monitoring Integration / Maintenance Service Provider

Guidance

Fault events indicate why a PLC shuts down so that the issue can be addressed before a restart.

Some PLCs may have error codes from the last case where the PLC faulted or shut down improperly. Record those errors and then clear them. It might be a good idea to report those errors to the HMI as informational data or perhaps to a syslog server, if those features and that infrastructure exist.

Most PLCs also have some kind of first scan feature that generates events. It is a behavior that nearly all PLC equipment has in some form. It is basically one or more flags or a designated routine that is executed on the first scan of a PLC after it “wakes up.” This First Scan should be logged and tracked.

Why?

Beneficial for …? Why?
Security Logs enable troubleshooting in case of an incident. Before a PLC becomes operational, especially after having experienced problems, it is important to ensure it is trustworthy.
**Reliability ** Logs are also good sources for debugging if the event was not caused maliciously.
**Maintenance ** /

References

Standard/framework Mapping
**MITRE ATT &CK for ICS ** Tactic:TA009 - Inhibit Response Function Technique:T0816 - Device Restart/Shutdown
**ISA 62443-3-3 ** SR 7.6: Network and security configuration settings
**ISA 62443-4-2 ** CR 7.6: Network and security configuration settings
MITRE CWE CWE-778: Insufficient Logging

What’s next?

In the next article of The Top 20 Secure PLC Coding Practices series, you will find out about monitoring PLC memory usage and trending it on the HMI .

Do you require help with secure coding of your PLCs?

If you have any questions or require help in securely coding your PLCs, please contact SEQRED. SEQRED specialises in providing bespoke OT and IoT cybersecurity solutions. Our services cover such areas as Critical Infrastructure Protection, Cloud Services Security or Audits, and Threat Intelligence. For a full list of our services visit our services page – https://seqred.pl/en/services/

About this article

This article is reproduced from the Top 20 Secure PLC Coding Practices project coordinated by Sarah Fluchs (admeritia GmbH) and Vivek Ponnada (Nozomi Networks), with support from ISA Global Cybersecurity Alliance and S4 Events.

The full copy of the document is available at plc-security.com.

License

Copyright (c) 2021 admeritia GmbH, Langenfeld/Rheinland, Germany.

Permission is hereby granted, free of charge, to any person obtaining a copy of “Top 20 Secure PLC Coding Practices” and associated documentation files, to deal in the work without restriction, including the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies, subject to preserving this copyright notice.

The work is provided “as is”, without warranty of any kind. Full license at plc-security.com.

See also

  • SEQRED’s synthesis article: Top 20 Secure PLC Coding Practices - a condensed guide
  • Full series: browse all 21 parts under the secure coding tag

Need help in this area?

Our experts will help you assess the risk and plan next steps.

Talk to an expert

We'll discuss scope, methodology, and timeline.

Book a call