사고 대응 및 재해 복구

Security incidents are an unfortunate reality. An Incident Response (IR) plan helps your organization detect, react, and recover effectively when a breach or attack occurs.

Without a clear plan, security incidents can lead to chaos, significantly increasing damage, data loss, and recovery time. Being prepared is key to minimizing impact.

The National Institute of Standards and Technology (NIST) outlines a widely adopted IR lifecycle. It's a structured approach to manage incidents from start to finish:

• Preparation: Getting ready
• Detection & Analysis: Spotting the threat
• Containment: Limiting damage
• Eradication: Removing the cause
• Recovery: Restoring operations
• Post-Incident Activity: Learning and improving

This crucial first phase is all about building your defenses and ensuring readiness before an attack happens.

• Team Formation: Assign clear roles (e.g., incident responders, communication leads).
• Tooling: Set up logging, monitoring, SIEM (Security Information and Event Management) systems.
• Policies: Define clear procedures, runbooks, and communication channels.
• Training: Regularly train your team through simulations and tabletop exercises.

This is where you identify that something is wrong and begin to understand what it is. Rapid detection is critical.

• Detection: Use alerts from SIEM systems, intrusion detection systems (IDS), or user reports.
• Analysis: Investigate the scope, type, and severity of the incident. Look for Indicators of Compromise (IoCs) like unusual network traffic, unauthorized logins, or modified files.

The immediate goal of containment is to limit the damage and prevent the attack from spreading further within your systems or network.

• Short-term: Isolate affected systems, block malicious IP addresses, or disable compromised user accounts.
• Long-term: Develop temporary workarounds to restore essential services while a permanent fix is being prepared.

Once the incident is contained, the next step is to completely remove the threat and its root cause from your environment.

• Identify and fix the vulnerability that led to the breach (e.g., patch software, update configurations, remove malware).
• Ensure all backdoors, malicious accounts, or persistent access mechanisms left by attackers are thoroughly removed.

After eradicating the threat, you restore affected systems and data to a secure, operational state. This means getting back to business as usual.

• Restore systems and data from clean, verified backups.
• Implement stronger security controls or new configurations to prevent recurrence.
• Continuously monitor systems for any signs of re-infection or new attacks.

This crucial final step helps you learn from the incident and improve your future incident response capabilities. It's about continuous improvement.

• Conduct a post-mortem analysis: What happened? How was it handled? What could be done better next time?
• Update policies, tools, and training based on lessons learned.
• Communicate findings and improvements to relevant stakeholders.

While IR handles specific security incidents, Disaster Recovery (DR) deals with major disruptions like natural disasters, large-scale power outages, or catastrophic data center failures. DR ensures overall business continuity.

Key DR concepts include:

• Recovery Time Objective (RTO): The maximum acceptable downtime for a system or service.
• Recovery Point Objective (RPO): The maximum acceptable data loss (e.g., how old can your data be after recovery).

Incident Response and Disaster Recovery are related but distinct disciplines. Test your understanding of their differences and common practices.

In this lesson, you've learned about the critical role of Incident Response and Disaster Recovery in maintaining robust backend security and business continuity.

• Incident Response (IR) is a structured approach to manage security breaches, following phases like preparation, detection, containment, eradication, recovery, and post-incident activity.
• Disaster Recovery (DR) focuses on restoring operations after major disruptions, using concepts like RTO and RPO to guide recovery efforts.

Together, IR and DR are vital for building resilience against various threats, from cyberattacks to natural disasters.