Skip to content

Blog

IT and OT cybersecurity insights - threat analysis, guides, vulnerability research, and regulatory updates.

All articles

Category
Author

T

The Top 20 Secure PLC Coding Practices. Part 1 - IntroductionSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 10 - Validate indirectionsSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 11 - Assign designated register blocks by function (read/write/validate)Secure PLC coding
The Top 20 Secure PLC Coding Practices. Part 12 - Instrument for plausibility checksSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 13 - Validate inputs based on physical plausibilitySecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 14 - Disable unneeded / unused communication ports and protocolsSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 15 - Restrict third-party data interfacesSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 16 - Define a safe process state in case of a PLC restartSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 17 - Summarise PLC cycle times and trend them on the HMISecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 18 - Log PLC uptime and trend it on the HMISecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 19 - Log PLC hard stops and trend them on the HMISecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 2 - Modularise PLC codeSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 20 - Monitor PLC memory usage and trend it on the HMISecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 21 - Trap false negatives and false positives for critical alertsSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 3 - Track operating modesSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 4 - Leave operational logic in the PLC wherever feasibleSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 5 - Use PLC flags as integrity checksSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 6 - Use cryptographic and / or checksum integrity checks for PLC codeSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 7 - Validate timers and countersSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 8 - Validate and alert for paired inputs / outputsSecure PLC coding
The Top 20 Secure PLC Coding Practices. Part 9 - Validate HMI input variables at the PLC level, not only at HMISecure PLC coding
Two vulnerabilities in the Gameloop emulator - root access through su and through ADBCybersecurity

We'll discuss scope, methodology, and timeline.

Book a call