Circuit schematics

Identifies documents containing circuit schematic or layout content in Australian contexts. Enforcement denotes actual schematic or layout artifacts (reference designators with pin/net/node/footprint relations, netlists, sheet numbers, EDA design files) — circuit-design topic language alone, i.e. the discipline of circuit design, is discovery-only. This information type is classified as personally identifiable information under applicable data protection regulations.

Type: regex
Engine: boost_regex
Confidence: medium
Confidence justification: category-aware structural regex with anchor and context constraints replaces phrase-only detection.
Detection quality: Topic false positive
Jurisdictions: global
Regulations: Anti-Money Laundering and Counter-Terrorism Financing Act 2006 (Cth), Information Privacy Act 2009 (Qld), My Health Records Act 2012 (Cth), NDB Scheme (Cth), Privacy Act 1988 (Cth), Telecommunications (Interception and Access) Act 1979 (Cth), GDPR
Frameworks: ISO 27001, ISO 27701
Data categories: intellectual-property
Scope: wide
Risk rating: 8
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Degraded, Netskope: Unsupported

Pattern

(?is)\b(?:circuit\s+schematics|circuit\s+design|schematic\s+diagram|PCB\s+layout|electronic\s+design|intellectual\s+property|proprietary\s+design|hardware\s+design|component\s+layout|board\s+schematic)\b

Corroborative evidence keywords

circuit schematics, circuit, schematics, intellectual, property, trade, secrets

Proximity: 300 characters

Should match

circuit schematics — Primary topic phrase match
circuit design — Case-insensitive topic phrase match
schematic diagram — Alternative topic phrase match
PCB layout — Additional topic phrase match
Sheet 3: U14 pin 7 connects to net VREF; R22 10k; source board.kicad_sch rev B. — Reference designators with pin/net relations plus an EDA filename prove schematic content (artifact enforcement branch)

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
Tutorial sample schematic: U1 pin 1 to NET_A. — Tutorial/sample teaching material must not enforce (single artifact token, noise-gated)
The seating layout places component teams near each other. — Layout/component words in organisational prose are not schematic content
placeholder value 12345 — Random text should not match topic-specific regex
algorithm schematic — Generic word pair from old broad template should not match

Known false positives

Common words and phrases related to circuit schematics appearing in policy documents, training materials, HR templates, or compliance guidelines without actual personal data. Mitigation: Require corroborative evidence keywords within the proximity window to confirm sensitive data context rather than general discussion.
In Australian English, similar terminology used in formal or administrative contexts (education, professional documentation) that does not constitute sensitive data collection. Mitigation: Layer with additional contextual signals such as structured identifiers, form fields, or database column headers to distinguish sensitive records from general references.
High-frequency pattern matches in large document corpora due to broad regex anchors. Expected match rate is significantly higher than specific identifier patterns. Mitigation: Tune confidence thresholds for bulk scanning. Consider using this pattern primarily as a pre-filter with secondary validation.