Audit Logs for Cross-site Connections

About this Page

The Site Connections Audit Log provides a precise record of all connection-related activities, such as initiation, activation, and deactivation, between different Jira sites and environments.

What is the Use Case?

The use case is to ensure security and control over data migration and synchronization processes by tracking who establishes, verifies, and disconnects cross-site connections. This log is vital for validating that only authorized personnel manage the links between production and staging environments.

This feature is applicable to:

COMMAND CENTER FOR JIRA CONFIG MANAGER FOR JIRA ASSETS DATA MANAGER FOR JIRA

What is Audit Logs for Cross-site Connections?

Connection Events Tracked

The Event Type column records three critical state changes for a connection:

1. Site connection | Initiated: The first step where a connection attempt is registered.

2. Site connection | Activation: The moment the connection is confirmed as live and ready for data transfer.

3. Site connection | Deactivated: The deliberate action of shutting down or disconnecting a site link.

Accountability and Traceability

• Event details: This is the most crucial part for security, as it clearly lists the Source site (the origin) and the Destination site (the target). This detail is necessary for confirming that connections are only made between intended environments and not unauthorized external sites.

• Name: This identifies the individual who initiated the connection activity (e.g., Rupali Tankar, Deepak Wagmare), ensuring direct user accountability.

• Timestamp (UTC): The exact date and time the connection status changed is recorded, which is essential for auditing and incident response.

The ability to filter by event type and export the data via Download CSV enables administrators to quickly audit the security posture of their cross-site connections and meet compliance requirements.