Physical badge access maps
Identifies substantive physical badge and door access-control maps. Topic phrases are retained for discovery; enforcement requires floor-plan, reader-to-door, security-zone, access-level, restricted-area, entry-point, zone-boundary, or credential-group relationships, and high confidence also requires populated door, reader, zone, entry, credential-group, or access-level identifiers.
- Type
- regex
- Engine
- boost_regex
- Confidence
- medium
- Confidence justification
- Medium confidence requires mapped reader, door, zone, access, or credential relationships. High confidence adds populated physical-access identifiers.
- Detection quality
- Topic false positive
- Jurisdictions
- global
- Regulations
- GDPR, AML/CTF Act (Cth), HRIPA (Cth), IPA 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), TIA Act 1979 (Cth)
- Data categories
- location, security
- Scope
- wide
- Risk rating
- 8
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported
Pattern
(?is)\b(?:physical\s+badge\s+access\s+map|badge\s+access\s+control\s+map|facility\s+badge\s+access\s+map|door\s+access\s+control\s+map|physical\s+access\s+zone\s+map)\b
Corroborative evidence keywords
physical badge access maps, physical, badge, access, maps, critical, infrastructure, systems
Proximity: 300 characters
Should match
physical badge access map— Low-tier probe - map topic without access relationshipsPhysical badge access map: floor plan maps card readers to doors, security zones, restricted areas, zone boundaries, access levels, and credential groups— Medium-tier probe - substantive access relationships without populated identifiersPhysical badge access map for North Facility: floor plan links door ID: D-104 to reader ID: CR-12 in zone ID: Z-3, access level: RESTRICTED-2, credential group: OPS— High-tier probe - mapped access relationships with populated door, reader, zone, level, and group identifiers
Should not match
unrelated generic text without domain phrases— No relevant topic phrases presentplaceholder value 12345— Random text should not match topic-specific regexbadge access zone— Generic word pair from old broad template should not matchThe physical-security policy explains how badge access levels are assigned.— Policy guidance without an access mapTraining example: physical badge access map door D-104, reader CR-12, zone Z-3, access level RESTRICTED-2— Explicit training content must not enforce
Known false positives
- Access-control policies, product documentation, and generic floor plans discuss readers, doors, zones, and badge levels without exposing a real access map. Mitigation: Keep map topics discovery-only and require floor-plan, reader-to-door, zone, access-level, restricted-area, boundary, or credential-group relationships for enforcement.
- Training maps can contain realistic reader, door, zone, credential-group, and access-level identifiers. Mitigation: Reject explicit template, demo, tutorial, sample-data, and training-example framing from enforcing tiers.
References
- https://www.legislation.gov.au/C2018A00029/latest/text
- https://www.cyber.gov.au/resources-business-and-government/essential-cyber-security/ism
- https://www.legislation.gov.au/C2004A03712/latest/text