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

Detection of malicious or unwanted applications in the ICS environment

So, how do we go about finding malicious or unwanted code in our environment? Typically, the answer would be to find what is running right now and compare the findings against a known good state, a baseline. To give you an example of this method, we will now run a comparison between a baseline file and a current snapshot for Workstation12 in the lab. If you recall from Chapter 7, Active Security Monitoring, in the Assets scan section, we discovered an unusual open port (12345) on that workstation.

Comparing system snapshots to find artifacts

In Chapter 7, Active Security Monitoring, Exercise 2 – Manual inspection of industrial computers, we saw how we can pull system state snapshots from our end devices using msinfo32.exe and netstat. The following example shows how if we had a known good baseline copy of these snapshots, we could compare them against a current, freshly pulled snapshot. A convenient...