Back to Course

Incident Response

0% Complete
0/0 Steps
  1. Incident Response
    Incident Reporting
  2. Incident Response Use Cases
    Lab Setup
  3. Role Playing - Shift Manager
  4. Demonstrating: Investigating and Escalating
  5. Report from Malware Analyst
  6. Exercise 1.1: Exploring Suspicious Executable Detected using SIEM
  7. Exercise 1.2: Investigating Multiple Failed Logins using SIEM
  8. Exercise 3: Mitigating Risk
  9. Exercise 4.1: Asking the Right Questions
  10. Scenario 4.1: Asking the Right Questions
  11. Scenario 4.2: Suspicious or Malicious?
  12. Exercise 4.2: Reviewing the Shift Log
  13. Exercise 4.3: Investigating an Unauthorized Login Attempt
  14. Exercise 4.4: Investigating Firewall Traffic
  15. Exercise 4.5: Reviewing the Security Operations Mailbox
  16. Exercise 5.1: Reviewing New Intelligence
  17. Exercise 5.2: Assessing Threat Severity
  18. Exercise 6: Recommending Remediation
  19. Exercise 7: Conducting a Post-Incident Review
  20. Exercise 8: Communicating with Operations and Senior Management
  21. Business Continuity
    Business Continuity Plan Development
    8 Topics
  22. BCP Invocation Process
    2 Topics
  23. Emergency Procedures
    7 Topics
  24. Crisis Management Team
    10 Topics
  25. BCP Seating Plan
  26. Overview
  27. Disaster Recovery
    Scope of Critical Services
  28. Network Services
  29. Application Hosting Service
  30. File Hosting Services
  31. Call Centre and Voice Recording Services
  32. Regulatory Links
  33. Thin Client Environment
  34. Voice System (Non-Service Desk)
  35. Printing Services
  36. Recovery Time Objective (RTO) & Recovery Point Objective
  37. Single Point of Failure
  38. Redundancy Requirements
  39. Alternate Locations
  40. Contact Protocol
    4 Topics
Lesson 30 of 40
In Progress

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.