[Legacy] Atlassian (Jira & Confluence) - Cloud

Installation & Configuration

Prerequisites

• Atlassian Cloud admin privileges

• A Dedicated Integration User with read-only access (see Dedicated Atlassian User)

• A valid API Token (see Atlassian Token Creation)

• Outbound HTTPS (TCP 443) access from SailPoint Entro to Atlassian Cloud

---

Connect to SailPoint Entro

1. Select Integration

   In the SailPoint Entro Dashboard, go to Management → Accounts & Integrations → Add New Account (top right) → Atlassian

2. Enter Connection Details

   Provide the following details:

   • Environment (e.g., Production)

   • Base URL: e.g., https://yourcompany.atlassian.net

   • Atlassian Username: user@entrosecurity.com

   • Integration User Email

   • Atlassian Token

   • Choose your connector

3. Create Account

   Click Create Account to validate access.

   ---

System Requirements

Component	Requirement
Platform	Atlassian Cloud (Jira/Confluence)
Authentication	Atlassian API Token
Network	Outbound HTTPS (443) to SailPoint Entro endpoints
Permissions	Read-only access for the integration user
File Size Limit	≤ 10 MB per file

---

Managing Findings

After the initial synchronization, detected secrets appear in the Findings Dashboard.

Each finding displays:

• Product (Jira/Confluence)

• Resource name (issue, page, repository)

• Secret type and exposure severity

• Direct URL to the affected resource

You can:

• Assign remediation to team members

• Sync or create Jira tickets for follow-up

• Mark verified false positives as Resolved

---

Security & Compliance

• All operations are read-only via Atlassian’s official APIs.

• Raw Atlassian data is never stored - only metadata and detected findings are retained.

• All traffic between SailPoint Entro and Atlassian is encrypted with HTTPS/TLS 1.2+.

• Tokens are securely encrypted and stored in SailPoint Entro’s infrastructure.

🔒 Compliance Alignment

• SOC 2 Type II

• ISO 27001

• GDPR Compliant

• Principle of Least Privilege enforced (read-only access)