Feature flag configurations

Name: Feature flag configurations
Creator: TestPattern Community
License: https://opensource.org/licenses/MIT

Identifies feature flag configurations patterns in security and access control contexts. Detects potential exposure of sensitive security information in Australian systems.

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: NDB Scheme (Cth), Security of Critical Infrastructure Act 2018 (Cth), Telecommunications (Interception and Access) Act 1979 (Cth), GDPR
Frameworks: CIS Controls, DISP, ISO 27001, NIST CSF, PCI-DSS, SOC 2
Data categories: credentials, 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(?:feature\s+flag|feature\s+toggle|feature\s+configuration|flag\s+management|feature\s+rollout|canary\s+release|dark\s+launch|feature\s+gate|toggle\s+configuration|release\s+flag)\b

Corroborative evidence keywords

feature flag configurations, feature, flag, configurations, software, engineering, architecture

Proximity: 300 characters

Should match

feature flag — Primary topic phrase match
feature toggle — Case-insensitive topic phrase match
feature configuration — Alternative topic phrase match
flag management — Additional topic phrase match
Feature flag Hostname: app-prd-01.corp.local username: svc_deploy Source 10.20.30.40 tcp/443 — Populated technical artefact reaching the 75/85 structure gate

Should not match

unrelated generic text without domain phrases — No relevant topic phrases present
placeholder value 12345 — Random text should not match topic-specific regex
source code config — Generic word pair from old broad template should not match
Feature flag: Hostname: username: — Empty form: the heading and field labels without values must not corroborate themselves (discovery only)
Policy guidance: this procedure explains how records about feature flag are handled, who may access them and how long they are kept. It contains no records about any person or system. — Policy guidance naming the topic without any record (discovery only)

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.