You're reading from Industrial Cybersecurity Efficiently monitor the cybersecurity posture of your ICS environment

Product type Paperback

Published in Oct 2021

Publisher Packt

ISBN-13 9781800202092

Length 800 pages

Edition 2nd Edition

Tools

Kali Linux

Concepts

Cybersecurity

Author (1):

Pascal Ackerman

Preface

1. Section 1: ICS Cybersecurity Fundamentals

2. Chapter 1: Introduction and Recap of First Edition FREE CHAPTER

3. Chapter 2: A Modern Look at the Industrial Control System Architecture

4. Chapter 3: The Industrial Demilitarized Zone

5. Chapter 4: Designing the ICS Architecture with Security in Mind

6. Section 2:Industrial Cybersecurity – Security Monitoring

7. Chapter 5: Introduction to Security Monitoring

8. Chapter 6: Passive Security Monitoring

9. Chapter 7: Active Security Monitoring

10. Chapter 8: Industrial Threat Intelligence

11. Chapter 9: Visualizing, Correlating, and Alerting

12. Section 3:Industrial Cybersecurity – Threat Hunting

13. Chapter 10: Threat Hunting

14. Chapter 11: Threat Hunt Scenario 1 – Malware Beaconing

15. Chapter 12: Threat Hunt Scenario 2 – Finding Malware and Unwanted Applications

16. Chapter 13: Threat Hunt Scenario 3 – Suspicious External Connections

17. Section 4:Industrial Cybersecurity – Security Assessments and Intel

18. Chapter 14: Different Types of Cybersecurity Assessments

19. Chapter 15: Industrial Control System Risk Assessments

20. Chapter 16: Red Team/Blue Team Exercises

21. Chapter 17: Penetration Testing ICS Environments

22. Section 5:Industrial Cybersecurity – Incident Response for the ICS Environment

23. Chapter 18: Incident Response for the ICS Environment

24. Chapter 19: Lab Setup

25. Other Books You May Enjoy

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...