Skip to content

Secure PLC coding

The Top 20 Secure PLC Coding Practices. Part 12 - Instrument for plausibility checks

Integrity oI/O values | Product Supplier Integration / Maintenance Service Provider

Eugen WypiorEugen Wypior

Published 4 min read

PLCsecure codingOT securityIEC 62443ICS
Contents
  1. Guidance
  2. Example
  3. Why?
  4. References
  5. What’s next?
  6. Do you require help with secure coding of your PLCs?
  7. 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/
  8. About this article

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

**Instrument the process in a way that allows for plausibility checks by cross-checking different measurements. **

Security Objective Target Group
Integrity oI/O values Product Supplier Integration / Maintenance Service Provider

Guidance

There are different ways of using physical plausibility for validating measurements:

a) Compare integrated and time-independent measurements

Plausibility checks can be done by integrating or differentiating time-dependent values over a period of time and comparing them to time-independent measurements.

b) Compare different measurement sources

Also, measuring the same phenomenon in different ways can be a good plausibility check. Different measurement sources do not necessarily have to be different physical sensors, but can also mean using alternative communication channels (see examples).

Example

**a) Compare integrated and time-independent measurements **

  • Metered pump and tank level gauge: volumetric change should equal integrated flow.
  • A burner in a boiler: added caloric heat should equal temperature rise.

**b) Compare different measurement sources **

  • Using airspeed, artificial horizon, vertical speed, and altitude in the airplane to measure the phenomenon of the climbing / descending airplane.
  • Comparing process parameter values from independent data loggers (tied into 4-20mA loops or relay contacts and transmitted via independent communication channels) to SCADA system data (coming in the “normal” way through PLC and HMI) and alerting on deviations and significantly off-specified values.

Why?

Beneficial for …? Why?
Security Facilitates monitoring for manipulated values (assuming not all sensors are manipulated at once).
**Reliability ** Prevents acceptance or identifies (for future action) corrupted / wrong measurements as inputs.
**Maintenance ** Rules out the possible physical causes for failures more quickly.

References

Standard / framework Mapping
**MITRE ATT &CK for ICS ** Tactic:TA010 - Impair Process Control Technique:T0806 - Brute Force I/O
**ISA 62443-3-3 ** SR 3.5 : Input validation SR 3.6 : Deterministic Output
**ISA 62443-4-2 ** CR 3.5 : Input validation CR 3.6 : Deterministic Output
MITRE CWE CWE-754: Improper Check for Unusual or Exceptional Conditions

What’s next?

In the next article of The Top 20 Secure PLC Coding Practices series, you will find out about validating inputs based on physical plausibility.

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