New Zealand Marking - IN-CONFIDENCE
Detects the New Zealand Government IN-CONFIDENCE protective marking under the Protective Security Requirements (PSR) classification system: endorsed forms (e.g. MEDICAL IN-CONFIDENCE, BUDGET: IN-CONFIDENCE), the legacy SEEMail bracket trigger-word convention ([IN-CONFIDENCE]), and the bare ALL-CAPS document-banner form. Regex logic verified against the official PSR Classification Handbook (protectivesecurity.govt.nz) and Cabinet Office Circular CO(08)1; matched case-sensitively.
- Type
- regex
- Engine
- boost_regex
- Confidence
- high
- Confidence justification
- High confidence on the endorsed and legacy-bracket forms: both are case-sensitive, structured markings with low natural-English collision risk. The bare IN-CONFIDENCE banner (75) is a distinctive hyphenated compound absent from ordinary prose, but is one tier lower and gated by a template/noise NOT-exclusion since it lacks the endorsement/bracket's structural signal.
- Jurisdictions
- nz
- Regulations
- Privacy Act 2020 (NZ)
- Frameworks
- PSR
- Data categories
- government, security
- Scope
- narrow
- Risk rating
- 6
- Platform compatibility
- Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Unsupported
Pattern
\b(?:POLICY|MEDICAL|STAFF|EVALUATIVE|COMMERCIAL|APPOINTMENTS|HONOURS|BUDGET)(?:\s+|:\s*)IN-CONFIDENCE\b|\[IN-CONFIDENCE\]Corroborative evidence keywords
New Zealand, PSR, Protective Security Requirements, Cabinet
Proximity: 300 characters
Should match
This memo is marked MEDICAL IN-CONFIDENCE and must not be forwarded outside HR.— Endorsed form, space-separated — matches the PSR Classification Handbook's own worked example (MEDICAL IN-CONFIDENCE)Cabinet paper: BUDGET:IN-CONFIDENCE — do not distribute before the Budget announcement.— Endorsed form, colon-separated — matches the Cabinet Office Circular CO(08)1 convention (e.g. "Commercial: In Confidence")The attached briefing is classified BUDGET IN-CONFIDENCE pending Cabinet sign-off.— PDF-wrapped endorsed form — line wrap inserts a newline between the endorsement and the classification wordSubject: [IN-CONFIDENCE] Draft policy paper for review— Legacy SEEMail bracket trigger-word formIN-CONFIDENCE Ministry of Business, Innovation and Employment — briefing for the Minister— Bare document-banner form (PSR Classification Handbook document-marking convention — centred, bold, ALL CAPS)
Should not match
Please keep this in confidence between us until the announcement.— lowercase English idiom (case-sensitive exclusion)IN-CONFIDENCE (template) — replace this sample paragraph with your own content— bare banner tier excluded by the template/noise NOT-group (documentation/sample content)STAFF IN CONFIDENCE handling applies to this personnel file— non-hyphenated "IN CONFIDENCE" (two words) is a known coverage gap — canonical PSR guidance renders the classification as the single hyphenated token IN-CONFIDENCE
Known false positives
- ALL-CAPS prose (legal boilerplate, headers, or documents rendered entirely in capitals) defeats the case-sensitivity signal the bare IN-CONFIDENCE banner tier relies on. Mitigation: Treat banner-tier-only (75) hits as lower confidence when the surrounding text is itself all-caps; the endorsed and legacy-bracket tiers (85) remain the reliable signal.
- The SEEMail square-bracket trigger-word convention ([IN-CONFIDENCE]) is being decommissioned during 2026 as the Secure Government Email (SGE) Framework replaces SEEMail. It retains legacy detection value for circulated documents and email archives but is not the durable long-term signal. Mitigation: Weight the bracket tier (85) as a transitional/legacy indicator; the endorsed and bare-banner tiers reflect the current PSR Classification Handbook convention and are expected to remain valid after SEEMail's decommissioning.
- The non-hyphenated form "IN CONFIDENCE" (two words, no hyphen) is not matched — canonical PSR guidance renders it as the single hyphenated token "IN-CONFIDENCE", but some agency drafting may omit the hyphen. Mitigation: No mitigation implemented; documented as a known coverage gap for a future revision.