Back to Course

Incident Response

  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 33 of 40
In Progress

Thin Client Environment

1.1                    Server Architecture

1.2                    Scenario 1 >>>>>> Server down

Description:  This could be due to failure in the Citrix farm Data Base, or H/W failure.

Impact: Medium. It will be impact all Thin Client users, but it will cause minor performance degradation of application published on Citrix. 

Probability: Low, as we have redundancy in DC & DR. Please refer to Fig.1 in 9.1

BCP: There are 70 virtual Citrix farm servers in DC, and another 70 in DR. These servers are on two high end redundant physical servers and 5 smaller servers in DC, one high end and 7 smaller physical servers in DR.

If we face DB failure, the last server snapshot will be restored.

If we face H/W failure, we will depend on the redundant servers, and restore the faulty server as per the maintenance contract and the SLA with HP.

RTO: 1 Hours to restore the DB backup.

          6 Hour to replace the faulty H/W part