Skip to content

Commit 3f2fd80

Browse files
authored
Merge pull request #53133 from riswinto/main
updates to reduce redundancy and change level
2 parents a80fb5d + 23081fb commit 3f2fd80

7 files changed

Lines changed: 35 additions & 63 deletions

learn-pr/wwl-sci/.openpublishing.redirection.wwl-sci.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -647,6 +647,11 @@
647647
"source_path_from_root": "/learn-pr/achievements/learn.wwl.case-study-design-security-operations-identity-compliance-capabilities.badge.yml",
648648
"redirect_url": "https://learn.microsoft.com/training/modules/case-study-identity-data-security/",
649649
"redirect_document_id": false
650+
},
651+
{
652+
"source_path_from_root": "/learn-pr/wwl-sci/purview-data-security-investigations-understand/data-security-investigation-clarification.md",
653+
"redirect_url": "https://learn.microsoft.com/training/modules/purview-data-security-investigations-understand/data-security-investigation-differentiation",
654+
"redirect_document_id": false
650655
}
651656
]
652657
}

learn-pr/wwl-sci/purview-data-security-investigations-understand/data-security-investigation-clarification.yml

Lines changed: 0 additions & 15 deletions
This file was deleted.

learn-pr/wwl-sci/purview-data-security-investigations-understand/data-security-investigation-differentiation.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,6 @@ metadata:
1010
ms.topic: unit
1111
azureSandbox: false
1212
labModal: false
13-
durationInMinutes: 3
13+
durationInMinutes: 5
1414
content: |
1515
[!include[](includes/data-security-investigation-differentiation.md)]

learn-pr/wwl-sci/purview-data-security-investigations-understand/includes/data-security-investigation-clarification.md

Lines changed: 0 additions & 36 deletions
This file was deleted.

learn-pr/wwl-sci/purview-data-security-investigations-understand/includes/data-security-investigation-differentiation.md

Lines changed: 25 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
Security teams use several tools to investigate activity and assess risk. Each serves a distinct purpose. Each serves a different purpose, and understanding those differences helps determine when a data security investigation is the right choice.
1+
Security teams use several tools to investigate activity and assess risk. Each serves a distinct purpose, and understanding those differences helps determine when a data security investigation is the right choice.
22

33
Data security investigations don't replace alerts, cases, or audit. They fill a specific gap when decisions depend on understanding **data exposure and sensitivity**, not just activity.
44

5-
### Alerts focus on activity signals
5+
## Alerts focus on activity signals
66

77
Alerts are designed to surface activity that might require attention. They're effective for identifying:
88

@@ -18,7 +18,7 @@ Alerts answer questions like:
1818

1919
What alerts often don't provide is enough data context to assess risk. An alert can confirm that activity occurred without showing whether sensitive data was involved or exposed.
2020

21-
### Cases organize investigation work
21+
## Cases organize investigation work
2222

2323
Cases help group related alerts, evidence, and actions into a single investigation record. They're useful for:
2424

@@ -28,7 +28,7 @@ Cases help group related alerts, evidence, and actions into a single investigati
2828

2929
Cases improve organization, but they don't inherently add data insight. Understanding data sensitivity and exposure often still requires investigation outside the case structure.
3030

31-
### Audit provides detailed activity records
31+
## Audit provides detailed activity records
3232

3333
Audit logs capture detailed records of actions taken across services and workloads. They're valuable for:
3434

@@ -38,7 +38,7 @@ Audit logs capture detailed records of actions taken across services and workloa
3838

3939
Audit data is comprehensive, but it's activity-centric. It typically requires manual effort to correlate events with data sensitivity, scope, and risk.
4040

41-
### Where data security investigations fit
41+
## Where data security investigations fit
4242

4343
Data security investigations focus on **data context**, not just events. They bring together:
4444

@@ -52,4 +52,23 @@ This approach is most useful when:
5252
- Audit logs show behavior without clarifying data sensitivity
5353
- Decisions require validation before remediation or escalation
5454

55-
Now that you understand how data security investigations differ from alerts, cases, and audit, you can look at how investigations can be used in both reactive and proactive ways.
55+
### Use data security investigations intentionally
56+
57+
Understanding where data security investigations fit also means knowing when not to use them. A data security investigation isn't designed to replace existing security or compliance tools. It doesn't function as:
58+
59+
- An alerting system that detects suspicious activity
60+
- An incident response workflow for containment and remediation
61+
- A case management solution for legal or regulatory review
62+
- A substitute for audit logs or activity tracking
63+
64+
Those tools remain essential. Data security investigations complement them by adding data context when understanding exposure and sensitivity is critical.
65+
66+
Without clear boundaries, investigations can become inefficient or misleading. Using a data security investigation when simpler tools are sufficient can slow response time. Relying only on alerts when deeper analysis is needed can lead to decisions based on incomplete information.
67+
68+
Data security investigations are most effective when used:
69+
70+
- After activity has been identified and requires validation
71+
- When the scope or sensitivity of data is unclear
72+
- When decisions depend on confidence rather than speed alone
73+
74+
You now understand how data security investigations differ from alerts, cases, and audit. This distinction helps explain how investigations can be used in reactive and proactive ways.

learn-pr/wwl-sci/purview-data-security-investigations-understand/includes/introduction.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
Security teams investigate activity every day, but understanding **what happened to the data** is often harder than detecting the activity itself. Alerts, cases, and audit logs can show who did something and when, but they don't always answer more important questions. Was the data sensitive? How exposed was it? Did the activity create real risk, or was it expected behavior?
1+
Security teams investigate activity every day. Alerts, cases, and audit logs can show who did something and when it happened. What's often harder to determine is **what happened to the data itself**.
22

3-
Data security investigations focus on answering those questions. Instead of centering on events alone, they examine data context, sensitivity, and exposure to help teams make informed decisions about response and prevention. This approach supports both reactive investigations, where activity has already occurred, and proactive investigations, where potential risk needs validation before an incident happens.
3+
When sensitive or high-value data is involved, activity alone doesn't always provide enough information to make confident decisions. Teams might see that an action occurred without knowing whether the data was sensitive, how exposed it became, or whether the situation represents real risk. Data security investigations exist to close that gap by focusing on data context, sensitivity, and exposure.
44

5-
Understanding when and how to use data security investigations helps avoid unnecessary escalation, reduces guesswork, and ensures deeper analysis is applied only when it adds value. It also clarifies how this capability fits alongside existing security tools rather than replacing them.
5+
By understanding when and how to use data security investigations, teams can apply deeper analysis where it adds value and rely on simpler investigation paths when appropriate.
66

77
By the end of this module, you'll be able to:
88

learn-pr/wwl-sci/purview-data-security-investigations-understand/index.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ prerequisites: |
2727
2828
iconUrl: /training/achievements/generic-badge.svg
2929
levels:
30-
- beginner
30+
- intermediate
3131
roles:
3232
- administrator
3333
- risk-practitioner
@@ -41,7 +41,6 @@ units:
4141
- learn.wwl.purview-data-security-investigations-understand.introduction
4242
- learn.wwl.purview-data-security-investigations-understand.data-security-investigation-understand
4343
- learn.wwl.purview-data-security-investigations-understand.data-security-investigation-need
44-
- learn.wwl.purview-data-security-investigations-understand.data-security-investigation-clarification
4544
- learn.wwl.purview-data-security-investigations-understand.data-security-investigation-differentiation
4645
- learn.wwl.purview-data-security-investigations-understand.reactive-proactive-investigations
4746
- learn.wwl.purview-data-security-investigations-understand.deeper-investigation-value

0 commit comments

Comments
 (0)