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/recommendations-reference.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,6 +159,7 @@ Your Secure Score is based on the number of Security Center recommendations you'
159
159
## Next steps
160
160
To learn more about recommendations, see the following:
161
161
162
+
*[The Microsoft Learn module on how to analyze the recommendations made by Security Center](https://docs.microsoft.com/learn/modules/identify-threats-with-azure-security-center/)
162
163
*[Security recommendations in Azure Security Center](security-center-recommendations.md)
163
164
*[Protecting your machines and applications](security-center-virtual-machine-protection.md)
164
165
*[Protecting your network in Azure Security Center](security-center-network-recommendations.md)
Copy file name to clipboardExpand all lines: articles/security-center/security-center-just-in-time.md
+15-14Lines changed: 15 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ From Security Center, you can configure a JIT policy and request access to a VM
73
73
1. Click **Save**.
74
74
75
75
> [!NOTE]
76
-
>When JIT VM Access is enabled for a VM, Azure Security Center creates "deny all inbound traffic" rules for the selected ports in the network security groups associated and Azure Firewall with it. If other rules had been created for the selected ports, then the existing rules take priority over the new “deny all inbound traffic” rules. If there are no existing rules on the selected ports, then the new “deny all inbound traffic” rules take top priority in the Network Security Groups and Azure Firewall.
76
+
>When JIT VM Access is enabled for a VM, Azure Security Center creates "deny all inbound traffic" rules for the selected ports in the network security groups associated and Azure Firewall with it. If other rules had been created for the selected ports, then the existing rules take priority over the new "deny all inbound traffic" rules. If there are no existing rules on the selected ports, then the new "deny all inbound traffic" rules take top priority in the Network Security Groups and Azure Firewall.
77
77
78
78
79
79
## Request JIT access via Security Center
@@ -84,7 +84,7 @@ To request access to a VM via Security Center:
84
84
85
85
1. Under **Virtual Machine**, click the VMs that you want to request access for. This puts a checkmark next to the VM.
86
86
87
-
- The icon in the **Connection Details** column indicates whether JIT is enabled on the NSG or FW. If it’s enabled on both, only the Firewall icon appears.
87
+
- The icon in the **Connection Details** column indicates whether JIT is enabled on the NSG or FW. If it's enabled on both, only the Firewall icon appears.
88
88
89
89
- The **Connection Details** column provides the information required to connect the VM, and its open ports.
90
90
@@ -173,7 +173,7 @@ In the Azure portal, when you try to connect to a VM, Azure checks to see if you
173
173
174
174
Access is requested with the following default parameters:
175
175
176
-
-**source IP**: ‘Any’ (*) (cannot be changed)
176
+
-**source IP**: 'Any' (*) (cannot be changed)
177
177
-**time range**: Three hours (cannot be changed) <!--Isn't this set in the policy-->
178
178
-**port number** RDP port 3389 for Windows / port 22 for Linux (can be changed)
179
179
@@ -198,14 +198,14 @@ To use the just-in-time VM access solution via PowerShell, use the official Azur
198
198
199
199
The following example sets a just-in-time VM access policy on a specific VM, and sets the following:
200
200
201
-
1.Close ports 22 and 3389.
201
+
1.Close ports 22 and 3389.
202
202
203
-
2.Set a maximum time window of 3 hours for each so they can be opened per approved request.
204
-
3.Allows the user who is requesting access to control the source IP addresses and allows the user to establish a successful session upon an approved just-in-time access request.
203
+
2.Set a maximum time window of 3 hours for each so they can be opened per approved request.
204
+
3.Allows the user who is requesting access to control the source IP addresses and allows the user to establish a successful session upon an approved just-in-time access request.
205
205
206
206
Run the following in PowerShell to accomplish this:
207
207
208
-
1.Assign a variable that holds the just-in-time VM access policy for a VM:
208
+
1.Assign a variable that holds the just-in-time VM access policy for a VM:
In the following example, you can see a just-in-time VM access request to a specific VM in which port 22 is requested to be opened for a specific IP address and for a specific amount of time:
@@ -267,6 +267,7 @@ In this article, you learned how just-in-time VM access in Security Center helps
267
267
268
268
To learn more about Security Center, see the following:
269
269
270
+
- The Microsoft Learn module [Protect your servers and VMs from brute-force and malware attacks with Azure Security Center](https://docs.microsoft.com/learn/modules/secure-vms-with-azure-security-center/)
270
271
-[Setting security policies](tutorial-security-policy.md) — Learn how to configure security policies for your Azure subscriptions and resource groups.
271
272
-[Managing security recommendations](security-center-recommendations.md) — Learn how recommendations help you protect your Azure resources.
272
273
-[Security health monitoring](security-center-monitoring.md) — Learn how to monitor the health of your Azure resources.
Copy file name to clipboardExpand all lines: articles/security-center/security-center-managing-and-responding-alerts.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,5 +68,6 @@ Security Center automatically collects, analyzes, and integrates log data from y
68
68
69
69
In this document, you learned how to configure security policies in Security Center. To learn more about Security Center, see the following:
70
70
71
+
-[The Microsoft Learn module on how to use the alert capabilities of Azure Security Center to watch for and respond to threats](https://docs.microsoft.com/learn/modules/resolve-threats-with-azure-security-center/)
71
72
*[Security alerts in Azure Security Center](security-center-alerts-overview.md).
Copy file name to clipboardExpand all lines: articles/security-center/workflow-automation.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,10 +92,11 @@ To view the raw event schemas of the security alerts or recommendations events p
92
92
93
93
## Next steps
94
94
95
-
In this article, you learned about creating Logic Apps, running them manually in Security Center, and automating their execution.
95
+
In this article, you learned about creating Logic Apps, automating their execution in Security Center, and running them manually.
96
96
97
-
For other related material, see the following articles:
97
+
For other related material, see:
98
98
99
+
-[The Microsoft Learn module on how to use workflow automation to automate a security response](https://docs.microsoft.com/learn/modules/resolve-threats-with-azure-security-center/)
99
100
-[Security recommendations in Azure Security Center](security-center-recommendations.md)
100
101
-[Security alerts in Azure Security Center](security-center-alerts-overview.md)
0 commit comments