Trade secret inventories

Identifies trade secret inventories patterns in security and access control contexts. Detects potential exposure of sensitive security information in international systems.

Type: regex
Engine: boost_regex
Confidence: low
Confidence justification: Low confidence marker: phrase-based artifact detection to bootstrap line-by-line coverage. Requires corroborative evidence and later hardening to high-confidence structural patterns. Added context gating and exclusion rules improve precision and reduce incidental matches.
Detection quality: Mixed
Jurisdictions: global
Regulations: GDPR
Data categories: credentials, security
Scope: wide
Platform compatibility: Purview: Compatible, GCP DLP: Compatible, Macie: Compatible, Zscaler: Compatible, Palo Alto: Compatible, Netskope: Compatible

Pattern

\btrade\s+secret\s+inventories\b

Corroborative evidence keywords

trade secret inventories, trade, secret, inventories, intellectual, property, secrets, OFFICIAL, OFFICIAL:Sensitive, PROTECTED, SECRET, TOP SECRET, CABINET-IN-CONFIDENCE, NOFORN, REL TO, ORCON, National Cabinet, AUSTEO, AGAO, Sensitive: Legal (+53 more)

Proximity: 300 characters

Should match

Trade secret inventories — Exact phrase marker match
trade secret inventories — Case-insensitive phrase match
Trade secret inventories — Normalized whitespace phrase

Should not match

unrelated generic text — No relevant phrase context
placeholder value 12345 — Random text should not match phrase marker
template example placeholder record identifier — Template/sample context should be excluded even when anchor words are present

Known false positives

Authentication-related terminology in software documentation, security training materials, or system architecture descriptions without actual credentials. Mitigation: Require proximity to credential-specific patterns (API keys, connection strings, tokens) rather than general security terminology.
Code snippets and configuration examples containing credential-related keywords or placeholder values in developer documentation. Mitigation: Check for common placeholder patterns (example.com, localhost, 0000) and documentation file types to reduce false positives from technical writing.

References

https://www.ipaustralia.gov.au/tools-and-research/business-resources/non-disclosure-agreements
https://www.ipaustralia.gov.au/patents/how-to-apply-for-a-standard-patent/what-to-consider-before-applying-for-a-patent