The Pivotal Tracker integration enables security and compliance teams to track and verify security issues within Pivotal Tracker. It connects Drata to Pivotal Tracker so your team can demonstrate that vulnerabilities are logged, categorized, and prioritized according to your vulnerability management policies.
Key Capabilities
Security issue tracking: Monitor vulnerability-related issues within Pivotal Tracker
Severity verification: Validate that issues are categorized by severity levels
Automated evidence collection: Provide auditors with proof that security issues are tracked and managed
This integration is used to automate tests such as vulnerability tracking verification and issue remediation monitoring, helping prove compliance with vulnerability management policies.
Prerequisites & Data Access
Admin access to your organization’s Pivotal Tracker account
Access to your organization’s Pivotal Tracker labels and severity classifications
Required Drata Role with Write access: Admin, Workspace Managers, DevOps Engineer
Access Reviewers (Access Reviewers can only Read the connection page they can’t make changes)
Permissions & Data Table
Permission/Scope | Why It’s Needed |
Pivotal Tracker admin access | Allows Drata to connect and retrieve issue tracking data |
Security label | Identifies which issues represent security-related tickets |
Severity labels | Maps Pivotal Tracker severity levels to Drata’s severity categories |
Step-by-Step Setup
Step 1: Identify Your Security Label
Log in to Pivotal Tracker.
Navigate to the project or workspace where security issues are tracked.
Identify the label used to categorize security-related issues (for example,
Security).
Expected outcome: You know the label used to identify security issues in Pivotal Tracker.
Step 2: Identify Severity Labels
In Pivotal Tracker, review the labels used to categorize issue severity.
Identify the labels used for the following severity levels:
Critical
High
Medium
Low
Expected outcome: You know the labels used for each severity level.
Step 3: Connect Pivotal Tracker in Drata
Log in to Drata → go to the Connections page.
Navigate to your Available Connections.
Search for and start the Pivotal Tracker connection process.
Enter the required values when prompted:
Security Label – the label used for security issues
Critical Severity Label
High Severity Label
Medium Severity Label
Low Severity Label
Expected outcome:
Pivotal Tracker is successfully connected and issue tracking data begins syncing to Drata.
Important Notes
This integration is used to verify that security vulnerabilities are tracked and prioritized according to your organization’s vulnerability management policies.
If you do not use Security as the label for security-related tickets in Pivotal Tracker, update the Security Label field during setup.
Severity labels must match the labels configured in Pivotal Tracker for issues to be correctly categorized by Drata.
If labels are renamed or removed in Pivotal Tracker, the integration may not correctly categorize issues.