Megosztás a következőn keresztül:

Microsoft security incident management: Containment, eradication, and recovery

  • Cikk

Based on the analysis performed by the security response team, the service team develops an appropriate containment and recovery plan to minimize the effect of the security incident. The appropriate service teams then apply that plan in production with support from the security response team.

Containment

After detecting a security incident, it's important to contain the intrusion before the adversary can access more resources or cause more damage. The primary goal of our security incident response procedures is to limit impact to customers or their data, or to Microsoft systems, services, and applications.

Eradication

Eradication is the process of eliminating the root cause of the security incident with a high degree of confidence. The goal is two-fold:

  • to evict the adversary completely from the environment
  • to mitigate the vulnerability (if known) that enabled or could enable the adversary to reenter the environment.

Depending on the nature of the incident, the scope of the security incident, the depth of the penetration and possible repercussions, the security response team recommends that service teams adopt eradication techniques. Considering the potential business impact that may be caused by these eradication steps, these decisions are made by service teams and the security response team after a detailed analysis and approval from the Executive Incident Manager (if necessary).

Recovery

As the response team gains a reasonable level of confidence that the adversary has been evicted from the environment and all known vulnerable paths have been eliminated, the individual service teams initiate restoration steps to bring the service to a known and good configuration. These restoration steps are in consultation with the security response team. This activity includes identifying the last known good state of the service, restoring from backups to this state, inspecting vulnerable attack paths in the restored state, etc. The security response team, in consultation with the service teams, determine the best possible recovery plan for the environment.

A key aspect to the recovery is to have enhanced vigilance and controls in place to validate that the recovery plan has been successfully executed, and that no signs of breach exist in the environment.

Customer notification of security incident

If Microsoft determines that a security incident has occurred, we'll notify you with undue delay, and within contractual and compliance requirements we agree to. After identifying all affected tenants, the corresponding communications team works to identify any relevant regulations that might apply to affected tenants. The communications team uses the appropriate communication channel defined in applicable regulations to notify the appropriate tenant contact.

Incident response process.

Notification includes detailed information about the incident, such as a description of the incident, the effect on customer data, if any, actions taken by Microsoft, and/or suggested actions for customers to take to resolve the issue and prevent recurrence. Notification is delivered to the designated administrator(s) of the Microsoft online services tenant. To ensure notifications are received, you should ensure that your administrators provide and maintain accurate contact information in their tenant profiles. In addition, depending on the nature of the incident, Microsoft 365 customers can also be notified via the Microsoft 365 Service Health Dashboard.