IP Address v4
Catalogue reference for the Microsoft Purview built-in IP Address v4 sensitive information type, which detects an IPv4 address in dotted-decimal form, with IP-address keywords raising confidence. Microsoft recommends medium confidence (75) for the built-in entity. This YAML-only record lets a package recipe include the Microsoft entity explicitly; it does not reproduce Microsoft's built-in regular expressions, keyword dictionaries, checksums or XML.
- Type
- keyword_list
- Confidence
- medium
- Confidence justification
- Medium confidence for this YAML-only record: its keyword logic finds references to the built-in entity name with Microsoft Purview context, not populated values. Microsoft's own recommended confidence for the entity is 75. The record does not claim to reproduce Microsoft's proprietary detection logic.
- Jurisdictions
- global
- Regulations
- GDPR
- Frameworks
- CIS Controls, ISO 27001, NIST CSF, SOC 2
- Data categories
- network, pii
- Scope
- specific
- Risk rating
- 4
Should match
IP Address v4 built-in SIT— Microsoft built-in entity nameIPv4 Address catalogue reference— Name variant used for registry discoveryDLP policy inventory - Microsoft Purview Rule: Builtin-global-ip-address-v4 Condition: IP Address v4 (built-in entity a7dd5e5f-e7f9-4626-a2c6-86a8cb6830d2), medium confidence, instance count 1 or more Action: notify sender— DLP rule inventory row naming the built-in entity with Microsoft Purview context
Should not match
Server at 192.0.2.10— Populated value or sibling reference without the built-in entity nameNetwork diagram legend— Populated value or sibling reference without the built-in entity nameSubnet mask reference card— Populated value or sibling reference without the built-in entity name
Known false positives
- Documentation and policy inventories can mention the Microsoft built-in entity by name. Mitigation: Treat this YAML-only record as catalogue discovery; enable the Microsoft entity for value detection.
- The custom SIT global-ipv4-address detects the same data; deploying both doubles matches on the same content. Mitigation: Pick one per package. The custom SIT is the default; include this built-in only by an explicit recipe decision.