Skip to content

Commit b831e69

Browse files
committed
Added links to MS Learn
1 parent 50d0be8 commit b831e69

File tree

4 files changed

+20
-16
lines changed

4 files changed

+20
-16
lines changed

articles/security-center/recommendations-reference.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,7 @@ Your Secure Score is based on the number of Security Center recommendations you'
159159
## Next steps
160160
To learn more about recommendations, see the following:
161161

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/)
162163
* [Security recommendations in Azure Security Center](security-center-recommendations.md)
163164
* [Protecting your machines and applications](security-center-virtual-machine-protection.md)
164165
* [Protecting your network in Azure Security Center](security-center-network-recommendations.md)

articles/security-center/security-center-just-in-time.md

Lines changed: 15 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ From Security Center, you can configure a JIT policy and request access to a VM
7373
1. Click **Save**.
7474

7575
> [!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.
7777
7878

7979
## Request JIT access via Security Center
@@ -84,7 +84,7 @@ To request access to a VM via Security Center:
8484

8585
1. Under **Virtual Machine**, click the VMs that you want to request access for. This puts a checkmark next to the VM.
8686

87-
- The icon in the **Connection Details** column indicates whether JIT is enabled on the NSG or FW. If its 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.
8888

8989
- The **Connection Details** column provides the information required to connect the VM, and its open ports.
9090

@@ -173,7 +173,7 @@ In the Azure portal, when you try to connect to a VM, Azure checks to see if you
173173
174174
Access is requested with the following default parameters:
175175

176-
- **source IP**: Any (*) (cannot be changed)
176+
- **source IP**: 'Any' (*) (cannot be changed)
177177
- **time range**: Three hours (cannot be changed) <!--Isn't this set in the policy-->
178178
- **port number** RDP port 3389 for Windows / port 22 for Linux (can be changed)
179179

@@ -198,14 +198,14 @@ To use the just-in-time VM access solution via PowerShell, use the official Azur
198198

199199
The following example sets a just-in-time VM access policy on a specific VM, and sets the following:
200200

201-
1. Close ports 22 and 3389.
201+
1. Close ports 22 and 3389.
202202

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.
205205

206206
Run the following in PowerShell to accomplish this:
207207

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:
209209

210210
$JitPolicy = (@{
211211
id="/subscriptions/SUBSCRIPTIONID/resourceGroups/RESOURCEGROUP/providers/Microsoft.Compute/virtualMachines/VMNAME"
@@ -220,31 +220,31 @@ Run the following in PowerShell to accomplish this:
220220
allowedSourceAddressPrefix=@("*");
221221
maxRequestAccessDuration="PT3H"})})
222222

223-
2. Insert the VM just-in-time VM access policy to an array:
224-
223+
2. Insert the VM just-in-time VM access policy to an array:
224+
225225
$JitPolicyArr=@($JitPolicy)
226226

227-
3. Configure the just-in-time VM access policy on the selected VM:
228-
227+
3. Configure the just-in-time VM access policy on the selected VM:
228+
229229
Set-AzJitNetworkAccessPolicy -Kind "Basic" -Location "LOCATION" -Name "default" -ResourceGroupName "RESOURCEGROUP" -VirtualMachine $JitPolicyArr
230230

231231
### Request access to a VM via PowerShell
232232

233233
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:
234234

235235
Run the following in PowerShell:
236-
1. Configure the VM request access properties
236+
1. Configure the VM request access properties
237237

238238
$JitPolicyVm1 = (@{
239239
id="/SUBSCRIPTIONID/resourceGroups/RESOURCEGROUP/providers/Microsoft.Compute/virtualMachines/VMNAME"
240240
ports=(@{
241241
number=22;
242242
endTimeUtc="2018-09-17T17:00:00.3658798Z";
243243
allowedSourceAddressPrefix=@("IPV4ADDRESS")})})
244-
2. Insert the VM access request parameters in an array:
244+
2. Insert the VM access request parameters in an array:
245245

246246
$JitPolicyArr=@($JitPolicyVm1)
247-
3. Send the request access (use the resource ID you got in step 1)
247+
3. Send the request access (use the resource ID you got in step 1)
248248

249249
Start-AzJitNetworkAccessPolicy -ResourceId "/subscriptions/SUBSCRIPTIONID/resourceGroups/RESOURCEGROUP/providers/Microsoft.Security/locations/LOCATION/jitNetworkAccessPolicies/default" -VirtualMachine $JitPolicyArr
250250

@@ -267,6 +267,7 @@ In this article, you learned how just-in-time VM access in Security Center helps
267267

268268
To learn more about Security Center, see the following:
269269

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/)
270271
- [Setting security policies](tutorial-security-policy.md) — Learn how to configure security policies for your Azure subscriptions and resource groups.
271272
- [Managing security recommendations](security-center-recommendations.md) — Learn how recommendations help you protect your Azure resources.
272273
- [Security health monitoring](security-center-monitoring.md) — Learn how to monitor the health of your Azure resources.

articles/security-center/security-center-managing-and-responding-alerts.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,5 +68,6 @@ Security Center automatically collects, analyzes, and integrates log data from y
6868

6969
In this document, you learned how to configure security policies in Security Center. To learn more about Security Center, see the following:
7070

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/)
7172
* [Security alerts in Azure Security Center](security-center-alerts-overview.md).
7273
* [Handling security incidents](security-center-incident.md)

articles/security-center/workflow-automation.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,10 +92,11 @@ To view the raw event schemas of the security alerts or recommendations events p
9292

9393
## Next steps
9494

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.
9696

97-
For other related material, see the following articles:
97+
For other related material, see:
9898

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/)
99100
- [Security recommendations in Azure Security Center](security-center-recommendations.md)
100101
- [Security alerts in Azure Security Center](security-center-alerts-overview.md)
101102
- [About Azure Logic Apps](https://docs.microsoft.com/azure/logic-apps/logic-apps-overview)

0 commit comments

Comments
 (0)