Skip to content

Commit f463cfc

Browse files
authored
Merge pull request #133398 from memildin/asc-melvyn-anh
Fixed a typo
2 parents 53df2af + 0243daf commit f463cfc

File tree

2 files changed

+3
-7
lines changed

2 files changed

+3
-7
lines changed

articles/security-center/overview-page.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ In the center of the page are **four central tiles**, each linking to a dedicate
3636
- **Secure score** - Security Center continually assesses your resources, subscriptions, and organization for security issues. It then aggregates all the findings into a single score so that you can tell, at a glance, your current security situation: the higher the score, the lower the identified risk level. [Learn more](secure-score-security-controls.md).
3737
- **Compliance** - Security Center provides insights into your compliance posture based on continuous assessments of your Azure environment. Security Center analyzes risk factors in your hybrid cloud environment according to security best practices. These assessments are mapped to compliance controls from a supported set of standards.[Learn more](security-center-compliance-dashboard.md).
3838
- **Azure Defender** - This is the cloud workload protection platform (CWPP) integrated within Security Center for advanced, intelligent, protection of your Azure and hybrid workloads. The tile shows the coverage of your connected resources (for the currently selected subscriptions) and the recent alerts, color-coded by severity. [Learn more](azure-defender.md).
39-
- **Inventory** - The tile shows the number of unmonitored VMs and a simple barometer of your resources monitored by Security CenterBen . [Learn more](asset-inventory.md).
39+
- **Inventory** - The tile shows the number of unmonitored VMs and a simple barometer of your resources monitored by Security Center. [Learn more](asset-inventory.md).
4040

4141

4242
The **Insights** pane offers customized items for your environment including:

articles/security-center/security-center-enable-data-collection.md

+2-6
Original file line numberDiff line numberDiff line change
@@ -138,20 +138,16 @@ When you select a workspace in which to store your data, all the workspaces acro
138138
Selecting a data collection tier in Azure Security Center will only affect the storage of security events in your Log Analytics workspace. The Log Analytics agent will still collect and analyze the security events required for Azure Security Center’s threat protection, regardless of which tier of security events you choose to store in your Log Analytics workspace (if any). Choosing to store security events in your workspace will enable investigation, search, and auditing of those events in your workspace.
139139
> [!NOTE]
140140
> Storing data in log analytics might incur additional charges for data storage. For more information, see the [pricing page](https://azure.microsoft.com/pricing/details/security-center/).
141-
>
142-
> You can choose the right filtering policy for your subscriptions and workspaces from four sets of events to be stored in your workspace:
143141
142+
You can choose the right filtering policy for your subscriptions and workspaces from four sets of events to be stored in your workspace:
144143
- **None** – Disable security event storage. This is the default setting.
145144
- **Minimal** – A smaller set of events for customers who want to minimize the event volume.
146145
- **Common** – This is a set of events that satisfies most customers and allows them a full audit trail.
147146
- **All events** – For customers who want to make sure all events are stored.
148147

148+
These security events sets are available only with Azure Defender. See [Pricing](security-center-pricing.md) to learn more about Security Center's pricing tiers.
149149

150-
> [!NOTE]
151-
> These security events sets are available only with Azure Defender. See [Pricing](security-center-pricing.md) to learn more about Security Center's pricing tiers.
152150
These sets were designed to address typical scenarios. Make sure to evaluate which one fits your needs before implementing it.
153-
>
154-
>
155151

156152
To determine the events that will belong to the **Common** and **Minimal** event sets, we worked with customers and industry standards to learn about the unfiltered frequency of each event and their usage. We used the following guidelines in this process:
157153

0 commit comments

Comments
 (0)