Skip to content

Commit 193a774

Browse files
authored
Clarify terminology in vulnerability management document
Updated terminology from 'weaknesses' to 'previously known as weaknesses' for clarity.
1 parent eba70eb commit 193a774

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

exposure-management/vulnerability-management-integration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ The integration provides comprehensive vulnerability context by combining device
3838
The following Vulnerability Management experiences reside within Exposure Management:
3939

4040
- **Overview dashboard**: Refocused on vulnerabilities only, with a new layout
41-
- **Vulnerabilities (weaknesses)**: Includes side-by-side Devices and Cloud views
41+
- **Vulnerabilities (previously known as weaknesses)**: Includes side-by-side Devices and Cloud views
4242
- **Remediation workflows**: Integrated remediation processes
4343
- **Inventories and baseline assessment**: Complete asset and security baseline visibility
4444
- **Event timeline**: Accessible via the events widget in both recommendations page and MDVM overview dashboard
@@ -52,7 +52,7 @@ The following Vulnerability Management experiences reside within Exposure Manage
5252

5353
### Prerequisites for access
5454

55-
- **Licensing**: MDVM features require appropriate Microsoft Defender licensing (Defender for Endpoint P1/P2)
55+
- **Licensing**: MDVM features require appropriate Microsoft Defender licensing (Defender for Endpoint P1)
5656
- **Permissions**: Use established MDVM permissions or the new unified Exposure Management RBAC roles
5757
- **Cloud integration**: For full cloud vulnerability visibility, Defender for Cloud licensing is recommended
5858

0 commit comments

Comments
 (0)