Downloaded 1,469 times
Uploaded byShah Sheikh
Building a Cyber Security Operations Center for SCADA/ICS Environments
The document outlines the essential steps for building a SCADA Cyber Security Operations Center (SOC), emphasizing the integration of people, processes, and technology to enhance cybersecurity posture and incident response. Key objectives include managing cyber threats, monitoring incidents, ensuring compliance with regulations, and developing effective communication and reporting structures. The SOC framework is designed to proactively monitor security infrastructures, automate incident response, and incorporate risk management aligned with business needs.
More Related Content
Similar to Building a Cyber Security Operations Center for SCADA/ICS Environments
Building a Cyber Security Operations Center for SCADA/ICS Environments
- 1. Building a SCADACyber Security Operations Center - PCN www.dts-solution.com Shah H Sheikh – Sr. Security Solutions Consultant MEng CISSP CISA CISM CRISC CCSK [email protected]
- 2. Agenda – Buildinga Security Operations Center • Information Security in Depth – put into practice • Understand overall security architecture • Identify ingress points of attack vectors • Physical and Logical Security • Build a SOC around the above … and more importantly build it around; People, Process and Technology Security Operations Center
- 3. Cyber Security -Defense In Depth
- 4. • Cost Savings –Reduced down time and maintenance costs – Improved productivity – Enhanced business continuity • Simplified Regulatory and Standards Compliance – FERC / NERC CIP – ANSI/ISA-99 – IEC 62443 – NIST 800-82 • Enhanced Security and Safety – Improved safety for the plant, employees and community – Improved defense against malicious attacks Why is Cyber Security important?
- 5. Critical Infrastructure Operations– The Emerging Threat
- 6. ICS Security -Defense-in-Depth
- 7. External Network Control LAN PlantNetwork Office LAN Internet Infected Laptops Infected Remote Support Mis-Configured Firewalls Unauthorized Connections Modems 3rd Party Issues USB Drives Pathways into the Plant Floor SIEM NMS Backup / Recovery
- 8. Corporate IT AutomationSystems IT Not life threatening Safety first Availability important Non-interruption is critical Transactional orientation Real-time focus IBM, SAP, Oracle, ….. ABB, Emerson, GE, Honeywell, Siemens... People ~= Devices Few people; Many, many devices PCs and Servers Sensors, Controllers, Servers Web services model is dominant Polled automation control model MS Windows is dominant OS Vendor-embedded operating systems Many commercial software products installed on each PC Purpose-specific devices and application Protocol is primarily HTTP/HTTPS over TCP/IP -- widely known Many industrial protocols, some over TCP/IP – vendor and sector- specific Office environment, plus mobile Harsh operating plant environments Cross-industry IT jargon Industry sector-specific jargon Cross-industry regulations (mostly) Industry-specific regulations Automation Systems Security Really Unique?
- 10.
- 11.
- 12. The current SOClandscape…
- 13. Outsourced or In-house?!? … VS …
- 14. Why build aSOC?
- 15. Key Objectives forSOC … (1) • Manages and Coordinates the response to Cyber Threats and Incidents • Monitors the Cyber Security posture and reports deficiencies • Coordinates with regulatory bodies • Performs Threat and Vulnerability Analysis • Performs Analysis of Cyber Security Events • Maintains an Internal Database of Cyber Security Incidents • Provide Alerts and Notifications to General and Specific Threats • Provide regular reporting to Management and Cyber Incident Responders
- 16. Key Objectives forSOC … (2) • Reduce the response time of security incident from initial findings, to reporting to containment • Recovery Time Objective (RTO) in case of security incident materializing • Proactive Security Monitoring based on predefined security metrics / KPI • Raise Awareness of Information Security across community of leaders and sub-ordinates • Ability to correlate system, application, network, server, security logs in a consistent way
- 17. Key Objectives forSOC … (3) • Ability to automate the requirement to meet compliance – vulnerability assessment and risk management • Ensure change control function is integrated into the SOC process • Identification for all security attack vectors and classification of incidents • Define disaster recovery plans for ICE (in-case of emergency). • Build a comprehensive reporting dashboard that is aligned to security metrics • Build a local in-house SIRT (security incident response team) that collaborates with national CERT
- 18. Key Objectives forSOC … (4) • To build SOC processes that are aligned to existing ISO27001 security policies • Build a physical and virtual team of SOC personnel for 24 x 7 monitoring • Build forensics capabilities to be able to reconstruct series of events during an incident • Proactive monitoring of network and security infrastructure devices
- 19. Components of aSOC • To build the SOC with simple acceptance and execution model • Maximize the use of technology. • To build security intelligence and visibility that was previously unknown; build effective coordination and response unit and to introduce automation of security process. • Develop SOC processes that are inline to industry best practices and accepted standards – ISO27001:2013, PCI-DSS3.0 SECURITY INCIDENT MANAGEMENT · PRE AND POST INCIDENT ANALYSIS · FORENSICS ANALYSIS · ROOT CAUSE ANALYSIS · INCIDENT HANDLING · aeCERT INTEGRATION · REPORTING · EXECUTIVE SUMMARY · AUDIT AND ASSESSMENT · SECURITY METRIC REPORTING · KPI COMPLIANCE · SLA REPORTING · REAL-TIME MONITORING · DATA AGGREGATION · DATA CORRELATION · AGGREGATE LOGS · CORDINATE RESPONSE · AUTOMATED REMEDIATION
- 20. Key Success Factorsin a SOC The Goal – Keep Things Simple
- 21. SOC – CoreComponents Core Components for a SOC 2.0 • OSS – Operational Support System • SIEM – Security Information and Event Management • Proactive Monitoring - Network and Security and Server Infrastructure • Alert and Notification – Security Incident Reporting • Events Correlation and Heuristics / Behavioural / Anomaly
- 22. SOC – CoreComponents Core Components for a SOC 2.0 • Information and Network Security $$ Automation $$ • To natively build-in compliance and audit functions • To manage change control process through integrated ITILv3 CM and SD • Configuration Management of Infrastructure Components
- 23. SOC – CoreComponents Core Components for a SOC 2.0 • Alignment of Risk Management with Business Needs • Qualified Risk Ranking • Risks are ranked based on business impact (BIA) • Risk framework is built into the SIEM solution; • incident = risk severity = appropriate remediation and isolation action • SOC is integrated with Vulnerability and Patch Management
- 24. SOC – CoreComponents Core Components for a SOC 2.0 • IRH – Incident Response Handling • How effective the SOC is measured by how incidents are managed, handled, administered, remediated and isolated. • Continuous cyclic feedback mechanism drives IRH • Critical functions include Network Forensics and Surveillance Tech.. • Reconstruct the incident …. Evidence gathering … Effective Investigation • Escalation Management – know who to communicate during an incident
- 25. SOC – CoreComponents Proposed Architecture for the SOC Perimeter and Boundary Points Network Nodes Internet DMZ / Published Services IPS WWW SSL VPN Applications Active DirectoryDB Middleware SMTP Internal Resources MAINFRAME Servers WAF FW (HTTP, SNMP, SMTP, SYSLOG, API, XML, CUSTOM FILE, LOGFILE DATA ACQUISITION LAYER – SECURITY INFORMATION AND EVENT MANAGEMENT (SIEM) EVENT CORRELATION LAYER · Event Correlation Engine · Analysis and Filtering · Event Management · Integration with NMS Systems · Trouble Ticket Integration · Flow Analysis SECURITY VULNERABILITY · Common Vulnerability Exploits CVE · Risk Ranking · Configuration Audit · Security Metric Dashboard DATA COLLABORATION · Policy Management · Asset Repository · Problem Incident Management · Security Incident Reporting · Change Control · Security Automation Security Management, Systems Management, Network Management, Reporting, KPI, SLA, Benchmark, Compliance Management REPORTING AND MANAGEMENT LAYER
- 26. SOC – CoreComponents Integration of Core SOC Components
- 27. SOC Technologies … Sonow the technologies … SIEM Solutions • Event Collector – Syslog, Log Files, Application Log Export • Flow Collection – NetFlow, J-Flow, S-Flow, IPIX • Asset Database • Event and Flow Correlation • Centralized Management Console for Security Dashboard and Reporting • Integration with service desk for automated ticket creation Compliance Management and Policy Conformance • Configuration Audit • ISO27001 / PCI-DSS3.0 Policy Compliance • Risk Management • Baseline Configuration Violation Monitoring • Network Topology Mapping and Visualization • Vulnerability Assessment
- 28. SOC Technologies … Sonow the technology … Network and Security Monitoring • Network Performance Monitor - SNMP • Network Monitoring • Link Utilization • Availability Monitoring • SLA reporting • Integration with service desk for automated ticket creation Security Intelligence • Network Forensics • Situation Awareness • Artifacts and Packet Reconstruction • Monitor all Internet Activity • Record metadata for recursive analysis during incident response • Integration with Incident Response Handling (IRH)
- 29. SOC (before) …..< The Silos >… Technology Integration … the old practice SIEM Vulnerability Assessment Network Monitoring
- 30. SOC (after) ….Automation Technology Integration … the new … WORKFLOW SIEM 2.0Compliance and Monitoring NMS
- 31. SOC – Processes…. Look familiar… Creating the SOC Processes … now that we have discussed technology, lets discuss processes … DATA SECURITY AND MONITORING • Data Asset Classification • Data Collection • Data Normalization • Data at Rest and In Motion • Data Protection • Data Distribution
- 32. SOC – Processes Creatingthe SOC Processes … now that we have discussed technology, lets discuss processes … EVENT MANAGEMENT • Event Correlation • Identification • Triage • Roles • Containment • Notification • Ticketing • Recovery • Forensics and Situational Awareness
- 33. SOC – Processes Creatingthe SOC Processes … now that we have discussed technology, lets discuss processes … INCIDENT RESPONSE PRACTICE • Security Incident Reporting Structure • Security Incident Monitoring • Security Incident Escalation Procedure • Forensics and Root Cause Analysis • Return to Normal Operations • Post-Incident Planning and Monitoring • Communication Guidelines • SIRT Integration
- 34. SOC – Processes Creatingthe SOC Processes … now that we have discussed technology, lets discuss processes … SOC OPERATING GUIDELINES • SOC Workflow • Personnel Shift Description • Shift Reporting • Shift Change • Information Acquisition • SOC Monitoring Suite • SOC Reporting Structure • Organizational Chart
- 35. SOC – Processes Creatingthe SOC Processes … now that we have discussed technology, lets discuss processes … ESCALATION MANAGEMENT • Escalation Procedure • Pre-Escalation Tasks • IT Security • Network Operation Center • Security Engineering • SIRT Integration • Law Enforcement • 3rd Party Service Providers and Vendors
- 36. SOC – Processes Creatingthe SOC Processes … now that we have discussed technology, lets discuss processes … DATA RECOVERY PROCEDURES • Disaster Recovery and BCP Procedure • Recovery Time Objective • Recovery Point Objective • Resiliency and High Availability • Facilities Outage Procedure
- 37. SOC – Processes SECURITYINCIDENT PROCEDURES • Email Phishing - Email Security Incident • Virus and Worm Infection • Anti-Virus Management Incident • NetFlow Abnormal Behavior Incident • Network Behaviour Analysis Incident • Distributed Denial of Service Incident • Host Compromise - Web Application Security Incident • Network Compromise • Internet Misuse • Human Resource - Hiring and Termination • Domain Hijack or DNS Cache Poisoning • Suspicious User Activity • Unauthorized User Access (Employee)
- 38. SOC – Processes VULNERABILITYAND PATCH MANAGEMENT • Vulnerability Research • Patch Management - Microsoft SCOM • Identification • Dissemination • Compliance Monitoring • Network Configuration Baseline • Anti-Virus Signature Management • Microsoft Updates Creating the SOC Processes … now that we have discussed technology, lets discuss processes …
- 39. SOC – Processes TOOLSOPERATING MANUAL FOR SOC PERSONNEL • Operating Procedure for SIEM Solutions – Event Management and Flow Collector/Processor • Firewall Security Logs • IDS/IPS Security Logs • DMZ Jump Server / SSL VPN logs • Endpoint Security logs (AV, DLP, HIPS) • User Activity / Login Logs • Operating Procedure for Policy and Configuration Compliance • Operating Procedure for Network Monitoring Systems • Operating Procedure for Vulnerability Assessment Creating the SOC Processes … now that we have discussed technology, lets discuss processes …
- 40. SOC – Processes SECURITYALARMS AND ALERT CLASSIFICATION • Critical Alarms and Alerts with Action Definition Non-Critical and Information Alarms Alarm reporting and SLA to resolve the alarms Creating the SOC Processes … now that we have discussed technology, lets discuss processes …
- 41. SOC – Processes SECURITYMETRIC AND DASHBOARD – EXECUTIVE SUMMARY • Definition of Security Metrics based on Center of Internet Security standards • Security KPI reporting definition • Security Balanced Scorecard and Executive Reporting Creating the SOC Processes … now that we have discussed technology, lets discuss processes …
- 42. • Environments • Location •Device Types • System Types • Security Zones • Demarcation Points • Ingress Perimeters • Data Center • Extranet • WAN ….Know your infrastructure…. You can only monitor what you know
- 43.
- 44. Industrial Control SystemsSecurity
- 45. SCADA Network… Whatis the problem?
- 46. SCADA Network… Isolationand Zoning
- 47.
- 48. Defense in DepthStrategy
- 49. • Knowledge onhow service flow across your infrastructure…. BUILD A SECURITY SERVICES CATALOG …. Service Flows ……
- 50. • Understanding theservice flows will allow you to VISUALIZE… ….. HEAT MAP ….. …. Service Flows ……
- 51. Build an AssetDatabase and Integrated into SIEM; Following asset details can be adjusted with Asset Manager: • Name • Description • Weight • Operating System • Business Owner • Business Owner Contact Information • Technical Owner • Technical Owner Contact Information • Location Build an Asset Repository
- 52. SCADA / ICS– ASSET REPOSITORY
- 53. Now that wehave the processes, technology and people what next….. • Build contextual threat cases per environment; – Extranet – Internet – Intranet – Data Center – Active Directory – Malware / Virus Infection and Propagation – NetFlow Analysis – Remote Sites / WAN – Remote Access – IPSEC VPN / SSL VPN – Wireless – etc….. Develop Threat Cases
- 54. Sample: Firewall GAPAnalysis Report
- 55. Sample: Firewall GAPAnalysis Report
- 56. Sample: Firewall GAPAnalysis Report
- 57. ADVANCED THREAT CASES- ENVIRONMENT • To define threat cases per environment … not by system…. (silo) • CONTEXTUAL • SERVICE ORIENTATED • USER CENTRIC ID Threat Case Development OS.WIN Microsoft Windows Servers - Threat Case Development Documentation Microsoft Active Directory - Threat Case Development Documentation MSIIS MSSQL MSEXC Microsoft Application - Threat Case Development Documentation • IIS • MSSQL • Exchange IBMAIX LINUX SOLARIS UNIX/LINUX/SOLARIS/AIX – Threat Case Development Documentation PRIVACC Advanced Threat Cases for Privileged User and Special Account Activity and Monitoring N/A Baseline Security Settings on UNIX/LINUX/SOLARIS/AIX server BUSINT Business Internet EXTRNT Extranet S2SVPN Site to Site VPN
- 58. ADVANCED THREAT CASES- ENVIRONMENT • To define threat cases per environment … …. Eventually …. Should …. Include …. All …. Environment ….. ID Threat Case Development INTOFF International Offices – Global MPLS SSLVPN Juniper SSL VPN NATIONAL IPVPN –National MPLS IPVPN WIRLESS Wireless Infrastructure VOIPUC Voice over IP VSAT VSAT – Satellite DIGPKI PKI and X.509 Digital Certificates (systems threat case) AAA AAA (systems threat case) HIPS HIPS (system threat case and ePO integration) EXECACC Executive Account Monitoring SAP SAP Router and SAP Privilege Activity Monitoring COMPLIANCE Compliance and Best Practices Configuration NAC Network Admission Control –
- 59. ADVANCED THREAT CASES- ENVIRONMENT • To define threat cases per environment … …. Eventually …. Should …. Include …. All …. Environment ….. ID Threat Case Development IPS-AV IPS and AV Management Console EMAIL Email Security – Business Internet Gateway DAM Database Activity Monitoring (DAM) SFT Secure File Transfer • IMPORTANT – understand the environment and understand the threats related to those environment…..
- 60. Develop Threat Cases– RHEL
- 61. Develop Threat Cases– RHEL
- 62. Important Note: "OS.WIN.010.Offense: MultipleLogon for Single User from Different Locations" offense is disabled pending application/system accounts names clarifications to be excluded from the rule's logic. Develop Threat Cases – Windows Servers
- 63. *NIX AUTHENTICATION …FOLLOW THE PROCESS
- 64.
- 65.
- 66.
- 67. Offense Management NamingConvention
- 68.
- 69.
- 70. SOC-Wiki - Goals •Centralized Knowledge Repository for SOC • Collaborate and Share Information with other Team Members • Easy of use and Searchable • Integrations with other Toolsets
- 71. SOC Wiki –SIEM Integration • Current Issues with SIEM Processes, Documentations, Offence Handling, Knowledge Sharing • SIEM Integrations into SOC-Wiki • SIEM Threat Cases
- 72. SOC Wiki –SIEM Threat Cases • Listed above is how Threat Cases are displayed in SOC-Wiki • Threat Case Name, Severity, Status • Information - Centralized, Detailed and Searchable • Information updated by SIEM and SOC Teams
- 73. SOC Wiki –SIEM Threat Cases • Example:
- 74. Security Assurance Level •Security Assurance Levels (SALs) in Critical Infrastructure • Functional Requirements • Security Levels • Based on 7 x Functional Requirements • a) Access control (AC) • b) Use control (UC) • c) Data integrity (DI) • d) Data confidentiality (DC) • e) Restrict data flow (RDF) • f) Timely response to an event (TRE) • g) Resource availability (RA)
- 75. Security Assurance Level •Security Assurance Levels (SALs) in Critical Infrastructure • Functional Requirements • Security Levels • Based on 4 x Security Levels
- 76.
- 77. Security Assurance Level AchievedSL vs. Target SL 0 1 2 3 4 Access control (AC) Use control (UC) Data integrity (DI) Data confidentiality (DC) Restrict data flow (RDF) Timely response to an event (TRE) Resource availability (RA) Achieved Security Level Target Security Level
- 78. Shah H Sheikh– Sr. Security Solutions Consultant MEng CISSP CISA CISM CRISC CCSK [email protected]