Security for Jira Data Center Documentation
Add extra security to your Jira workflow. Scan issues for leaked passwords, private keys, cloud credentials, etc.
-
Overview
-
Built-In Scanning Rules
-
Security Analysis: Viewing scan results for a project | Security for Jira (DC)
-
The Soteri Dashboard: Viewing Jira's overall security status
-
Granting Access to Additional Users and Groups
-
Hiding false positives, revoked credentials, etc.
-
Exporting Findings
-
Enabling and Disabling Scanning Rules
-
Viewing Audited Events
-
Defining Custom Detection Rules
-
Automatically Scanning New and Updated Projects
-
Scanning Files Attached to Issues
-
REST API For Scripting and Automation
- What can Security for Jira Scan?
- What do I do if a security scan finds a secret?
- How do I make sure all projects are scanned, remain scanned, and remain secret-free?
- Accessing the Settings Page
- What is the GENERIC_PASSWORD rule and why is it disabled by default?
- Why are some scanning rules disabled by default?
- Why isn't Security for Jira finding my passwords?
- Scan Performance
- Enabling debug logging
- Creating support zips
- Why are newline matchers not allowed in custom rules?
Security for Jira Data Center Documentation