Skip to content

Commit a50deea

Browse files
committed
Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into asc-melvyn-20200129
2 parents 2cbd271 + ef58a35 commit a50deea

11 files changed

+54
-54
lines changed

articles/aks/control-kubeconfig-access.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Limit access to kubeconfig in Azure Kubernetes Service (AKS)
33
description: Learn how to control access to the Kubernetes configuration file (kubeconfig) for cluster administrators and cluster users
44
services: container-service
55
ms.topic: article
6-
ms.date: 01/28/2020
6+
ms.date: 05/06/2020
77

88
---
99

@@ -36,7 +36,7 @@ The two built-in roles are:
3636

3737
These RBAC roles can be applied to an Azure Active Directory (AD) user or group.
3838

39-
> ![NOTE]
39+
> [!NOTE]
4040
> On clusters that use Azure AD, users with the *clusterUser* role have an empty *kubeconfig* file that prompts a log in. Once logged in, users have access based on their Azure AD user or group settings. Users with the *clusterAdmin* role have admin access.
4141
>
4242
> Clusters that do not use Azure AD only use the *clusterAdmin* role.

articles/azure-functions/durable/quickstart-js-vscode.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,14 @@ description: Create and publish an Azure Durable Function using Visual Studio Co
44
author: anthonychu
55

66
ms.topic: quickstart
7-
ms.date: 03/24/2020
7+
ms.date: 05/07/2020
88
ms.reviewer: azfuncdf, antchu
99
---
1010

1111
# Create your first durable function in JavaScript
1212

1313
*Durable Functions* is an extension of [Azure Functions](../functions-overview.md) that lets you write stateful functions in a serverless environment. The extension manages state, checkpoints, and restarts for you.
1414

15-
[!INCLUDE [v1-note](../../../includes/functions-durable-v1-tutorial-note.md)]
16-
1715
In this article, you learn how to use the Visual Studio Code Azure Functions extension to locally create and test a "hello world" durable function. This function will orchestrate and chain together calls to other functions. You then publish the function code to Azure.
1816

1917
![Running durable function in Azure](./media/quickstart-js-vscode/functions-vs-code-complete.png)
@@ -57,7 +55,7 @@ Visual Studio Code installs the Azure Functions Core Tools, if needed. It also c
5755

5856
A package.json file is also created in the root folder.
5957

60-
### Enable Azure Functions V2 compatibility mode
58+
### Enable compatibility mode
6159

6260
Currently, JavaScript Durable Functions require Azure Functions V2 compatibility mode to be enabled.
6361

@@ -200,7 +198,7 @@ After you've verified that the function runs correctly on your local computer, i
200198

201199
[!INCLUDE [functions-publish-project-vscode](../../../includes/functions-publish-project-vscode.md)]
202200

203-
### Enable Azure Functions V2 compatibility mode
201+
### Enable compatibility mode
204202

205203
The same Azure Functions V2 compatibility that you enabled locally needs to be enabled in the app in Azure.
206204

articles/azure-functions/functions-bindings-event-grid-trigger.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -567,4 +567,4 @@ The Event Grid trigger function executes and shows logs similar to the following
567567
568568
## Next steps
569569
570-
* [Dispatch an Event Grid event](./functions-bindings-event-grid-trigger.md)
570+
* [Dispatch an Event Grid event](./functions-bindings-event-grid-output.md)

articles/security-center/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -113,7 +113,7 @@
113113
href: custom-security-policies.md
114114
- name: Manage policies with the Azure Policy REST API
115115
href: configure-security-policy-azure-policy.md
116-
- name: Add dynamic compliance packages
116+
- name: Choose standards for your compliance dashboard
117117
href: update-regulatory-compliance-packages.md
118118
- name: Customize the information protection policy
119119
href: security-center-info-protection-policy.md
Loading
97.7 KB
Loading

articles/security-center/update-regulatory-compliance-packages.md

Lines changed: 31 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -15,74 +15,75 @@ ms.date: 11/04/2019
1515
ms.author: memildin
1616

1717
---
18-
# Update to dynamic compliance packages in your Regulatory Compliance dashboard
18+
# Customizing the set of standards in your regulatory compliance dashboard
1919

2020
Azure Security Center continually compares the configuration of your resources with requirements in industry standards, regulations, and benchmarks. The **regulatory compliance dashboard** provides insights into your compliance posture based on how you're meeting specific compliance controls and requirements.
2121

22-
With the **dynamic compliance packages** feature, Security Center *automatically improves its coverage of industry standards over time*.
2322

24-
One standard for which you can track your compliance posture is [Azure CIS 1.1.0](https://www.cisecurity.org/benchmark/azure/) (more formally, the "CIS Microsoft Azure Foundations Benchmark version 1.1.0"). The representation of Azure CIS that initially appears in your compliance dashboard relies on a static set of rules that is included with Security Center.
23+
## Overview of compliance packages
2524

26-
Compliance packages are essentially initiatives defined in Azure Policy. They can be assigned to your selected scope (subscription, management group, and so on). To see compliance data mapped as assessments in your dashboard, add a compliance package to your management group or subscription from within the Security Policy. Adding a compliance package effectively assigns the regulatory compliance initiative to your selected scope. In this way, you can track newly published regulatory initiatives as compliance standards in your dashboard. When Microsoft releases new content for the initiative (new policies that map to more controls in the standard), the additional content appears automatically in your dashboard.
25+
Industry standards, regulatory standards, and benchmarks are represented in Security Center as *compliance packages*. Each package is an initiative defined in Azure Policy. To see compliance data mapped as assessments in your dashboard, add a compliance package to your management group or subscription from within the **Security policy** page. (Learn more about Azure Policy and initiatives in [Working with security policies](tutorial-security-policy.md).)
2726

28-
The dynamic compliance package for the Azure CIS benchmark, **Azure CIS 1.1.0 (new)**, improves on the original *static* version by:
27+
When you've onboarded a standard or benchmark to your selected scope, the standard appears in your regulatory compliance dashboard with all associated compliance data mapped as assessments. You can also download summary reports for any of the standards that have been onboarded.
2928

30-
* Including more policies
31-
* Automatically updating with new coverage as it's added
29+
Microsoft also tracks the regulatory standards themselves and automatically improves its coverage in some of the packages over time. When Microsoft releases new content for the initiative (new policies that map to more controls in the standard), the additional content appears automatically in your dashboard.
3230

33-
Update to the new dynamic package as described below.
31+
> [!TIP]
32+
> One standard which improves over time as Microsoft releases new content is **Azure CIS 1.1.0 (new)** (more formally, the [CIS Microsoft Azure Foundations Benchmark version 1.1.0](https://www.cisecurity.org/benchmark/azure/)). You'll need to add this to your dashboard alongside "Azure CIS 1.1.0", the representation of Azure CIS that is configured by default in every Security Center environment. That package relies on a static set of rules. The newer package includes more policies and will automatically update over time. Update to the new dynamic package as described below.
3433
35-
## Adding a dynamic compliance package
3634

37-
The following steps explain how to add the dynamic package for monitoring your compliance with the Azure CIS benchmark v1.1.0.
35+
## Available packages
3836

39-
### Update to the Azure CIS 1.1.0 (new) dynamic compliance package
37+
You can add standards such as NIST SP 800-53 R4, SWIFT CSP CSCF-v2020, UK Official and UK NHS, Canada Federal PBMM, and Azure CIS 1.1.0 (new) - a more complete representation of Azure CIS 1.1.0.
38+
39+
In addition, you can add **Azure Security Benchmark**, the Microsoft-authored, Azure-specific guidelines for security and compliance best practices based on common compliance frameworks. ([Learn more about Azure Security Benchmark](https://docs.microsoft.com/azure/security/benchmarks/introduction).)
40+
41+
Additional standards will be supported in the dashboard as they become available.
42+
43+
44+
## Adding a regulatory standard to your dashboard
45+
46+
The following steps explain how to add a package to monitor your compliance with one of the supported regulatory standards.
47+
48+
> [!NOTE]
49+
> Only users who are owner or policy contributor have the necessary permissions to add compliance standards.
4050
4151
1. From Security Center's sidebar, select **Regulatory compliance** to open the regulatory compliance dashboard. Here you can see the compliance standards currently assigned to the currently selected subscriptions.
4252

43-
1. From the top of the page, select **Manage compliance policies**. This opens the Policy Management page.
53+
1. From the top of the page, select **Manage compliance policies**. The Policy Management page appears.
4454

4555
1. Select the subscription or management group for which you want to manage the regulatory compliance posture.
4656

4757
> [!TIP]
4858
> We recommend selecting the highest scope for which the standard is applicable so that compliance data is aggregated and tracked for all nested resources.
4959
50-
1. In the Industry & regulatory standards section, you'll see that Azure CIS 1.1.0 can be updated for new content. Click **Update now**.
60+
1. To add the standards relevant to your organization, click **Add more standards**.
5161

52-
1. Optionally, click **Add more standards** to open the **Add regulatory compliance standards** page. There, you can search manually for **Azure CIS 1.1.0 (New)** and dynamic packages for other compliance standards such as:
62+
1. From the **Add regulatory compliance standards** page, you can search for packages for any of the available standards. Some of the standards available are:
5363

54-
- **Azure Security Benchmark** ([details here](https://docs.microsoft.com/azure/security/benchmarks/introduction))
64+
- **Azure Security Benchmark**
5565
- **NIST SP 800-53 R4**
5666
- **SWIFT CSP CSCF-v2020**
5767
- **UKO and UK NHS**
5868
- **Canada PBMM**
5969

60-
> [!TIP]
61-
> Only users who are owner or policy contributor have the necessary permissions to add compliance standards.
62-
6370
![Adding regulatory packages to Azure Security Center's regulatory compliance dashboard](./media/update-regulatory-compliance-packages/dynamic-regulatory-compliance-additional-standards.png)
6471

65-
6672
1. From Security Center's sidebar, select **Regulatory compliance** again to go back to the regulatory compliance dashboard.
67-
* **Azure CIS 1.1.0 (New)** now appears in your list of Industry & regulatory standards.
68-
* The original *static* view of your Azure CIS 1.1.0 compliance will also remain alongside it. It may be automatically removed in the future.
73+
* Your new standard appears in your list of Industry & regulatory standards.
74+
* If you've added **Azure CIS 1.1.0 (New)**, the original *static* view of your Azure CIS 1.1.0 compliance will also remain alongside it. It may be automatically removed in the future.
6975

7076
> [!NOTE]
7177
> It may take a few hours for a newly added standard to appear in the compliance dashboard.
7278
73-
74-
[![Regulatory compliance dashboard showing old and new Azure CIS](media/update-regulatory-compliance-packages/security-center-dynamic-regulatory-compliance-cis-old-and-new.png)](media/update-regulatory-compliance-packages/security-center-dynamic-regulatory-compliance-cis-old-and-new.png#lightbox)
75-
79+
[![Regulatory compliance dashboard showing old and new Azure CIS](media/update-regulatory-compliance-packages/regulatory-compliance-dashboard-with-asb-small.png)](media/update-regulatory-compliance-packages/regulatory-compliance-dashboard-with-asb.png#lightbox)
7680

7781
## Next steps
7882

79-
In this article, you learned:
80-
81-
* How to **upgrade the standards** shown in your regulatory compliance dashboard to the new *dynamic* packages
82-
* How to **add compliance packages** to monitor your compliance with additional standards.
83+
In this article, you learned how to **add compliance packages** to monitor your compliance with additional standards.
8384

8485
For other related material, see the following articles:
8586

87+
- [Azure Security Benchmark](https://docs.microsoft.com/azure/security/benchmarks/introduction)
8688
- [Security center regulatory compliance dashboard](security-center-compliance-dashboard.md)
87-
- [Working with security policies](tutorial-security-policy.md)
88-
- [Managing security recommendations in Azure Security Center](security-center-recommendations.md) - Learn how to use recommendations in Azure Security Center to help protect your Azure resources.
89+
- [Working with security policies](tutorial-security-policy.md)

0 commit comments

Comments
 (0)