added text

Author: diannegali

defender-xdr/investigate-respond-container-threats.md

@@ -1,6 +1,6 @@
 ---
 title: Investigate and respond to container threats in the Microsoft Defender portal
-description: Investigate and respond to container attacks and threats with cloud investigation and response capabilities in the Microsoft Defender portal.
+description: Investigate and respond to container attacks and threats with cloud investigation and response actions in the Microsoft Defender portal.
 ms.service: defender-xdr
 f1.keywords: 
   - NOCSH
@@ -29,7 +29,7 @@ appliesto:
 
 Security operations can now investigate and respond to container-related alerts in near real-time in the Microsoft Defender portal with the integration of cloud-native response actions and investigation logs to hunt for related activities. The availability of attack paths can also help analysts immediately investigate and address critical security issues to prevent a potential breach.
 
-Organizations often use containers to support their microservices, DevOps, and hybrid cloud setup. However, containers can also be targeted by threat actors and used for malicious purposes.
+As organizations use containers and Kubernetes on platforms like Azure Kubernetes Service (AKS), Google Kubernetes Engine (GKE), ad Amazon Elastic Kubernetes Service (EKS), the attack surface expands, increasing security challenges. Containers can also be targeted by threat actors and used for malicious purposes.
 
 Security operations center (SOC) analysts can now easily track container threats with near real-time alerts and immediately respond to these threats by isolating or terminating container pods. This integration allows analysts to instantly mitigate a container attack from their environment in a click.
 
@@ -42,7 +42,7 @@ The following licenses are required to view and resolve container-related alerts
 - [Microsoft Defender for Containers enabled](/azure/defender-for-cloud/defender-for-containers-introduction)
 - Microsoft Defender XDR
 
-> [!Note]
+> [!NOTE]
 > The **isolate pod** response action requires a network policy enforcer. Check whether your Kubernetes cluster has a network policy installed.
 
 Users on the [Microsoft Defender for Cloud Security Posture Management](/azure/defender-for-cloud/concept-cloud-security-posture-management) plan can view attack paths in the incident graph.
@@ -59,3 +59,35 @@ To perform any of the response actions, users must have the following permission
 |Response|Manage|
 
 For more information on these permissions, see [Permissions in Microsoft Defender XDR Unified role-based access control (RBAC)](custom-permissions-details.md).
+
+## Investigate container threats
+
+To investigate container threats in the Microsoft Defender portal:
+
+1. Select **Investigation & response > Incidents and alerts** in the left-hand navigation menu to open the incident or alert queues.
+2. In the queue, select **Filter** and choose **Microsoft Defender for Cloud > Microsoft Defender for Containers** under Service source.
+3. In the incident graph, select the pod/service/cluster entity you need to investigate. Select **Kubernetes service details**, **Kubernetes pod details**, **Kubernetes cluster details**, or **Container registry details** to view relevant information about the service, pod, or registry.
+
+Using [Threat analytics](threat-analytics.md) reports, analysts can utilize threat intelligence from expert Microsoft security researchers to learn about active threat actors and campaigns exploiting containers, new attack techniques that might affect containers, and prevalent threats that affect containers.
+
+Access threat analytics reports from **Threat intelligence > Threat analytics**. You can also open a specific report from the incident page by selecting **View threat analytics report** under **Related threats** on the incident side pane.
+
+Threat analytics reports also contain relevant mitigation, recovery, and prevention methods that analysts can assess and apply to their environment. Using the information in threat analytics reports helps SOC teams defend and protect their environment from container attacks. Here’s an example of an analyst report about a container attack.
+
+## Respond to container threats
+
+You can **isolate** or **terminate** a pod once you determine that a pod is compromised or malicious. In the incident graph, select the pod then go to **Actions** to view the available response actions. You can also find these response actions on the entity side pane.
+
+You can release a pod from isolation with the **release from isolation** action once your investigation is complete. This option appears on the side pane for isolated pods.
+
+Details of all response actions can be viewed in the [Action center](m365d-action-center.md). In the Action center page, select the response action you want to inspect to view more information about the action like which entity was acted on, when the action was done, and view the comments on the action. For isolated pods, the **release from isolation** action is also available in the Action center details pane.
+
+## Hunt for container-related activities
+
+To determine the full scope of a container attack, you can deepen your investigation with the **Go hunt** action available in the incident graph. You can immediately view all process events and activities related to container-related incidents from the incident graph.
+
+In the [Advanced hunting](advanced-hunting-overview.md) page, you can extend your search for container-related activities using the **CloudProcessEvents** and **CloudAuditEvents** tables.
+
+The **CloudProcessEvents** table contains information about process events in multi-cloud hosted environments such as Azure Kubernetes Service, Amazon Elastic Kubernetes Service, and Google Kubernetes Engine.
+
+The **CloudAuditEvents table** contains cloud audit events from cloud platforms protected by Microsoft Defender for Cloud. It also contains kube-audit logs, which holds information about Kubernetes-related events.