Skip to main content
Skip table of contents

Defining Custom Detection Rules

Security for Confluence allows you to create custom scanning rules using regular expressions. You can create and edit custom rules from the Settings page, under “Custom rules”:

localhost_1990_confluence_plugins_servlet_soteri_settings (6).png

Only Confluence administrators and any user granted explicit app access can access these settings.

Security for Confluence imposes limits on how much memory a rule can use and how long a rule can take to scan a page fragment. Scanning rules which exceed these limits will be automatically disabled, and the scan will be marked as failed.

If a secret in a single page fragment matches more than one rule (built-in or custom), only the first match will be reported.

Developing custom rules

Our application uses the built-in JDK java regex library (Java 8). The supported regex constructs are documented here.

The tool we recommend for testing out new custom rules is .

Make sure to select “Java 8” as the “Flavor”:

Example custom rules

Bitcoin Address


Youtube Links


Auditing changes to custom rules

All custom rule creation, deletion, and updates (including enabling/disabling), are logged to the Confluence Audit log. See Viewing Audited Events for more information.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.