Skip to content

Commit b0ef58b

Browse files
committed
CAP Updates
1 parent 13f5a94 commit b0ef58b

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

exposure-management/classify-critical-assets.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -83,13 +83,13 @@ Create a custom classification as follows:
8383

8484
1. On the **Create a critical asset classification** page, complete the following information to set your classification criteria:
8585

86-
- **Name** - A new classification name.
87-
- **Description** - A new classification description.
88-
- **Query builder**
89-
- Use the query builder to define a new classification, for instance, "mark all devices with a certain naming convention as critical."
90-
- Add one or more Boolean filters that are defined per device, identity, or cloud resource.
86+
- **Name** - A new classification name.
87+
- **Description** - A new classification description.
88+
- **Query builder**
89+
- Use the query builder to define a new classification, for instance, "mark all devices with a certain naming convention as critical."
90+
- Add one or more Boolean filters that are defined per device, identity, or cloud resource.
9191

92-
:::image type="content" source="./media/classify-critical-assets/create-critical-asset-classification.png" alt-text="Screenshot of the page where you create critical asset classifications.":::
92+
:::image type="content" source="./media/classify-critical-assets/create-critical-asset-classification.png" alt-text="Screenshot of the page where you create critical asset classifications.":::
9393

9494
1. After setting the criteria, select **Next**.
9595
1. On the following pages, preview the affected assets, and assign the criticality level.
@@ -157,4 +157,3 @@ To see the sum of exposed critical assets go to the [Security recommendations](/
157157
## Next steps
158158

159159
Learn about simulating [attack paths](work-attack-paths-overview.md).
160-

0 commit comments

Comments
 (0)