Skip to content

Commit 95128f9

Browse files
authored
Merge pull request #270337 from dcurwin/fix-formatting-march27-2024
fix formatting
2 parents 627756a + 8acc6a2 commit 95128f9

9 files changed

+43
-42
lines changed

articles/defender-for-cloud/faq-general.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -165,7 +165,7 @@ sections:
165165
- The Azure Management app ID (797f4846-ba00-4fd7-ba43-dac1f8f63013), or all apps, are included in the **Apps** section of your MFA CA policy
166166
- The Azure Management app ID isn't excluded in the **Apps** section of your MFA CA policy
167167
- OR condition is used with only MFA, or AND condition is used with MFA
168-
- A Conditional Access policy enforcing MFA through [Authentication Strengths](https://learn.microsoft.com/entra/identity/authentication/concept-authentication-strengths) is currently not supported in our evaluation
168+
- A Conditional Access policy enforcing MFA through [Authentication Strengths](/entra/identity/authentication/concept-authentication-strengths) is currently not supported in our evaluation.
169169
170170
- question: |
171171
We're using a third-party MFA tool to enforce MFA. Why do we still get the Defender for Cloud recommendations?

articles/defender-for-cloud/how-to-manage-cloud-security-explorer.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,12 +62,12 @@ The cloud security explorer allows you to build queries that can proactively hun
6262

6363
:::image type="content" source="media/concept-cloud-map/cloud-security-explorer-main-page.png" alt-text="Screenshot of the cloud security explorer page." lightbox="media/concept-cloud-map/cloud-security-explorer-main-page.png":::
6464

65-
1. Search for and select a resource from the drop-down menu.
65+
1. Search for and select a resource from the drop-down menu.
6666

6767
:::image type="content" source="media/how-to-manage-cloud-security/cloud-security-explorer-select-resource.png" alt-text="Screenshot of the resource drop-down menu." lightbox="media/how-to-manage-cloud-security/cloud-security-explorer-select-resource.png":::
6868

6969
1. Select **+** to add other filters to your query.
70-
70+
7171
:::image type="content" source="media/how-to-manage-cloud-security/cloud-security-explorer-query-search.png" alt-text="Screenshot that shows a full query and where to select on the screen to perform the search." lightbox="media/how-to-manage-cloud-security/cloud-security-explorer-query-search.png":::
7272

7373
1. Add subfilters as needed.

articles/defender-for-cloud/how-to-transition-to-built-in.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.date: 01/09/2024
1010
# Transition to Microsoft Defender Vulnerability Management for servers
1111

1212
> [!IMPORTANT]
13-
> Defender for Server's vulnerability assessment solution powered by Qualys, is on a retirement path that is set to complete on **May 1st, 2024**. If you are a currently using the built-in vulnerability assessment powered by Qualys, you should plan to transition to the Microsoft Defender Vulnerability Management vulnerability scanning using the steps on this page.
13+
> Defender for Server's vulnerability assessment solution powered by Qualys, is on a retirement path that is set to complete on **May 1st, 2024**. If you are a currently using the built-in vulnerability assessment powered by Qualys, you should plan to transition to the Microsoft Defender Vulnerability Management vulnerability scanning using the steps on this page.
1414
>
1515
> For more information about our decision to unify our vulnerability assessment offering with Microsoft Defender Vulnerability Management, see [this blog post](https://techcommunity.microsoft.com/t5/microsoft-defender-for-cloud/defender-for-cloud-unified-vulnerability-assessment-powered-by/ba-p/3990112).
1616
>
@@ -26,13 +26,13 @@ To transition to the integrated Defender Vulnerability Management solution, you
2626
- [Transition with Defender for Cloud’s portal](#transition-with-defender-for-clouds-portal)
2727
- [Transition with REST API](#transition-with-rest-api)
2828

29-
## Transition with Azure policy (for Azure VMs)
29+
## Transition with Azure policy (for Azure VMs)
3030

3131
1. Sign in to the [Azure portal](https://portal.azure.com/).
3232

3333
1. Navigate to **Policy** > **Definitions**.
3434

35-
1. Search for `Setup subscriptions to transition to an alternative vulnerability assessment solution`.
35+
1. Search for `Setup subscriptions to transition to an alternative vulnerability assessment solution`.
3636

3737
1. Select **Assign**.
3838

@@ -41,18 +41,18 @@ To transition to the integrated Defender Vulnerability Management solution, you
4141
1. Select **Review + create**.
4242

4343
1. Review the information you entered and select **Create**.
44-
44+
4545
This policy ensures that all Virtual Machines (VM) within a selected subscription are safeguarded with the built-in Defender Vulnerability Management solution.
4646

4747
Once you complete the transition to the Defender Vulnerability Management solution, you need to [Remove the old vulnerability assessment solution](#remove-the-old-vulnerability-assessment-solution)
4848

49-
## Transition with Defender for Cloud’s portal
49+
## Transition with Defender for Cloud’s portal
5050

51-
In the Defender for Cloud portal, you have the ability to change the vulnerability assessment solution to the built-in Defender Vulnerability Management solution.
51+
In the Defender for Cloud portal, you have the ability to change the vulnerability assessment solution to the built-in Defender Vulnerability Management solution.
5252

5353
1. Sign in to the [Azure portal](https://portal.azure.com/).
5454

55-
1. Navigate to **Microsoft Defender for Cloud** > **Environment settings**
55+
1. Navigate to **Microsoft Defender for Cloud** > **Environment settings**
5656

5757
1. Select the relevant subscription.
5858

@@ -68,7 +68,7 @@ In the Defender for Cloud portal, you have the ability to change the vulnerabili
6868

6969
1. Select **Microsoft Defender Vulnerability Management**.
7070

71-
1. Select **Apply**.
71+
1. Select **Apply**.
7272

7373
1. Ensure that `Endpoint protection` or `Agentless scanning for machines` are toggled to **On**.
7474

articles/defender-for-cloud/implement-security-recommendations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ In addition to risk level, we recommend that you prioritize the security control
5858

5959
## Use the Fix option
6060

61-
To simplify remediation and improve your environment's security (and increase your secure score), many recommendations include a **Fix** option to help you quickly remediate a recommendation on multiple resources. If the Fix button isn't present in the recommendation, then there's no option to apply a quick fix.
61+
To simplify remediation and improve your environment's security (and increase your secure score), many recommendations include a **Fix** option to help you quickly remediate a recommendation on multiple resources. If the Fix button isn't present in the recommendation, then there's no option to apply a quick fix.
6262

6363
**To remediate a recommendation with the Fix button**:
6464

articles/defender-for-cloud/investigate-resource-health.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,7 @@ This single page, currently in preview, in Defender for Cloud's portal pages sho
2121
In this tutorial you'll learn how to:
2222

2323
> [!div class="checklist"]
24+
>
2425
> - Access the resource health page for all resource types
2526
> - Evaluate the outstanding security issues for a resource
2627
> - Improve the security posture for the resource

articles/defender-for-cloud/just-in-time-access-usage.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ In this article, you learn how to include JIT in your security program, includin
3838

3939
| To enable a user to: | Permissions to set|
4040
| --- | --- |
41-
|Configure or edit a JIT policy for a VM | *Assign these actions to the role:* <ul><li>On the scope of a subscription (or resource group when using API or PowerShell only) that is associated with the VM:<br/> `Microsoft.Security/locations/jitNetworkAccessPolicies/write` </li><li> On the scope of a subscription (or resource group when using API or PowerShell only) of VM: <br/>`Microsoft.Compute/virtualMachines/write`</li></ul> |
41+
|Configure or edit a JIT policy for a VM | *Assign these actions to the role:* <ul><li>On the scope of a subscription (or resource group when using API or PowerShell only) that is associated with the VM:<br/> `Microsoft.Security/locations/jitNetworkAccessPolicies/write` </li><li> On the scope of a subscription (or resource group when using API or PowerShell only) of VM: <br/>`Microsoft.Compute/virtualMachines/write`</li></ul> |
4242
|Request JIT access to a VM | *Assign these actions to the user:* <ul><li> `Microsoft.Security/locations/jitNetworkAccessPolicies/initiate/action` </li><li> `Microsoft.Security/locations/jitNetworkAccessPolicies/*/read` </li><li> `Microsoft.Compute/virtualMachines/read` </li><li> `Microsoft.Network/networkInterfaces/*/read` </li> <li> `Microsoft.Network/publicIPAddresses/read` </li></ul> |
4343
|Read JIT policies| *Assign these actions to the user:* <ul><li>`Microsoft.Security/locations/jitNetworkAccessPolicies/read`</li><li>`Microsoft.Security/locations/jitNetworkAccessPolicies/initiate/action`</li><li>`Microsoft.Security/policies/read`</li><li>`Microsoft.Security/pricings/read`</li><li>`Microsoft.Compute/virtualMachines/read`</li><li>`Microsoft.Network/*/read`</li>|
4444

@@ -48,7 +48,7 @@ In this article, you learn how to include JIT in your security program, includin
4848
- To set up JIT on your Amazon Web Service (AWS) VM, you need to [connect your AWS account](quickstart-onboard-aws.md) to Microsoft Defender for Cloud.
4949

5050
> [!TIP]
51-
> 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 Defender for Cloud GitHub community pages.
51+
> 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 Defender for Cloud GitHub community pages.
5252
5353
> [!NOTE]
5454
> In order to successfully create a custom JIT policy, the policy name, together with the targeted VM name, must not exceed a total of 56 characters.
@@ -60,15 +60,15 @@ You can use Defender for Cloud or you can programmatically enable JIT VM access
6060
**Just-in-time VM access** shows your VMs grouped into:
6161

6262
- **Configured** - VMs configured to support just-in-time VM access, and shows:
63-
- the number of approved JIT requests in the last seven days
64-
- the last access date and time
65-
- the connection details configured
66-
- the last user
63+
- the number of approved JIT requests in the last seven days
64+
- the last access date and time
65+
- the connection details configured
66+
- the last user
6767
- **Not configured** - VMs without JIT enabled, but that can support JIT. We recommend that you enable JIT for these VMs.
6868
- **Unsupported** - VMs that don't support JIT because:
69-
- Missing network security group (NSG) or Azure Firewall - JIT requires an NSG to be configured or a Firewall configuration (or both)
70-
- Classic VM - JIT supports VMs that are deployed through Azure Resource Manager. [Learn more about classic vs Azure Resource Manager deployment models](../azure-resource-manager/management/deployment-models.md).
71-
- Other - The JIT solution is disabled in the security policy of the subscription or the resource group.
69+
- Missing network security group (NSG) or Azure Firewall - JIT requires an NSG to be configured or a Firewall configuration (or both)
70+
- Classic VM - JIT supports VMs that are deployed through Azure Resource Manager. [Learn more about classic vs Azure Resource Manager deployment models](../azure-resource-manager/management/deployment-models.md).
71+
- Other - The JIT solution is disabled in the security policy of the subscription or the resource group.
7272

7373
### Enable JIT on your VMs from Microsoft Defender for Cloud
7474

articles/defender-for-cloud/multicloud-resource-types-support-foundational-cspm.md

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -11,17 +11,17 @@ ms.date: 02/29/2024
1111

1212
## Resource types supported in AWS
1313

14-
| Provider Namespace | Resource Type Name |
14+
| Provider Namespace | Resource Type Name |
1515
|----|----|
1616
| AccessAnalyzer | AnalyzerSummary |
17-
| ApiGateway | Stage |
17+
| ApiGateway | Stage |
1818
| AppSync | GraphqlApi |
1919
| ApplicationAutoScaling | ScalableTarget |
2020
| AutoScaling | AutoScalingGroup |
2121
| AWS | Account |
2222
| AWS | AccountInRegion |
2323
| CertificateManager | CertificateTags |
24-
| CertificateManager | CertificateDetail |
24+
| CertificateManager | CertificateDetail |
2525
| CertificateManager | CertificateSummary |
2626
| CloudFormation | StackSummary |
2727
| CloudFormation | StackTemplate |
@@ -40,10 +40,10 @@ ms.date: 02/29/2024
4040
| CloudWatchLogs | LogGroup |
4141
| CloudWatchLogs | MetricFilter |
4242
| CodeBuild | Project |
43-
| CodeBuild | ProjectName |
43+
| CodeBuild | ProjectName |
4444
| CodeBuild | SourceCredentialsInfo |
4545
| ConfigService | ConfigurationRecorder |
46-
| ConfigService | ConfigurationRecorderStatus |
46+
| ConfigService | ConfigurationRecorderStatus |
4747
| ConfigService | DeliveryChannel |
4848
| DAX | Cluster |
4949
| DAX | ClusterTags |
@@ -62,20 +62,20 @@ ms.date: 02/29/2024
6262
| EC2 | AccountAttribute |
6363
| EC2 | Address |
6464
| EC2 | CreateVolumePermission |
65-
| EC2 | EbsEncryptionByDefault |
65+
| EC2 | EbsEncryptionByDefault |
6666
| EC2 | FlowLog |
6767
| EC2 | Image |
6868
| EC2 | InstanceStatus |
6969
| EC2 | InstanceTypeInfo |
7070
| EC2 | NetworkAcl |
7171
| EC2 | NetworkInterface |
72-
| EC2 | Region |
72+
| EC2 | Region |
7373
| EC2 | Reservation |
7474
| EC2 | RouteTable |
7575
| EC2 | SecurityGroup |
7676
| ECR | Image |
7777
| ECR | Repository |
78-
| ECR | RepositoryPolicy |
78+
| ECR | RepositoryPolicy |
7979
| ECS | TaskDefinition |
8080
| ECS | ServiceArn |
8181
| ECS | Service |
@@ -121,7 +121,7 @@ ms.date: 02/29/2024
121121
| Iam | ManagedPolicy |
122122
| Iam | ManagedPolicy |
123123
| Iam | AccessKeyLastUsed |
124-
| Iam | AccessKeyMetadata |
124+
| Iam | AccessKeyMetadata |
125125
| Iam | PolicyVersion |
126126
| Iam | PolicyVersion |
127127
| Internal | Iam_EntitiesForPolicy |
@@ -133,7 +133,7 @@ ms.date: 02/29/2024
133133
| KMS | KeyPolicy |
134134
| KMS | KeyMetadata |
135135
| KMS | KeyListEntry |
136-
| KMS| AliasListEntry |
136+
| KMS| AliasListEntry |
137137
| Lambda | FunctionCodeLocation |
138138
| Lambda | FunctionConfiguration|
139139
| Lambda | FunctionPolicy |
@@ -156,9 +156,9 @@ ms.date: 02/29/2024
156156
| RDS | DBClusterSnapshotAttributesResult |
157157
| RedShift | LoggingStatus |
158158
| RedShift | Parameter |
159-
| Redshift | Cluster |
159+
| Redshift | Cluster |
160160
| Route53 | HostedZone |
161-
| Route53 | ResourceRecordSet |
161+
| Route53 | ResourceRecordSet |
162162
| Route53Domains | DomainSummary |
163163
| S3 | S3Region |
164164
| S3 | S3BucketTags |
@@ -169,7 +169,7 @@ ms.date: 02/29/2024
169169
| S3 | BucketVersioning |
170170
| S3 | LifecycleConfiguration |
171171
| S3 | PolicyStatus |
172-
| S3 | ReplicationConfiguration |
172+
| S3 | ReplicationConfiguration |
173173
| S3 | S3AccessControlList |
174174
| S3 | S3BucketLoggingConfig |
175175
| S3Control | PublicAccessBlockConfiguration |
@@ -178,12 +178,12 @@ ms.date: 02/29/2024
178178
| SNS | TopicAttributes |
179179
| SNS | TopicTags |
180180
| SQS | Queue |
181-
| SQS | QueueAttributes |
181+
| SQS | QueueAttributes |
182182
| SQS | QueueTags |
183183
| SageMaker | NotebookInstanceSummary |
184184
| SageMaker | DescribeNotebookInstanceTags |
185185
| SageMaker | DescribeNotebookInstanceResponse |
186-
| SecretsManager | SecretResourcePolicy |
186+
| SecretsManager | SecretResourcePolicy |
187187
| SecretsManager | SecretListEntry |
188188
| SecretsManager | DescribeSecretResponse |
189189
| SimpleSystemsManagement | ParameterMetadata |
@@ -198,8 +198,8 @@ ms.date: 02/29/2024
198198

199199
## Resource types supported in GCP
200200

201-
| Provider Namespace | Resource Type Name |
202-
|----|----|
201+
| Provider Namespace | Resource Type Name |
202+
|----|----|
203203
| ApiKeys | Key |
204204
| ArtifactRegistry | Image |
205205
| ArtifactRegistry | Repository |

0 commit comments

Comments
 (0)