Incident Response
-
Incident ResponseIncident Reporting
-
Incident Response Use CasesLab Setup
-
Role Playing - Shift Manager
-
Demonstrating: Investigating and Escalating
-
Report from Malware Analyst
-
Exercise 1.1: Exploring Suspicious Executable Detected using SIEM
-
Exercise 1.2: Investigating Multiple Failed Logins using SIEM
-
Exercise 3: Mitigating Risk
-
Exercise 4.1: Asking the Right Questions
-
Scenario 4.1: Asking the Right Questions
-
Scenario 4.2: Suspicious or Malicious?
-
Exercise 4.2: Reviewing the Shift Log
-
Exercise 4.3: Investigating an Unauthorized Login Attempt
-
Exercise 4.4: Investigating Firewall Traffic
-
Exercise 4.5: Reviewing the Security Operations Mailbox
-
Exercise 5.1: Reviewing New Intelligence
-
Exercise 5.2: Assessing Threat Severity
-
Exercise 6: Recommending Remediation
-
Exercise 7: Conducting a Post-Incident Review
-
Exercise 8: Communicating with Operations and Senior Management
-
Business ContinuityBusiness Continuity Plan Development8 Topics
-
BCP Invocation Process2 Topics
-
Emergency Procedures7 Topics
-
Crisis Management Team10 Topics
-
BCP Seating Plan
-
Overview
-
Disaster RecoveryScope of Critical Services
-
Network Services
-
Application Hosting Service
-
File Hosting Services
-
Call Centre and Voice Recording Services
-
Regulatory Links
-
Thin Client Environment
-
Voice System (Non-Service Desk)
-
Printing Services
-
Recovery Time Objective (RTO) & Recovery Point Objective
-
Single Point of Failure
-
Redundancy Requirements
-
Alternate Locations
-
Contact Protocol4 Topics
Participants3
File Hosting Services
1.1 Storage Architecture
Fig. 1
1.2 Scenario 1 >>>>>> Core Storage Malfunction
Description: This is H/W failure of the EMC storage system carrying the Core Banking DB.
Impact: Severe. It will cause outage to All Core services.
Probability: Medium, as we have only one EMC storage system in DC and another one in DR.
BCP: There are only one EMC storage system in DC and another one in DR. as shown in Fig.1 in 5.1 so in case of H/W failure in the DC, we have to do Full services switch to DR.
RTO: 4 Hours for the full switch to DR.
1.3 Scenario 2 >>>>>> Virtualization storage HW malfunction
Description: This is H/W failure in the HP storage system carrying the VMware applications.
Impact: Medium. Minor performance degradation
Probability: Low, as we have 15 HP storage boxes in DC and another 12 in DR.
BCP: There are many HP storage boxes in DC and DR as shown in Fig.1 in 5.1, so any failure will cause just minor performance degradation till replacing the faulty part.
RTO: 2 Hours to restore the server backup
6 hours to replace the faulty HP H/W part as per SLA.