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/security-center/azure-container-registry-integration.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,13 +19,11 @@ ms.author: memildin
19
19
20
20
Azure Container Registry (ACR) is a managed, private Docker registry service that stores and manages your container images for Azure deployments in a central registry. It's based on the open-source Docker Registry 2.0.
21
21
22
-
If you're on Azure Security Center's standard tier, you can add the Container Registries bundle. This optional feature brings deeper visibility into the vulnerabilities of the images in your ARM-based registries. Enable or disable the bundle at the subscription level to cover all registries in a subscription. This feature is charged per image, not per scan as shown on the [pricing page](security-center-pricing.md).
23
-
24
-
Enabling the Container Registries bundle, ensures that Security Center is ready to scan images that get pushed to the registry. The scans are at the image level: Security Center isn't scanning your registry, it's scanning the images stored in the registry.
22
+
If you're on Azure Security Center's standard tier, you can add the Container Registries bundle. This optional feature brings deeper visibility into the vulnerabilities of the images in your ARM-based registries. Enable or disable the bundle at the subscription level to cover all registries in a subscription. This feature is charged per image, as shown on the [pricing page](security-center-pricing.md). Enabling the Container Registries bundle, ensures that Security Center is ready to scan images that get pushed to the registry.
25
23
26
24
Whenever an image is pushed to your registry, Security Center automatically scans that image. To trigger the scan of an image, push it to your repository.
27
25
28
-
When the scan completes (typically after approximately 10 minutes), findings are available in Security Center recommendations such as this one:
26
+
When the scan completes (typically after approximately 10 minutes), findings are available in Security Center recommendations like this:
29
27
30
28
[](media/azure-container-registry-integration/container-security-acr-page.png#lightbox)
Copy file name to clipboardExpand all lines: articles/security-center/azure-kubernetes-service-integration.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Azure Security Center and Azure Kubernetes Service | Microsoft Docs
2
+
title: Azure Security Center and Azure Kubernetes Service
3
3
description: "Learn about Azure Security Center's integration with Azure Kubernetes Services"
4
4
services: security-center
5
5
documentationcenter: na
@@ -30,22 +30,25 @@ Together, these two tools form the best cloud-native Kubernetes security offerin
30
30
31
31
Using the two services together provides:
32
32
33
-
***Security recommendations** - Security Center identifies your AKS resources and categorizes them: from clusters to individual virtual machines. You can then view security recommendations per resource. For more information, see [How to implement security recommendations](security-center-recommendations.md).
33
+
***Security recommendations** - Security Center identifies your AKS resources and categorizes them: from clusters to individual virtual machines. You can then view security recommendations per resource. For more information, see the containers recommendations in the [reference list of recommendations](recommendations-reference.md#recs-computeapp).
34
34
35
35
> [!NOTE]
36
-
> If the name of a Security Center recommendation ends with a "(Preview)" tag, it's referring to the preview nature of the recommendation; not the feature.
36
+
> If the name of a Security Center recommendation ends with a "(Preview)" tag, it's referring to the preview nature of the recommendation, not the feature.
37
37
38
-
***Environment hardening** - Security Center constantly monitors the configuration of your Kubernetes clusters, and generates security recommendations that reflect industry standards.
38
+
***Environment hardening** - Security Center constantly monitors the configuration of your Kubernetes clusters and Docker configurations, and generates security recommendations that reflect industry standards.
39
39
40
-
***Run-time protection** - Through continuous analysis of the following AKS sources, Security Center alerts you to threats and malicious activity detected at the host *and* AKS cluster level (for more information, see [threat detection for Azure containers](https://docs.microsoft.com/azure/security-center/security-center-alerts-compute#azure-containers-)):
40
+
***Run-time protection** - Through continuous analysis of the following AKS sources, Security Center alerts you to threats and malicious activity detected at the host *and* AKS cluster level (for more information, see [threat detection for Azure containers](security-center-alerts-compute.md#azure-containers-)):
41
41
* Raw security events, such as network data and process creation
42
42
* The Kubernetes audit log
43
43
44
+
For the list of possible alerts, see the following sections in the reference table of alerts: [AKS cluster level alerts](alerts-reference.md#alerts-akscluster) and [Container host level alerts](alerts-reference.md#alerts-containerhost).
45
+
44
46

45
47
46
48
> [!NOTE]
47
49
> Some of the data scanned by Azure Security Center from your Kubernetes environment may contain sensitive information.
48
50
51
+
49
52
## Next steps
50
53
51
54
To learn more about Security Center's container security features, see:
@@ -54,6 +57,4 @@ To learn more about Security Center's container security features, see:
54
57
55
58
*[Integration with Azure Container Registry](azure-container-registry-integration.md)
*[Data management at Microsoft](https://www.microsoft.com/trust-center/privacy/data-management) - Describes the data policies of Microsoft services (including Azure, Intune, and Office 365), details of Microsoft’s data management, and the retention policies that affect your data
Copy file name to clipboardExpand all lines: articles/security-center/container-security.md
+33-11Lines changed: 33 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.devlang: na
10
10
ms.topic: conceptual
11
11
ms.tgt_pltfrm: na
12
12
ms.workload: na
13
-
ms.date: 11/04/2019
13
+
ms.date: 02/11/2020
14
14
ms.author: memildin
15
15
16
16
---
@@ -19,25 +19,31 @@ ms.author: memildin
19
19
20
20
Azure Security Center is the Azure-native solution for container security. Security Center is also the optimal single pane of glass experience for the security of your cloud workloads, VMs, servers, and containers.
21
21
22
-
This article describes how you can improve, monitor, and maintain the security of your containers and their apps. You'll learn how Security Center helps with these core aspects of container security:
22
+
This article describes how Security Center helps you improve, monitor, and maintain the security of your containers and their apps. You'll learn how Security Center helps with these core aspects of container security:
To monitor your ARM-based Azure Container Registry, ensure you're on Security Center's standard tier (see [pricing](/azure/security-center/security-center-pricing)). Then enable the optional Container Registries bundle. When a new image is pushed, Security Center scans the image using a scanner from the industry-leading vulnerability scanning vendor, Qualys.
32
34
33
-
When issues are found – by Qualys or Security Center – you’ll get notified in the Security Center dashboard. For every vulnerability, Security Center provides actionable recommendations, along with a severity classification, and guidance for how to remediate the issue. For details of Security Center's recommendations, see the [reference list of recommendations](recommendations-reference.md).
35
+
When issues are found – by Qualys or Security Center – you’ll get notified in the Security Center dashboard. For every vulnerability, Security Center provides actionable recommendations, along with a severity classification, and guidance for how to remediate the issue. For details of Security Center's recommendations for containers, see the [reference list of recommendations](recommendations-reference.md#recs-containers).
34
36
35
37
## Environment hardening
36
38
37
39
### Continuous monitoring of your Docker configuration
38
-
Azure Security Center identifies unmanaged containers hosted on IaaS Linux VMs, or other Linux machines running Docker containers. Security Center continuously assesses the configurations of these containers. It then compares them with the [Center for Internet Security (CIS) Docker Benchmark](https://www.cisecurity.org/benchmark/docker/)).
40
+
Azure Security Center identifies unmanaged containers hosted on IaaS Linux VMs, or other Linux machines running Docker containers. Security Center continuously assesses the configurations of these containers. It then compares them with the [Center for Internet Security (CIS) Docker Benchmark](https://www.cisecurity.org/benchmark/docker/)).
41
+
42
+
Security Center includes the entire ruleset of the CIS Docker Benchmark and alerts you if your containers don't satisfy any of the controls. When it finds misconfigurations, Security Center generates security recommendations. Use the **recommendations page** to view recommendations and remediate issues. You'll also see the recommendations on the **Containers** tab that displays all virtual machines deployed with Docker.
43
+
44
+
For details of the relevant Security Center recommendations that might appear for this feature, see the [container section](recommendations-reference.md#recs-containers) of the recommendations reference table.
39
45
40
-
Security Center includes the entire ruleset of the CIS Docker Benchmark and alerts you if your containers don't satisfy any of the controls. When it finds misconfigurations, Security Center generates security recommendations. Use the **recommendations page** to view recommendations and remediate issues. You'll also see the recommendations on the **Containers** tab that displays all virtual machines deployed with Docker. When you're exploring the security issues on a virtual machine, Security Center provides additional information about the containers on the machine. Such information includes the Docker version and the number of images running on the host. For details of the recommendations, see [here](https://docs.microsoft.com/azure/security-center/security-center-virtual-machine-protection).
46
+
When you're exploring the security issues of a VM, Security Center provides additional information about the containers on the machine. Such information includes the Docker version and the number of images running on the host.
41
47
42
48
>[!NOTE]
43
49
> These CIS benchmark checks will not run on AKS-managed instances or Databricks-managed VMs.
@@ -49,22 +55,38 @@ AKS provides security controls and visibility into the security posture of your
49
55
* Constantly monitor the configuration of your AKS clusters
50
56
* Generate security recommendations aligned with industry standards
51
57
52
-
For details of Security Center's recommendations, see [Virtual Machine protection](security-center-virtual-machine-protection.md).
58
+
For details of the relevant Security Center recommendations that might appear for this feature, see the [container section](recommendations-reference.md#recs-containers) of the recommendations reference table.
Security Center provides real-time threat detection for your containerized environments and generates alerts for suspicious activities. You can use this information to quickly remediate security issues and improve the security of your containers.
57
63
58
64
We detect threats at the host and AKS cluster level. For full details, see [threat detection for Azure containers](https://docs.microsoft.com/azure/security-center/security-center-alerts-compute#azure-containers-).
59
65
60
-
## To view the security posture of your container-related resources
61
-
1. Open Security Center’s **Compute & apps** page.
62
-
2. Click the **Containers** tab.
63
-
The posture of your AKS clusters, ACR registries, and VMs running Docker appears.
66
+
67
+
## Container security FAQ
68
+
69
+
### What types of images can Azure Security Center scan?
70
+
Security Center scans Linux OS based images.
71
+
72
+
The Qualys scanner doesn't support "distroless" images which only contain your application and its runtime dependencies.
73
+
74
+
### How does we scan Azure Security Center scan an image?
75
+
The image is extracted from the registry. It's then run in an isolated sandbox with the Qualys scanner which extracts a list of known vulnerabilities.
76
+
77
+
### How often does Azure Security Center scan my images?
78
+
Image scans are triggered on every push.
79
+
80
+
### Can I get the scan results via REST API?
81
+
Yes. The results are under [Sub-Assessments Rest API](/rest/api/securitycenter/subassessments/list/). In addition, you can use Azure Resource Graph (ARG), the Kusto-like API for all of your resources: a query can fetch a specific scan.
82
+
64
83
65
84
## Next steps
66
85
67
-
To learn more about container security in Azure Security Center, see:
86
+
To learn more about container security in Azure Security Center, see these related articles:
87
+
88
+
* To view the security posture of your container-related resources, see the containers section of [Protect your machines and applications](security-center-virtual-machine-protection.md#containers).
89
+
68
90
* Details of the [integration with Azure Kubernetes Service](azure-kubernetes-service-integration.md)
69
91
70
92
* Details of the [integration with Azure Container Registry](azure-container-registry-integration.md)
0 commit comments