Skip to content

Commit 590a917

Browse files
author
David Curwin
committed
fix formatting
1 parent 2aa8d95 commit 590a917

10 files changed

+14
-14
lines changed

articles/defender-for-cloud/adaptive-network-hardening.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ When necessary, you can delete a recommended rule for the current session. For e
130130

131131
To delete an adaptive network hardening rule for your current session:
132132

133-
- In the **Rules** tab, select the three dots (...) at the end of the rule's row, and select **Delete**.
133+
- In the **Rules** tab, select the three dots (...) at the end of the rule's row, and select **Delete**.
134134

135135
![Deleting a rule.](./media/adaptive-network-hardening/delete-hard-rule.png)
136136

articles/defender-for-cloud/agentless-malware-scanning.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,9 +28,9 @@ Agentless malware scanning provides:
2828

2929
Agentless malware scanning offers the following benefits to both protected and unprotected machines:
3030

31-
- **Improved coverage** - If a machine doesn't have an antivirus solution enabled, the agentless detector scans that machine to detect malicious activity.
31+
- **Improved coverage** - If a machine doesn't have an antivirus solution enabled, the agentless detector scans that machine to detect malicious activity.
3232

33-
- **Detect potential threats** - The agentless scanner scans all files and folders including any files or folders that are excluded from the agent-based antivirus scans, without having an effect on the performance of the machine.
33+
- **Detect potential threats** - The agentless scanner scans all files and folders including any files or folders that are excluded from the agent-based antivirus scans, without having an effect on the performance of the machine.
3434

3535
You can learn more about [agentless machine scanning](concept-agentless-data-collection.md) and how to [enable agentless scanning for VMs](enable-agentless-scanning-vms.md).
3636

articles/defender-for-cloud/alert-validation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ After the Microsoft Defender for Endpoint agent is installed on your machine, as
7070

7171
:::image type="content" source="media/alert-validation/powershell-no-exit.png" alt-text="Screenshot showing PowerShell message line." lightbox="media/alert-validation/powershell-no-exit.png":::
7272

73-
Alternately, you can also use the [EICAR](https://www.eicar.org/download-anti-malware-testfile/) test string to perform this test: Create a text file, paste the EICAR line, and save the file as an executable file to your machine's local drive.
73+
Alternately, you can also use the [EICAR](https://www.eicar.org/download-anti-malware-testfile/) test string to perform this test: Create a text file, paste the EICAR line, and save the file as an executable file to your machine's local drive.
7474

7575
> [!NOTE]
7676
> When reviewing test alerts for Windows, make sure that you have Defender for Endpoint running with Real-Time protection enabled. Learn how to [validate this configuration](/microsoft-365/security/defender-endpoint/configure-real-time-protection-microsoft-defender-antivirus).

articles/defender-for-cloud/concept-data-security-posture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -59,7 +59,7 @@ By applying sensitivity information types and Microsoft Purview sensitivity labe
5959

6060
Data sensitivity settings define what's considered sensitive data in your organization. Data sensitivity values in Defender for Cloud are based on:
6161

62-
- **Predefined sensitive information types**: Defender for Cloud uses the built-in sensitive information types in [Microsoft Purview](/microsoft-365/compliance/sensitive-information-type-learn-about). This ensures consistent classification across services and workloads. Some of these types are enabled by default in Defender for Cloud. You can [modify these defaults](data-sensitivity-settings.md). Of these built-in sensitive information types, there's a subset supported by sensitive data discovery. You can view a [reference list](sensitive-info-types.md) of this subset, which also lists which information types are supported by default.
62+
- **Predefined sensitive information types**: Defender for Cloud uses the built-in sensitive information types in [Microsoft Purview](/microsoft-365/compliance/sensitive-information-type-learn-about). This ensures consistent classification across services and workloads. Some of these types are enabled by default in Defender for Cloud. You can [modify these defaults](data-sensitivity-settings.md). Of these built-in sensitive information types, there's a subset supported by sensitive data discovery. You can view a [reference list](sensitive-info-types.md) of this subset, which also lists which information types are supported by default.
6363
- **Custom information types/labels**: You can optionally import custom sensitive information types and [labels](/microsoft-365/compliance/sensitivity-labels) that you defined in the Microsoft Purview compliance portal.
6464
- **Sensitive data thresholds**: In Defender for Cloud, you can set the threshold for sensitive data labels. The threshold determines minimum confidence level for a label to be marked as sensitive in Defender for Cloud. Thresholds make it easier to explore sensitive data.
6565

articles/defender-for-cloud/file-integrity-monitoring-enable-log-analytics.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -184,12 +184,12 @@ Use wildcards to simplify tracking across directories. The following rules apply
184184

185185
### Enable built-in recursive registry checks
186186

187-
The FIM registry hive defaults provide a convenient way to monitor recursive changes within common security areas. For example, an adversary might configure a script to execute in LOCAL_SYSTEM context by configuring an execution at startup or shutdown. To monitor changes of this type, enable the built-in check.
187+
The FIM registry hive defaults provide a convenient way to monitor recursive changes within common security areas. For example, an adversary might configure a script to execute in LOCAL_SYSTEM context by configuring an execution at startup or shutdown. To monitor changes of this type, enable the built-in check.
188188

189189
![Registry.](./media/file-integrity-monitoring-enable-log-analytics/baselines-registry.png)
190190

191191
>[!NOTE]
192-
> Recursive checks apply only to recommended security hives and not to custom registry paths.
192+
> Recursive checks apply only to recommended security hives and not to custom registry paths.
193193
194194
### Add a custom registry check
195195

@@ -233,7 +233,7 @@ In the example in the following figure, **Contoso Web App** resides in the D:\ d
233233
234234
### Retrieve change data
235235
236-
File Integrity Monitoring data resides within the Azure Log Analytics/ConfigurationChange table set.
236+
File Integrity Monitoring data resides within the Azure Log Analytics/ConfigurationChange table set.
237237
238238
1. Set a time range to retrieve a summary of changes by resource.
239239
@@ -258,7 +258,7 @@ File Integrity Monitoring data resides within the Azure Log Analytics/Configurat
258258
| order by Computer, RegistryKey
259259
```
260260
261-
Reports can be exported to CSV for archival and/or channeled to a Power BI report.
261+
Reports can be exported to CSV for archival and/or channeled to a Power BI report.
262262
263263
![FIM data.](./media/file-integrity-monitoring-enable-log-analytics/baselines-data.png)
264264

articles/defender-for-cloud/file-integrity-monitoring-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.date: 03/11/2024
88
---
99
# File Integrity Monitoring in Microsoft Defender for Cloud
1010

11-
File Integrity Monitoring (FIM) examines operating system files, Windows registries, application software, and Linux system files for changes that might indicate an attack.
11+
File Integrity Monitoring (FIM) examines operating system files, Windows registries, application software, and Linux system files for changes that might indicate an attack.
1212

1313
FIM (file integrity monitoring) uses the Azure Change Tracking solution to track and identify changes in your environment. When FIM is enabled, you have a **Change Tracking** resource of type **Solution**. If you remove the **Change Tracking** resource, you'll also disable the File Integrity Monitoring feature in Defender for Cloud. FIM lets you take advantage of [Change Tracking](../automation/change-tracking/overview.md) directly in Defender for Cloud. For data collection frequency details, see [Change tracking data collection details](../automation/change-tracking/overview.md#change-tracking-and-inventory-data-collection).
1414

articles/defender-for-cloud/sql-azure-vulnerability-assessment-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ Configuration modes benefits and limitations comparison:
6060
| Scan export | Azure Resource Graph | Excel format, Azure Resource Graph |
6161
| Supported Clouds | :::image type="icon" source="./media/icons/yes-icon.png"::: Commercial clouds<br>:::image type="icon" source="./media/icons/yes-icon.png"::: Azure Government<br>:::image type="icon" source="./media/icons/yes-icon.png"::: Microsoft Azure operated by 21Vianet | :::image type="icon" source="./media/icons/yes-icon.png"::: Commercial clouds<br>:::image type="icon" source="./media/icons/yes-icon.png"::: Azure Government<br>:::image type="icon" source="./media/icons/yes-icon.png"::: Azure operated by 21Vianet |
6262

63-
## Next steps
63+
## Next steps
6464

6565
- Enable [SQL vulnerability assessments](sql-azure-vulnerability-assessment-enable.md)
6666
- Express configuration [common questions](faq-defender-for-databases.yml) and [Troubleshooting](sql-azure-vulnerability-assessment-manage.md?tabs=express#troubleshooting).

articles/defender-for-cloud/troubleshooting-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Defender for Cloud uses connectors to collect monitoring data from Amazon Web Se
4242
- **GKE clusters should have Microsoft Defender's extension for Azure Arc installed**
4343
- **Azure Arc-enabled Kubernetes clusters should have the Azure Policy extension installed**
4444
- **GKE clusters should have the Azure Policy extension installed**
45-
- If you're experiencing problems with deleting the AWS or GCP connector, check if you have a lock. An error in the Azure activity log might hint at the presence of a lock.
45+
- If you're experiencing problems with deleting the AWS or GCP connector, check if you have a lock. An error in the Azure activity log might hint at the presence of a lock.
4646
- Check that workloads exist in the AWS account or GCP project.
4747

4848
### Tips for AWS connector problems

articles/defender-for-cloud/working-with-log-analytics-agent.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ To configure integration with the Log Analytics agent:
3737
> - [Where is the default Log Analytics workspace created?](./faq-data-collection-agents.yml#where-is-the-default-log-analytics-workspace-created-)
3838
> - [Can I delete the default workspaces created by Defender for Cloud?](./faq-data-collection-agents.yml#can-i-delete-the-default-workspaces-created-by-defender-for-cloud-)
3939
40-
- **Connect Azure VMs to a different workspace** - From the dropdown list, select the workspace to store collected data. The dropdown list includes all workspaces across all of your subscriptions. You can use this option to collect data from virtual machines running in different subscriptions and store it all in your selected workspace.
40+
- **Connect Azure VMs to a different workspace** - From the dropdown list, select the workspace to store collected data. The dropdown list includes all workspaces across all of your subscriptions. You can use this option to collect data from virtual machines running in different subscriptions and store it all in your selected workspace.
4141

4242
If you already have an existing Log Analytics workspace, you might want to use the same workspace (requires read and write permissions on the workspace). This option is useful if you're using a centralized workspace in your organization and want to use it for security data collection. Learn more in [Manage access to log data and workspaces in Azure Monitor](../azure-monitor/logs/manage-access.md).
4343

articles/defender-for-cloud/workload-protections-dashboard.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ Defender for Cloud includes many advanced threat protection capabilities for vir
2525

2626
## Insights
2727

28-
Insights provide you with news, suggested reading, and high priority alerts that are relevant in your environment.
28+
Insights provide you with news, suggested reading, and high priority alerts that are relevant in your environment.
2929

3030
## Next steps
3131

0 commit comments

Comments
 (0)