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)
1
Section 1: ICS Cybersecurity Fundamentals
6
Section 2:Industrial Cybersecurity – Security Monitoring
12
Section 3:Industrial Cybersecurity – Threat Hunting
17
Section 4:Industrial Cybersecurity – Security Assessments and Intel
19
Chapter 15: Industrial Control System Risk Assessments
22
Section 5:Industrial Cybersecurity – Incident Response for the ICS Environment

Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “We can see Snort detected the response from testmyids.ca (104.31.77.72) as being malicious.”

A block of code is set as follows:

sd.aler_rt			Feb 15 2021 16:46:11
sd.alert_category	NetworkAttack
sd.alert_message		NMAP Scan detecte
sd.alert_name		nmap_scan
sd.alert_number		11

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

  <localfile>
    <location>Microsoft-Windows-Sysmon/Operational</location>
    <log_format>eventchannel</log_format>
  </localfile>

Any command-line input or output is written as follows:

idstools:
  config:
    ruleset: ‘ETOPEN’

Bold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: “Navigate to the Home | Host | Sysmon dashboard and view the event logs at the bottom of the dashboard screen.”

Tips or important notes

Appear like this.