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

Example incident report form

This, or a similar form, should be used for handling, tracking, and recording incident response activities:

Let's look at the different fields shown in the preceding form:

  • Fields 1 through 5 should be completed based on the initial incident report alone. It is expected that these fields are completed before you start the severity determination discussions.
  • Field 6 is intended to hold a more technical description of the incident based on analysis by the Technology Owner(s).
  • Field 7 holds the name of the Incident Lead. This field can be completed as soon as the Incident Lead is assigned.
  • Field 8 holds the current incident status as incident handling proceeds.
  • Field 9 contains the case number and the names of related incidents. These incidents could be previous or current and could be within OT, an IT incident, or an externally known incident.
  • Field 10 is a categorization of a type of incident. More...