Skip to content

Secure PLC coding

The Top 20 Secure PLC Coding Practices. Part 1 - Introduction

For many years, the workhorses of industrial automation as some call the Programmable Logic Controllers (PLCs) have been insecure by design. Several years into customising and appl

Eugen WypiorEugen Wypior

Published 4 min read

PLCsecure codingOT securityIEC 62443ICS
Contents
  1. Who should read and implement
  2. What are the benefits of applying
  3. What’s next?
  4. Do you require help with secure coding of your PLCs?
  5. 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/****
  6. About this article

Part 1 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.

For many years, the workhorses of industrial automation as some call the Programmable Logic Controllers (PLCs) have been insecure by design. Several years into customising and applying best practices from IT gave rise to secure protocols, encrypted communications, network segmentation etc. However, to date, there has not been a focus on using the characteristic features in PLCs (or SCADA/DCS) for security, or how to program PLCs with security in mind. This gap has been filled now with the PLC Security Top 20 List project initiated with Jake Brodsky’s talk at the S4 annual event in Miami Beach in 2020 (see link to talk below this article).

Over the next weeks, in its ‘OT Thursdays’ series SEQRED will publish details of each of the 20 Secure PLC Coding Practices.

Who should read and implement

the Secure PLC Coding Practices?

These practices have been created as guidelines for engineers creating software (ladder logic, function charts etc.) to help improve the security posture of Industrial Control Systems. These practices leverage natively available functionality in the PLC/DCS. Little to no additional software tools or hardware is needed to implement these practices. They can all be fit into the normal PLC programming and operating workflow. More than security expertise, good knowledge of the PLCs to be protected, their logic, and the underlying process is needed for implementing these practices.

To fit the scope of the Top 20 Secure PLC Coding practices list, practices need to involve changes made directly to a PLC.

What are the benefits of applying

Secure PLC Coding Practices?

Using these practices clearly has security benefits – mostly either reducing the attack surface or enabling faster troubleshooting if a security incident were to happen. However, many practices have additional benefits beyond security. Some also make the PLC code more reliable, easier to debug and maintain, easier to communicate, and possibly also leaner. Further, the secure PLC coding practices not only help users in the event of a malicious attacker but also make the PLC code more robust to withstand accidental misconfiguration or human error.

What’s next?

The second article in this series will cover the first Secure PLC Coding Practice - Modularising PLC code.

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