Skip to content

Commit 505166a

Browse files
committed
module update
1 parent 5460b09 commit 505166a

20 files changed

Lines changed: 90 additions & 32 deletions

learn-pr/wwl-sci/create-manage-sensitive-information-types/1-introduction.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Introduction
44
metadata:
55
title: Introduction
66
description: "Introduction"
7-
ms.date: 05/26/2023
7+
ms.date: 04/15/2026
88
author: wwlpublish
99
ms.author: riswinto
1010
ms.topic: unit

learn-pr/wwl-sci/create-manage-sensitive-information-types/2-compare-built-versus-custom.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Compare built-in versus custom sensitive information types
44
metadata:
55
title: Compare built-in versus custom sensitive information types
66
description: "Compare built-in versus custom sensitive information types"
7-
ms.date: 10/04/2024
7+
ms.date: 04/15/2026
88
author: wwlpublish
99
ms.author: riswinto
1010
ms.topic: unit

learn-pr/wwl-sci/create-manage-sensitive-information-types/3-create-manage-custom.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Create and manage custom sensitive information types
44
metadata:
55
title: Create and manage custom sensitive information types
66
description: "Create and manage custom sensitive information types"
7-
ms.date: 10/04/2024
7+
ms.date: 04/15/2026
88
author: wwlpublish
99
ms.author: riswinto
1010
ms.topic: unit

learn-pr/wwl-sci/create-manage-sensitive-information-types/4-describe-custom-with-exact-data-match.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Create and manage exact data match sensitive info types
44
metadata:
55
title: Create and manage exact data match sensitive info types
66
description: "Create and manage exact data match sensitive info types."
7-
ms.date: 10/04/2024
7+
ms.date: 04/15/2026
88
author: wwlpublish
99
ms.author: riswinto
1010
ms.topic: unit

learn-pr/wwl-sci/create-manage-sensitive-information-types/5-implement-document-fingerprint.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Implement document fingerprinting
44
metadata:
55
title: Implement document fingerprinting
66
description: "Implement document fingerprinting"
7-
ms.date: 10/04/2024
7+
ms.date: 04/15/2026
88
author: wwlpublish
99
ms.author: riswinto
1010
ms.topic: unit

learn-pr/wwl-sci/create-manage-sensitive-information-types/6-create-keyword-dictionary.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Create a keyword dictionary
44
metadata:
55
title: Create a keyword dictionary
66
description: "Create a keyword dictionary"
7-
ms.date: 10/07/2024
7+
ms.date: 04/15/2026
88
author: wwlpublish
99
ms.author: riswinto
1010
ms.topic: unit

learn-pr/wwl-sci/create-manage-sensitive-information-types/7-knowledge-check.yml

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Module assessment
44
metadata:
55
title: Module assessment
66
description: "Knowledge check"
7-
ms.date: 05/26/2023
7+
ms.date: 04/15/2026
88
author: wwlpublish
99
ms.author: riswinto
1010
ms.topic: unit
@@ -47,4 +47,15 @@ quiz:
4747
explanation: "This answer isn't correct."
4848
- content: "Confidence level"
4949
isCorrect: true
50-
explanation: "This answer is correct."
50+
explanation: "This answer is correct."
51+
- content: "An organization needs to detect exact employee Social Security numbers from an HR database to prevent them from being shared externally. Which approach is most appropriate?"
52+
choices:
53+
- content: "A custom sensitive information type using a regular expression."
54+
isCorrect: false
55+
explanation: "This answer isn't correct. A regular expression matches patterns but can't match exact values from a specific database, which increases the risk of false positives."
56+
- content: "An exact data match (EDM) sensitive information type."
57+
isCorrect: true
58+
explanation: "This answer is correct. EDM-based SITs match exact values from a database of sensitive information, making them ideal for detecting specific data like employee Social Security numbers."
59+
- content: "Document fingerprinting."
60+
isCorrect: false
61+
explanation: "This answer isn't correct. Document fingerprinting detects documents based on form templates, not specific data values from a database."

learn-pr/wwl-sci/create-manage-sensitive-information-types/8-summary-resources.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Summary and resources
44
metadata:
55
title: Summary and resources
66
description: "Summary and resources"
7-
ms.date: 10/04/2024
7+
ms.date: 04/15/2026
88
author: wwlpublish
99
ms.author: riswinto
1010
ms.topic: unit

learn-pr/wwl-sci/create-manage-sensitive-information-types/describe-named-entities.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ title: Describe named entities
44
metadata:
55
title: Describe named entities
66
description: "Describe named entities"
7-
ms.date: 10/04/2024
7+
ms.date: 04/15/2026
88
author: wwlpublish
99
ms.author: riswinto
1010
ms.topic: unit

learn-pr/wwl-sci/create-manage-sensitive-information-types/includes/1-introduction.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,15 @@
11

22
Finding sensitive data between all the data produced in an organization requires different search and recognition patterns, which are called sensitive information types. In this module, you'll learn how to use sensitive information types to support your information protection strategy.
33

4-
A sensitive information type is defined by a pattern that can be identified by a regular expression or a function. In addition, corroborative evidence such as keywords and checksums can be used to identify a sensitive information type. Confidence level and proximity are also used in the evaluation process. Altogether, these elements serve as the foundation of the various policies you'll establish in Microsoft 365 to protect your information and support your data lifecycle management strategy.
4+
A sensitive information type uses a pattern, such as a regular expression or a function, to detect specific data formats. Keywords and checksums provide corroborative evidence that strengthens detection, while confidence levels and proximity further refine how matches are evaluated. Together, these elements form the foundation of the policies you establish in Microsoft 365 to protect your information and support your data lifecycle management strategy.
5+
6+
Sensitive information types are one of three classification methods available in Microsoft Purview, alongside manual classification by users and automated machine learning through trainable classifiers. Understanding how sensitive information types work gives you the foundation to build effective pattern-based detection across your environment.
57

68
## Learning objectives
79

810
Upon completion of this module, you should be able to:
911

10-
- Recognize the difference between built-in and custom sensitivity labels
12+
- Recognize the difference between built-in and custom sensitive information types
1113

1214
- Configure sensitive information types with exact data match-based classification
1315

0 commit comments

Comments
 (0)