Skip to end of banner
Go to start of banner

Security Statement

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

September 3, 2016

1. Overview

IssueSYNC for JIRA Cloud uses the IssueSYNC hosted service (cloud.issuesync.com ) to store imported JIRA data and render IssueSYNC data. IssueSYNChosted service is provided by Amazon Web Services (AWS).

Each IssueSYNC customers data is stored in a IssueSYNC database. Each incoming web request is authenticated and authorized before access to customer data is allowed.

IssueSYNC hosted service is using AWS components. InTENSO is responsible for provisioning, monitoring, and managing the virtual servers, and for providing support to IssueSYNC for JIRA Cloud subscribers. 

2. Data Storage and Facilities

IssueSYNC hosted service uses AWS components and infrastructure for data storage. 

3. Stored JIRA data

IssueSYNC for JIRA Cloud uses JIRA issues REST APIs to query data from selected projects.

IssueSYNC stores, in its own database, configuration and messages that contains field values and comments based on configured synchronization contracts;

4. People and Access

InTENSO support and monitoring teams access application data only for purposes of application health monitoring and performing system or application maintenance, and upon customer request for support purposes.

Only authorized InTENSO employees and consultants have access to application data.

IssueSYNC users are authenticated using Atlassian Connect JWT authentication.

IssueSYNC will get JIRA Cloud current user information which will be used for access control.

Customers are responsible for maintaining the security of their own JIRA Cloud login information.

5. Backups

IssueSYNC application database full backups are performed once per day and are retained for 30 days.

  • No labels