Book Image

Industrial Cybersecurity - Second Edition

By : Pascal Ackerman
Book Image

Industrial Cybersecurity - Second Edition

By: Pascal Ackerman

Overview of this book

With Industrial Control Systems (ICS) expanding into traditional IT space and even into the cloud, the attack surface of ICS environments has increased significantly, making it crucial to recognize your ICS vulnerabilities and implement advanced techniques for monitoring and defending against rapidly evolving cyber threats to critical infrastructure. This second edition covers the updated Industrial Demilitarized Zone (IDMZ) architecture and shows you how to implement, verify, and monitor a holistic security program for your ICS environment. You'll begin by learning how to design security-oriented architecture that allows you to implement the tools, techniques, and activities covered in this book effectively and easily. You'll get to grips with the monitoring, tracking, and trending (visualizing) and procedures of ICS cybersecurity risks as well as understand the overall security program and posture/hygiene of the ICS environment. The book then introduces you to threat hunting principles, tools, and techniques to help you identify malicious activity successfully. Finally, you'll work with incident response and incident recovery tools and techniques in an ICS environment. By the end of this book, you'll have gained a solid understanding of industrial cybersecurity monitoring, assessments, incident response activities, as well as threat hunting.
Table of Contents (26 chapters)
Section 1: ICS Cybersecurity Fundamentals
Section 2:Industrial Cybersecurity – Security Monitoring
Section 3:Industrial Cybersecurity – Threat Hunting
Section 4:Industrial Cybersecurity – Security Assessments and Intel
Chapter 15: Industrial Control System Risk Assessments
Section 5:Industrial Cybersecurity – Incident Response for the ICS Environment


In this chapter, we discussed the ins and outs of Red Team exercises, how they differ from penetration testing, and how the Blue Team fits into things. We then performed an example Red Team engagement for Company Z, where we attacked their ICS and successfully replaced the running firmware of a PLC that is sitting on their industrial network, "safely" tucked away behind a firewall, segmented off from the enterprise network. Along the way, we discussed potential opportunities for the Blue Team to catch our activities and discussed recommendations around better securing the setup.

What we covered in the example Red Team exercise only showed a single approach to accomplishing our goals. By no means should this be used as a playbook to perform such assessments, but it should be used as a guideline to direct you through the phases of an attack.

In the next chapter, we will discuss the ins and outs of a penetration test and get hands-on experience performing one for...