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/active-directory/fundamentals/active-directory-deployment-checklist-p2.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,19 +16,19 @@ ms.reviewer:
16
16
---
17
17
# Azure Active Directory Premium P2 licensing feature checklist
18
18
19
-
It can seem daunting to deploy Azure Active Directory (Azure AD) for your organization and keep it secure. This article identifies some common tasks that customers find helpful to complete over the course of 30 days, 90 days, or beyond to enhance their security posture. Even organizations who have already deployed Azure AD can use this checklist to ensure they are getting the most out of their investment.
19
+
It can seem overwhelming to deploy Azure Active Directory (Azure AD) for your organization and keep it secure. This article identifies some common tasks that customers find helpful. Customers typically complete these tasks over the course of 30 days, 90 days, or beyond to enhance their security posture. Even organizations who have already deployed Azure AD can use this checklist to make sure they're getting the most out of their investment.
20
20
21
21
A well-planned and executed identity infrastructure paves the way for more secure access to your productivity workloads and data only by authenticated users and devices.
22
22
23
23
## Prerequisites
24
24
25
-
This guide assumes you have Azure AD Premium P2 licenses, Enterprise Mobility + Security E5, Microsoft 365 E5, or an equivalent license bundle.
25
+
This guide assumes you have Azure AD Premium P2 licenses, Enterprise Mobility + Security E5, Microsoft 365 E5, or a similar license bundle.
26
26
27
27
[Azure AD licensing](https://azure.microsoft.com/pricing/details/active-directory/)
Copy file name to clipboardExpand all lines: articles/active-directory/hybrid/reference-connect-germany.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,8 +22,9 @@ ms.author: billmath
22
22
# Azure AD Connect in Microsoft Cloud Germany - Public Preview
23
23
## Introduction
24
24
Azure AD Connect provides synchronization between your on-premises Active Directory and Azure Active Directory.
25
-
Currently, many of the scenarios in [Microsoft Cloud Germany](https://www.microsoft.com/de-de/cloud/deutschland/default.aspx) must be done by the operator.
26
-
When using Microsoft Cloud Germany, you must be aware of the following:
25
+
Currently, many of the scenarios in [Microsoft Cloud Germany](https://azure.microsoft.com/global-infrastructure/germany/
26
+
) must be done by the operator.
27
+
When using Microsoft Cloud Germany, you must be aware of the following information:
27
28
28
29
* The following URLs must be opened on a proxy server for synchronization to occur successfully:
29
30
@@ -37,13 +38,13 @@ When using Microsoft Cloud Germany, you must be aware of the following:
37
38
You can download Azure AD Connect from the Azure AD Connect blade within the portal. Use the instructions below to locate the Azure AD Connect blade.
38
39
39
40
### The Azure AD Connect Blade
40
-
Once you have signed in to the Azure portal, do the following:
41
+
Once you've signed in to the Azure portal:
41
42
42
43
1. Go to Browse
43
44
2. Select Azure Active Directory
44
45
3. Then select Azure AD Connect
45
46
46
-
You should see the following:
47
+
You'll see these details:
47
48
48
49

49
50
@@ -59,5 +60,5 @@ The following table describes the features shown in the blade.
59
60
To install Azure AD Connect, you can use the documentation [here](how-to-connect-install-roadmap.md).
60
61
61
62
## Advanced features and Additional Information
62
-
For additional information and guidance on custom settings or advanced configurations, start with[Integrating your on-premises identities with Azure Active Directory](whatis-hybrid-identity.md). This page provides information and links to additional guidance.
63
+
For additional information about custom settings or advanced configurations, go to[Integrating your on-premises identities with Azure Active Directory](whatis-hybrid-identity.md). This page provides information and links to additional guidance.
-[Sign in to Azure portal](https://portal.azure.com)
38
-
39
-
-[Create a Linux virtual machine](/azure/virtual-machines/linux/quick-create-portal)
40
-
41
-
-[Enable system-assigned managed identity on your virtual machine](/azure/active-directory/managed-service-identity/qs-configure-portal-windows-vm#enable-system-assigned-identity-on-an-existing-vm)
42
-
43
35
## Grant your VM access to a Resource Group in Azure Resource Manager
44
36
45
37
Using managed identities for Azure resources, your code can get access tokens to authenticate to resources that support Azure AD authentication. The Azure Resource Manager API supports Azure AD authentication. First, we need to grant this VM's identity access to a resource in Azure Resource Manager, in this case the Resource Group in which the VM is contained.
-[Sign in to Azure portal](https://portal.azure.com)
37
-
38
-
-[Create a Windows virtual machine](/azure/virtual-machines/windows/quick-create-portal)
39
-
40
-
-[Enable system-assigned managed identity on your virtual machine](/azure/active-directory/managed-service-identity/qs-configure-portal-windows-vm#enable-system-assigned-identity-on-an-existing-vm)
41
-
42
34
## Grant your VM access to a resource group in Resource Manager
43
35
Using managed identities for Azure resources, your code can get access tokens to authenticate to resources that support Azure AD authentication. The Azure Resource Manager supports Azure AD authentication. First, we need to grant this VM’s system-assigned managed identity access to a resource in Resource Manager, in this case the Resource Group in which the VM is contained.
Copy file name to clipboardExpand all lines: articles/application-gateway/waf-overview.md
+19-13Lines changed: 19 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,21 +4,25 @@ description: This article provides an overview of web application firewall (WAF)
4
4
services: application-gateway
5
5
author: vhorne
6
6
ms.service: application-gateway
7
-
ms.date: 11/7/2018
7
+
ms.date: 11/16/2018
8
8
ms.author: amsriva
9
9
---
10
10
11
11
# Web application firewall (WAF)
12
12
13
-
Web application firewall (WAF) is a feature of Application Gateway that provides centralized protection of your web applications from common exploits and vulnerabilities.
13
+
Web application firewall (WAF) is a feature of Application Gateway that provides centralized protection of your web applications from common exploits and vulnerabilities.
14
14
15
-
Web applications are increasingly targets of malicious attacks that exploit common known vulnerabilities. Common among these exploits are SQL injection attacks, cross site scripting attacks to name a few. Preventing such attacks in application code can be challenging and may require rigorous maintenance, patching and monitoring at multiple layers of the application topology. A centralized web application firewall helps make security management much simpler and gives better assurance to application administrators against threats or intrusions. A WAF solution can also react to a security threat faster by patching a known vulnerability at a central location versus securing each of individual web applications. Existing application gateways can be converted to a web application firewall enabled application gateway easily.
15
+
Web applications are increasingly targets of malicious attacks that exploit common known vulnerabilities. Common among these exploits are SQL injection attacks, and cross site scripting attacks to name a few.
16
+
17
+
Preventing such attacks in application code can be challenging and may require rigorous maintenance, patching and monitoring at multiple layers of the application topology. A centralized web application firewall helps make security management much simpler and gives better assurance to application administrators against threats or intrusions. A WAF solution can also react to a security threat faster by patching a known vulnerability at a central location, instead of securing each of individual web applications. Existing application gateways can be converted to a web application firewall enabled application gateway easily.
16
18
17
19
WAF is based on rules from the [OWASP core rule sets](https://www.owasp.org/index.php/Category:OWASP_ModSecurity_Core_Rule_Set_Project) 3.0 or 2.2.9. It automatically updates to include protection against new vulnerabilities, with no additional configuration needed.
18
20
19
21

20
22
21
-
Application Gateway operates as an application delivery controller (ADC) and offers SSL termination, cookie-based session affinity, round-robin load distribution, content-based routing, ability to host multiple websites and security enhancements. Security enhancements offered by Application Gateway include SSL policy management, end to end SSL support. Application security is now strengthened by WAF (web application firewall) being directly integrated into the ADC offering. This provides an easy to configure central location to manage and protect your web applications against common web vulnerabilities.
23
+
Application Gateway operates as an application delivery controller (ADC) and offers SSL termination, cookie-based session affinity, round-robin load distribution, content-based routing, ability to host multiple websites, and security enhancements.
24
+
25
+
Security enhancements offered by Application Gateway include SSL policy management, and end to end SSL support. Application security is now strengthened by WAF (web application firewall) being directly integrated into the ADC offering. This provides an easy to configure central location to manage and protect your web applications against common web vulnerabilities.
22
26
23
27
## Benefits
24
28
@@ -48,11 +52,11 @@ The following are the core benefits that Application Gateway and web application
48
52
- Protection against HTTP protocol violations
49
53
- Protection against HTTP protocol anomalies such as missing host user-agent and accept headers
50
54
- Prevention against bots, crawlers, and scanners
51
-
- Detection of common application misconfigurations (that is, Apache, IIS, etc.)
55
+
- Detection of common application misconfigurations (for example, Apache, IIS, and so on)
52
56
53
57
### Public preview features
54
58
55
-
The current WAF public preview SKU incudes the following features:
59
+
The current WAF public preview SKU includes the following features:
56
60
57
61
-**Request size limits** - Web Application Firewall allows users to configure request size limits within lower and upper bounds.
58
62
-**Exclusion lists** - WAF exclusion lists allow users to omit certain request attributes from a WAF evaluation. A common example is Active Directory inserted tokens that are used for authentication or password fields.
@@ -75,9 +79,9 @@ Web application firewall comes preconfigured with CRS 3.0 by default or you can
75
79
- Protection against HTTP protocol violations
76
80
- Protection against HTTP protocol anomalies such as missing host user-agent and accept headers
77
81
- Prevention against bots, crawlers, and scanners
78
-
- Detection of common application misconfigurations (i.e. Apache, IIS, etc.)
82
+
- Detection of common application misconfigurations (for example, Apache, IIS, etc.)
79
83
80
-
For a more detailed list of rules and their protections see [Core rule sets](#core-rule-sets).
84
+
For a more detailed list of rules and their protections, see [Core rule sets](#core-rule-sets).
81
85
82
86
83
87
#### OWASP_3.0
@@ -86,7 +90,7 @@ The 3.0 core rule set provided has 13 rule groups as shown in the following tabl
86
90
87
91
|RuleGroup|Description|
88
92
|---|---|
89
-
|**[REQUEST-911-METHOD-ENFORCEMENT](application-gateway-crs-rulegroups-rules.md#crs911)**|Contains rules to lock down methods (PUT, PATCH< ..)|
93
+
|**[REQUEST-911-METHOD-ENFORCEMENT](application-gateway-crs-rulegroups-rules.md#crs911)**|Contains rules to lock down methods (PUT, PATCH)|
90
94
|**[REQUEST-913-SCANNER-DETECTION](application-gateway-crs-rulegroups-rules.md#crs913)**| Contains rules to protect against port and environment scanners.|
91
95
|**[REQUEST-920-PROTOCOL-ENFORCEMENT](application-gateway-crs-rulegroups-rules.md#crs920)**|Contains rules to protect against protocol and encoding issues.|
92
96
|**[REQUEST-921-PROTOCOL-ATTACK](application-gateway-crs-rulegroups-rules.md#crs921)**|Contains rules to protect against header injection, request smuggling, and response splitting|
@@ -119,18 +123,18 @@ The 2.2.9 core rule set provided has 10 rule groups as shown in the following ta
119
123
120
124
Application Gateway WAF can be configured to run in the following two modes:
121
125
122
-
***Detection mode** – When configured to run in detection mode, Application Gateway WAF monitors and logs in all threat alerts to a log file. Logging diagnostics for Application Gateway should be turned on using the **Diagnostics** section. You also need to ensure that the WAF log is selected and turned on. When running in detection mode web application firewall does not block incoming requests.
126
+
***Detection mode** – When configured to run in detection mode, Application Gateway WAF monitors and logs all threat alerts to a log file. Logging diagnostics for Application Gateway should be turned on using the **Diagnostics** section. You also need to ensure that the WAF log is selected and turned on. When running in detection mode web application firewall does not block incoming requests.
123
127
***Prevention mode** – When configured to run in prevention mode, Application Gateway actively blocks intrusions and attacks detected by its rules. The attacker receives a 403 unauthorized access exception and the connection is terminated. Prevention mode continues to log such attacks in the WAF logs.
Monitoring the health of your application gateway is important. Monitoring the health of your web application firewall and the applications that it protects are provided through logging and integration with Azure Monitor, Azure Security Center (coming soon), and Log Analytics.
131
+
Monitoring the health of your application gateway is important. Monitoring the health of your web application firewall and the applications that it protects are provided through logging and integration with Azure Monitor, Azure Security Center, and Log Analytics.
Each application gateway log is integrated with [Azure Monitor](../monitoring-and-diagnostics/monitoring-overview.md). This allows you to track diagnostic information including WAF alerts and logs. This capability is provided within the Application Gateway resource in the portal under the **Diagnostics** tab or through the Azure Monitor service directly. To learn more about enabling diagnostic logs for application gateway see [Application Gateway diagnostics](application-gateway-diagnostics.md)
137
+
Each application gateway log is integrated with [Azure Monitor](../monitoring-and-diagnostics/monitoring-overview.md). This allows you to track diagnostic information including WAF alerts and logs. This capability is provided within the Application Gateway resource in the portal under the **Diagnostics** tab or through the Azure Monitor service directly. To learn more about enabling diagnostic logs for application gateway, see [Application Gateway diagnostics](application-gateway-diagnostics.md)
134
138
135
139
#### Azure Security Center
136
140
@@ -174,7 +178,9 @@ Application Gateway WAF provides detailed reporting on each threat it detects. L
174
178
175
179
## Application Gateway WAF SKU pricing
176
180
177
-
Web application firewall is available under a new a WAF SKU. This SKU is available only in Azure Resource Manager provisioning model and not under the classic deployment model. Additionally WAF SKU comes only in medium and large application gateway instance sizes. All the limits for application gateway also apply to the WAF SKU. Pricing is based on per hour gateway instance charge and data processing charge. Per hour gateway pricing for WAF SKU is different from Standard SKU charges and can be found at [Application Gateway pricing details](https://azure.microsoft.com/pricing/details/application-gateway/). Data processing charges remain the same. There is no per rule or rule group charges. You can protect multiple web applications behind the same web application firewall and there are no additional charges for supporting multiple applications.
181
+
Web application firewall is available under a new a WAF SKU. This SKU is available only in Azure Resource Manager provisioning model and not under the classic deployment model. Additionally, the WAF SKU comes only in medium and large application gateway instance sizes. All the limits for application gateway also apply to the WAF SKU.
182
+
183
+
Pricing is based on per hour gateway instance charge and data processing charge. Per hour gateway pricing for WAF SKU is different from Standard SKU charges and can be found at [Application Gateway pricing details](https://azure.microsoft.com/pricing/details/application-gateway/). Data processing charges remain the same. There's no per rule or rule group charges. You can protect multiple web applications behind the same web application firewall and you are not charged for supporting multiple applications.
0 commit comments