As discussed in detail in the previous chapter, no security posture is complete without monitoring and logging. Without logging and monitoring, how would you know that your security holds? Keep in mind, though, that someone needs to be looking at these logs, alarms, and events for it to be effective. Refer to the previous chapter to see the various events that should be captured from your client computers.
- Preface
- Industrial Control Systems
- Insecure by Inheritance
- Anatomy of an ICS Attack Scenario
- Industrial Control System Risk Assessment
- The Purdue Model and a Converged Plantwide Ethernet
- The Defense-in-depth Model
- Physical ICS Security
- ICS Network Security
- Designing network architectures for security
- Network segmentation
- Resiliency and redundancy
- Architectural overview
- Firewalls
- Security monitoring and logging
- Network packet capturing
- Event logging
- Security information and event management
- Summary
- Designing network architectures for security
- ICS Computer Security
- ICS Application Security
- ICS Device Security
- The ICS Cybersecurity Program Development Process
- The NIST Guide to Industrial control systems security
- The ICS security program development process
- Security policies, standards, guidelines, and procedures
- Defining ICS-specific security policies, standards, and procedures
- Defining and inventorying the ICS assets
- Performing an initial risk assessment on discovered ICS assets
- Defining and prioritizing mitigation activities
- Defining and kicking off the security improvement cycle
- Summary
Monitoring and logging
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.