Skip to content

Commit 13e3de5

Browse files
committed
Merge branch 'master' of https://github.com/microsoftdocs/azure-docs-pr into asc-melvyn-release-notes
2 parents f722d2a + 13ac0b5 commit 13e3de5

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/security-center/deploy-vulnerability-assessment-vm.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -122,9 +122,9 @@ The vulnerability scanner extension works as follows:
122122
>[!IMPORTANT]
123123
> If the deployment fails on one or more machines, ensure the target machines can communicate with Qualys' cloud service by adding the following IPs to your allow lists (via port 443 - the default for HTTPS):
124124
>
125-
> - https://qagpublic.qg3.apps.qualys.com - Qualys' US data center
125+
> - `https://qagpublic.qg3.apps.qualys.com` - Qualys' US data center
126126
>
127-
> - https://qagpublic.qg2.apps.qualys.eu - Qualys' European data center
127+
> - `https://qagpublic.qg2.apps.qualys.eu` - Qualys' European data center
128128
>
129129
> If your machine is in a European Azure region, its artifacts will be processed in Qualys' European data center. Artifacts for virtual machines located elsewhere are sent to the US data center.
130130
@@ -168,8 +168,8 @@ The Azure Security Center vulnerability assessment extension (powered by Qualys)
168168

169169
During setup, Security Center checks to ensure that the machine can communicate with the following two Qualys data centers (via port 443 - the default for HTTPS):
170170

171-
- https://qagpublic.qg3.apps.qualys.com - Qualys' US data center
172-
- https://qagpublic.qg2.apps.qualys.eu - Qualys' European data center
171+
- `https://qagpublic.qg3.apps.qualys.com` - Qualys' US data center
172+
- `https://qagpublic.qg2.apps.qualys.eu` - Qualys' European data center
173173

174174
The extension doesn't currently accept any proxy configuration details.
175175

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ JIT requires [Azure Defender for servers](defender-for-servers-introduction.md)
7070
If you want to create custom roles that can work with JIT, you'll need the details from the table below.
7171

7272
> [!TIP]
73-
> To create a least-privileged role for users that need to request JIT access to a VM, and perform no other JIT operations, use the [Set-JitLeastPrivilegedRole script](https://github.com/Azure/Azure-Security-Center/tree/master/Powershell%20scripts/JIT%20Custom%20Role) from the Security Center GitHub community pages.
73+
> To create a least-privileged role for users that need to request JIT access to a VM, and perform no other JIT operations, use the [Set-JitLeastPrivilegedRole script](https://github.com/Azure/Azure-Security-Center/tree/main/Powershell%20scripts/JIT%20Scripts/JIT%20Custom%20Role) from the Security Center GitHub community pages.
7474
7575
| To enable a user to: | Permissions to set|
7676
| --- | --- |
@@ -88,4 +88,4 @@ If you want to create custom roles that can work with JIT, you'll need the detai
8888
This page explained _why_ just-in-time (JIT) virtual machine (VM) access should be used. To learn about _how_ to enable JIT and request access to your JIT-enabled VMs, see the following:
8989

9090
> [!div class="nextstepaction"]
91-
> [How to secure your management ports with JIT](security-center-just-in-time.md)
91+
> [How to secure your management ports with JIT](security-center-just-in-time.md)

0 commit comments

Comments
 (0)