You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/concept-agentless-containers.md
+3-7Lines changed: 3 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.custom: template-concept
11
11
12
12
Identify security risks in containers and Kubernetes realms with an agentless discovery and visibility capability across SDLC and runtime.
13
13
14
-
With container vulnerability assessment insights as part of [Cloud Security Explorer](how-to-manage-cloud-security-explorer.md) and Kubernetes [Attack Path](attack-path-reference.md#attack-paths) analysis, you can maximize coverage on container posture issues and extend beyond the reach of agent-based assessments, providing a holistic approach to your posture improvement.
14
+
With container vulnerability assessment insights as part of [Cloud Security Explorer](how-to-manage-cloud-security-explorer.md) and Kubernetes [Attack Path](attack-path-reference.md#azure-containers) analysis, you can maximize coverage on container posture issues and extend beyond the reach of agent-based assessments, providing a holistic approach to your posture improvement.
15
15
16
16
Learn more about [Cloud Security Posture Management](concept-cloud-security-posture-management.md).
17
17
@@ -76,13 +76,13 @@ Verify that the settings were saved successfully - a notification message pops u
76
76
77
77
Agentless information in Defender CSPM is updated once an hour via snapshotting mechanism. It can take up to **24 hours** to see results in Cloud Security Explorer and Attack Path.
78
78
79
-
Recommendations are available based on vulnerability assessment timeline. Learn more about [agentless scanning](concept-agentless-data-collection.md).
79
+
Recommendations are available based on vulnerability assessment timeline. Learn more about [image scanning](defender-for-containers-vulnerability-assessment-azure.md).
80
80
81
81
## How agentless containers works
82
82
83
83
The system’s architecture is based on a snapshot mechanism at intervals.
84
84
85
-
<!--- :::image type="content" source="media/concept-agentless-containers/diagram-permissions-architecture.png" alt-text="Diagram of the permissions architecture." lightbox="media/concept-agentless-containers/diagram-permissions-architecture.png"::: --->
85
+
:::image type="content" source="media/concept-agentless-containers/diagram-permissions-architecture.png" alt-text="Diagram of the permissions architecture." lightbox="media/concept-agentless-containers/diagram-permissions-architecture.png":::
86
86
87
87
By enabling the Agentless discovery for Kubernetes extension, the following process occurs:
88
88
@@ -103,10 +103,6 @@ By enabling the Agentless discovery for Kubernetes extension, the following proc
103
103
104
104
1.**Bind**: Upon discovery of an AKS cluster, MDC performs an AKS bind operation between the created identity and the Kubernetes role “Microsoft.Security/pricings/microsoft-defender-operator”. The role is visible via API and gives MDC data plane read permission inside the cluster.
105
105
106
-
Agentless information in Defender CSPM is updated once an hour via snapshotting mechanism.
107
-
108
106
## Next steps
109
107
110
-
This article explains how agentless container posture works.
111
-
112
108
Learn more about [Cloud Security Posture Management](concept-cloud-security-posture-management.md).
0 commit comments