IC37 IEC62443 Flashcards
(97 cards)
1
Q
Scope
A
Determine the parameters of what is included in the assessment how it is performed.
2
Q
Scope include
A
- IDENTIFY Requirement
- Specify Devices
- Select Collection Method
- Document
3
Q
Key Components of Scope
A
- System Description
- Asset Inventory
- Criticality Assessment.
- System Architecture Design.
- Document Data flow
- Network Diagram .
4
Q
Cybersecurity Vulnerability Assessment
A
defines, identify, and classifies the security vulnerabilities in industrial control system and its related network infra
5
Q
Cybersecurity Vulnerability Assessment is
A
-Critical step in evaluating cyber risk
- Evaluate the IACS design, implementation, configuration, operation and management.
- Determines the adequacy of security measures and identify security deficiencies
6
Q
Benefits of Cybersecurity risk assessment
A
- determine what plants/processes need to address and what order.
- Definition of threats, vulnerabilities, and consequences so they can be mitigated. - this is very time consuming.
- Design and apply countermeasures to reduce risk.
- Prioritize mitigation activities and resources.
- Evaluate countermeasures of effectiveness versus cost and complexity.
7
Q
Cyber Risk Assessment Process
A
- Identify System under consideration.
- Conduct high-level cyber risk assessment.
- Partition the SUC into zones and conduits.
- perform detailed cybersecurity risk assessment for each zone and conduit.
- Document security requirement assumption and constrains.
8
Q
for each zone and conduit you will need to run
A
IEC 62443-3-3
Detailed risk assessment process, this is section 5 of the detailed risk assessment. just an FYI, this include:
- Identify Threats
- Identify Vulnerabilities
- Determine consequences and Impact.
- Determine Likelihood
- Calculate unmitigated Cyber risk
- Determine Security Level target.
- Consider Existing Countermeasures.
- Reevaluate likelihood and impact.
- Calculate residual risk
- All risk mitigated or below tolerable risk
- Document the results.
9
Q
You need Documentation to prove what you did `
A
Documents in general should be
- Revised
- Amended
- Reviewed,
- Approved.
10
Q
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@22
A
Review for the Design Chapter
11
Q
remember the 4 T of Managing risk
A
- Tolerate - risk organizations are willing to take.
- Transfer - insurance.
- Terminate - block the risk
- Treat. - reduce the lielihood
12
Q
Five D’s of treating Risk.
A
- Deter
- Detect
- Delay
- Deny
- Defeat.
13
Q
Remember firewalls
A
block unauthorized access of firewall. Network and Host firewalls.
14
Q
IDS are either
A
NIDS or HID -
- pre-defined rules signatures
- Anomaly - behavior
15
Q
Remote access
A
Huge Operational Benefits
High Risk.
with ease huge operation benefits and high risk….
16
Q
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Monitoring and Management
A
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
identify component of asset inventory
identify system harden
17
Q
Asset Inventory
A
Maintain a list of database of all IACS and SCADA hardware - physical and virtual.
18
Q
Asset inventory done through
A
- Documentation and site survey. this could take long time if the company is around for a long time.
- tools also can be used.-
19
Q
if you use automations tools ensure that
A
- they don’t impact system availability or integrity
- introduced security Vulnerability.
20
Q
Hardware include all
A
servers, computers, workstations, smart phones., PLC, DCS, VFD, RTU, etc, serial routable devices.
you will need to have record of
- Asset ID
Device Type
Function
Network interfaces.
Network Addresses
Manufacture
Model
Serial Number
Operation system and version
Firmware Version,
Physical location
Notes.
Device system name
VM all details needs to be documents - do not forget about this.
- all software- application, databases, firmware, operation system, patch process.
anything with ethernet and serial communication. routable serial. modbus, serial, profibus
21
Q
Asset inventory for Software is also important. this should include
A
operation systems.
applications.
database
firmware.
22
Q
Asset inventory tools are are either:
NETWORK MANAGEMNET TOOLS
SOFTWARE ASSET MANAGEMENT SAM TOOLS
CONFIGURATION MANAGEMENT TOOLS
A
Network Management tools.
- SolarWinds, OPenNMS, Siemens SNM, MOXa
software asset management SAM tools
- IT Asset tool, Microsoft system center.
Configuration Management Tools.
- Rockwell Asset center
PAS integrity
MDT autosave
23
Q
System Hardening
A
the process of security a system by reducing its attack surface. this include
- Remove unnecessary software —
-Remote user accounts. —
-Enforce strong access control - multifactor authentication is important - Disable or remove services. this is important
-Install security patches. patches are also important.
24
Q
which device can be hardened
A
any configurable device can be hardened. such as operation ystem, database, applications. managed switches, routers, firewalls, modems., PLCm IED, VFD.
25
operation system hardening - where to go? OS HARDEINING Very IMPORTANT
- NIST SP 800-123
Microsoft Security Guides
CIS security Benchmarks.
Disa STIGS,
Automation suppliers
REMEMNER 800-123 IS OS HARDENING ---
26
Basic Step to secure operation system. OS
- Patches and update the OS
- Remove or disable services, application and network protocols.
configure access controls.
configure OS user authentication.
install and configuration additional security control
test the security of the OS, '
list of unnecessary softwares:
- Remove games.
- unused devicers.
- messaging services.
unused internet
software compliers
unused protocols.
27
Device Hardening Guidance DEVICE HARDENING 800-82
NIST SP 800-82
Always look for vendors.
28
HARDENING DEVICES INCLUDE
PLCs
MOTOROS AND DRIVES
I?O
HMI
Sensors
IEDs
Flow Computers.
29
Hardening of devices are
-disable program changes.
-install vendor firmware update
-compare file hash
-shutdown unused network interface.
-default password
-enable logging
-disable unused protocols.
-restrict remote access.
- protectet with ICS
-disable services not used.
- restict remote access.
30
Network Hardening NSA CISCO NIST
SANS
SECURITY CONFIGURATION CHECKLISTS
three functional planes of a network
- Management - IOS - SSH SNMP
- Control - EIGRP, BGP, OSPF
- Data actual data/
31
Network Hardening best practices
install firmware updates.
compare hash files
shutdown unused physical interfaces.
enable configuration access control
change and encrypt password
use snmp3
restict remote management
use secure protocols.
shutdown unused ervices.
enable logging.
32
ACCESS CONTROL
Policies, Procedures and technical controls that govern the use of system resources.
Access control ensure system only accessible to authorized users, programs, process and other systems.
ACCESS CONTROL ENFORCE the following:
separation of duties
least privilege
system notification.
previous login
concurrent session
session locking
unsuccessful login attempts
least privilege.
session termination
33
Access control involve
establishing.
activating
modifying
reviewing
disabling
removing accounts.
34
Access control best practices
- Develop access control policy to establish appropriate logical and physical rules
- segregate data with high sensitivity.
employ multiple authentication
- make use of centralized identify
- use organization units.
35
use always multifactor authentications
something you know
something you have
something you are.
36
remote access
technology made it so easy.
37
VPN appliance is a network device enhanced with security features known as secure socket layer SSL.
A network using public telecommunication infrastructure such as internet and provide remote networks or computes with secure access to another network.
38
VPN security employs
- IPSec Internet protocol security
SSL\TLS transport layer security
DTLS datagram transport layer
MPPE microsoft point to point encyption
SSTP secure socket tunneling protocol
MPVPN
SSH
39
firewall evelotion into all inclusive security products. NGFW-
firewall
VPN
content filtering
load balancing
vpn
antispam
data
40
Type of VPNs
Site to site to vpn
VPN gateway.
41
VPN best practise
- require the use of corporate owned laptops
-provide remote access users with secure bootable image
-no vpn split should be allowed
-change tcp port for something
-monitor and log all remote access sessions.
- encrypt all communications.
- configure modems for maximum security
- restirct remote connections to special machines.
42
Secure Remote Access Examples
Read only access
One way Reporting
Limited data exchange
Employee and vendor remote maintenance and troubleshooting
Full remote operations.
43
Antimalware Management
malware related incident are number one cause of cyber related production losses and upsets in process control systems.
Viruses can impact control systems. user mix deployment.
All major plc and DCS vendor support firewall.
44
Always recommend using mix solutions
Antivirus scanning at the control system firewall
Automatic updating for non critical system or systems with approved update schemes.
Manual scheduled updates for more difficult system.
45
Whitelisting
BENEFITS
Smaller and more efficient
Does not require sig-nature update
can ensure critical files and approved.
zero day protection.
ISSUES:
Agnostic to malware
can block software updates
Blacklisting
BENEFITS
Can define malicious software behavior
ISSUED:
Number of known bad signatures are large and growing.
Require frequent update.
False positive can block critical files.
no protection against zero day attack
46
Whitelisting mean
Allow known Good
47
blacklisting
blocking known bad
48
Anti-Virus Management
49
Application Control
Identify entitlement, privilege, or access based approval
Protect memory so application in memory cannot be changed.
50
Change Control
Extend application control to include file integrity monitoring for non executable.
51
ALWAYS KEEP Systems up to date because it is critical to protection
52
Patching
patch should be analyized for each device.
Installed and verified on test system
backup should be done before patch is installed.
Document all changes.
53
PATCH MANAGEMENT LIFECYCLE - it is continuous process
- Information Gathering
- Monitoring & Evaluation
- Patch Testing
- Patch Deployment
- Verification and Reporting
54
Patch Management Best Practice
- Establish and Maintain inventory for all updatable electronic devices.
- Determine regular schedule and what is available
- Test deployment of patches in manner that reflect production environment
- Schedule qualified patches for installation at next available opportunity
- Update records at planned interval
- periodically identify security vulnerabilities.
- Implement paches or equivalent counter measures.
55
PLC Backup and Configuration Management - (BACKUP AN Recovery)
Restoration Time - how much time required- is redundancy required.
Backup Interval - how often the backup should run
Backup Management - how many duplicates required in case of damage.
Media Storage - keep media and license keys in safe area,
Responsible party - what department is responsible
Review and Update plan - review and update BCP when system change.
56
System backup best practices
check for redundancy real time? near realtrimen?
data center? hot warm, cold?
point- in time snapshot automated or manual?
maintain version control.
automate the backup
protect backups.
57
System backup types?
Redundant systems.
= physical or virtual
= Pcs
= Hardware/software
= Network
Point in time snapshots.
= pc code, apps, image, partitions, files, and config.
= PLc code, apps, and config
= Data base
= network devices. config
58
`Backup and Recovery best practices
Establish backup and restore policies.
Document procedures and ensure they are repeatable.
All devices with configuration should be backed up
Backup are performed automatiacally on staggered schedule
Onsite and offisite storage of backup
Periodic testing of backup
periodic trsting of restore.
59
Change Management
the objective of change management is to minimalize RISK to safety and downtime by ensuring that request for change are
recorded,
evaluated,
autherized.
prioritized,
planned,,
tested,
implemented,
documented and
reviewed.
in controlled and consistent manner.
Remember that Vulnrability and Patch Management must also follow the same change management process.
ISA 62443-2-1 secrion 4.3 and 4.3.2
60
Typial IACS changed that require management of change
- Changes to equipment and system on ICS architecture diagram
Change of IT equipment and other services.
Any changes.
61
Change requests conftain inforamtion required in assessing the goals and cot wnd risk associated with change
Descirption of the change
benefit of applying the change
cost and risk of not applying the change
cost associated with the change
risk assessment of the change
priority of the change.
62
change in industrial facilities and processes is
Critical to safety.
Remember that change has to be done by MULTI-DISCIPLIONARY TEAM....
63
Change Management priority examples
- IMMEDIATE - Life is at risk, significant los of revenue - Imediate action is required.
- HIGH - Severely affecting safety systems or impacting the ability of production.
- MEDIUM - no server impact but things will need to be fixed prior the next schedule.
- LOW Changes can be taken care of in the next schedule.
64
Information and Document Management Best Practices
- Lifecycle document management process should be eveloped.
information classification is required.
Control system information such as design information
65
physical security
protection of personnel, hardware, program, networks and data from physical circumstances and events.
66
Asset inventory tools are
Network Management Tools
Management Tools known as SAM
Configuration Management tools
67
Three function planes of data are
Management,
Control
Data
68
System Hardening
System hardening is the process of securing a system by reducing its attack serfuce.
69
Access Control
is the policies, procedures, technical controls that govern the use of system resources to ensure the system can be accessed by authorized user, program and othe sysyems.
70
Detection tools @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
71
What does security monitoring and detection entail???
detecting abnormal activity.
Network inrusion detection
Host intrusion detection
Monitoring logs
Periodic testing and auditing.
72
Detection techniques??
Signature against black list
Behavior against beh avior
Anomaly again knowing good. white list
73
diffferences
best solution for zero day exploit is BEHAVIOR
Best solution for known exploit is Signature
Best solution for insider threat? Anomaly.
74
Anomaly detection include
- DATA HOARDING
- GEO Graphic location
- time versus data
-service traffic.
- host data loss
75
User Observation for Abnormal System Behavior
anything that can trigger changes such as?
CPU usage
protocol blocked
patch changes
system shutdown
lockedout account
logs and clear logs.
76
Cababilities of host inrusion systems are ?
Log analysis
policy enforcment
event colleration
Alerting
rootkit detection
integrity checking
77
LIDS are
log based Intrusion detection system
LIDS
LIDS is normally part of the SIEM
78
All intrusion detection system needs the following
Testing / Auditing / Adjustment as part of CSMS
testing should be established by policy
audit by third party tester
adjust based on new threats.
IMPORTANT-------------
79
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@2
this chapter will be talking about
- incident response lifecycle.
- aspect of incident response planning
- incident management.
incident prevention
- four phases of forensic
three C of incident Analysis.
80
Incident response lifecycle include?
1- PLANNING
2- INCIDENT PREVENTION
3- DETECTION
4- CONTAINMENT
5- REMEDIATION
6- RECOVERY and RESTORATION
7- POST INCIDENT Analysis and forensic.
81
1 - PHASE ONE IS PLANNING
in this phase we assemble CYBER SECURITY INSIDENT RESPONSE TEAM CSIRT the team consist of engineers. managers.
in this phase we need to have clear written operation procedure. and response checklist.
82
2- INCIDENT PREVNTION techniques....
IACS asset management
system hardening
access control
remote access
malware prevention
system backups
change management
information & documentation
physical security
and you will need vendor interaction.
83
Incident Analysis 3C's
Calm - dont panic
Cool intense discussion
Collected. list and think critcally.
84
INCIDENT MANAGEMENT include
Detection
Response tools
Categorization
Containment
Remediation
Recovery and restoration.
important
85
3- INCIDENET DETECTION
how to detect the incident
Automated detection tools
Reporting
Detection by observing traffic, CPU, USAGE
86
4- INCIDENT CONTAINMENET
How to contain an incident.
isolate the system?
remove the effected device
remove?
protect?
this should be documented.
87
5- REMEDIATION
fix the source of the problem
close unauthorized path
remove malware.
etc.
in this phase you may want to work with the asset owner and data owner.
88
6- Recovery and Restoration
Establish contingency plans
patch and maintain all bakcup systems.
verify failover systems.
establish plan to run segmenet in isolation.
test backups.
establish and run acceptance test.
this also include defining procedure to provide for the tests and declare the IACS fully operational.
89
7- Once you are done there is another phase called.... POST INCICENT ANALYSIS and FORENSIC
the idea of this phase is to gain understanding of how it happen and how why.
90
forensic process is as follow: CEAR
Collection
Examination
Analysis
Reporting
91
1 - Collection phase
time is important
secure senstive date
preserver the scene
protect the evidence
92
2- Examination
Establish check list
identify the key people and personeen.
identify normal and abnormal operating.
identify requirement
identify remote access.
identify any protections.
conduct interview
operation personnel can give you alot of insight.
93
3- Analysis.
conduct packet analyzer, network analyzer, and packet sniffer.
check cabling and wiring as well!
know how identify any alarms. HMI alarm view alarms.
windows event logs can also be configured.
94
- Reporting
preserve forensic data
keep detailed notes and report and dont rely on memory
detected computers.
95
INCIDENT REPONSE PLANNING INCLUDES::::
overview goals and objective.
incident description
incident detection.
incident notification
incident analysis
response action.
communication
forensics.
96
Incident response plan include
incident analysis
incident descirption
fornsic.
97
Network Hardening best practices
install firmware updates.
compare hash files
shutdown unused physical interfaces.
enable configuration access control
change and encrypt password
use snmp3
restict remote management
use secure protocols.
shutdown unused ervices.
enable logging.
