Revyz Data Manager for Jira Capabilities

Capability

Revyz Data Manager for Jira

Information Security & Compliance

Encryption

Data is Encrypted in-motion and at-rest

In-Motion | TLS 1.2

At-Rest | AES 256 bit key, AES-GCM mode, HKDF-512 bit key derivation and commitment, ECDSA with P-384 and SHA-384

More information here - https://support.revyz.io/legal-security/revyz-security-compliance-overview

Qualys SSL Labs

A+ https://www.ssllabs.com/ssltest/analyze.html?d=jira-app.revyz.io

SOC 2

Revyz is a SOC2 Type 2 compliant organization check out our Trust Center for more information - https://trust.revyz.io

ISO 27001

Revyz is a SOC2 Type 2 certified - ISO 27001 certification is driven by customer needs and it is currently gathering interest!

Personal Information Treatment

Revyz does not access a customers personal information directly and neither does it process that information. Any information that is present in Jira that was added in by the customer is pulled into the Revyz data store for backup puroposes and the information is encrypted - in-motion and at rest - learn more about our encryption methodology here - https://support.revyz.io/legal-security/revyz-security-compliance-overview

Immutable App Audit Logs

The Revyz App maintains a detailed access log of administrators accessing the Revyz app as well as maintaining any actions taken with the app including app setting changes, data restores etc..

Role Based Access Control

The Revyz App utilizes Atlassian native roles based access control scheme

Data Residency

🌐 Data Residency options: AWS US East 🇺🇸 Frankfurt 🇩🇪 Sydney 🇦🇺 Canada Central 🇨🇦 Singapore 🇸🇬

Reference data residency support - https://support.revyz.io/legal-security/data-residency

Immutable, air-gapped backups 

Support

Support Operations time & process

We have customers across the globe - hence we offer 24x5 support during weekdays, we are just a zoom call away!

The Revyz team operates out of 3 countries:

• United States of America 🇺🇸

• India 🇮🇳

• New Zealand 🇳🇿

To request a call at anytime reach out to our support desk here - https://revyz.atlassian.net/servicedesk/customer/portal/1 someone will respond to schedule a zoom meeting if need be

Phone Support

Data Protection (Backup & Restore)

Easy setup

Native to Atlassian App installation process - you never have to go outside of your Jira console

Automatic daily backups

Cloud Storage

Please reference our Fair Use Policy, for most Jira and Confluence objects there is no limit.

On-Demand backups

3 Years of backup data retention

On-demand restores

Granular/item-level restores

Attachment backups

Detailed backup analytics and logs

Supported items

As Supported by Atlassian API's - See detailed list below

Cross site data restore support

Maintain parent child relationships when restoring your issue data

Access to original timestamps of restored Jira Issues

Backup & Restore support for JSM Assets

Restore Use Cases Supported

Couple of points to note from the above:

• Most frequent disasters are driven by Human Error | Reference https://securityboulevard.com/2022/09/dude-wheres-my-data-how-data-is-lost-in-the-cloud/

• Malicious deletion of data occurs very frequently but is un-reported as it is typically not know or not reported for reputational reasons

With the above in mind who is responsible for data loss in SaaS for the various scenarios?

The answer depends on the cause of data destruction - simple rule of thumb, if the data loss is due to infrastructure failure / non-availability of infra then it is the SaaS vendor on the other hand if the data destruction is due to a data breach or human error on the customer side then it is the customer who is responsible for the data.

References

• Atlassian Shared Responsibility Model: https://www.atlassian.com/whitepapers/cloud-security-shared-responsibilities

• Atlassian Security Practices: https://www.atlassian.com/trust/security/security-practices#physical-security

  • “We do not use these backups to revert customer-initiated destructive changes, such as fields overwritten using scripts, or deleted issues, projects, or sites. To avoid data loss, we recommend making regular backups.”

Granular & Bulk Recovery of Issues and related data such as attachments

Bulk Recovery of configuration objects

Project level recovery

Cross site data & configuration restore

Site level recovery of data (issues + configuration)

Multiple steps to recover:

• Recover configuration

• Recover Projects & Issues

We are working on a simplified way to recover entire site data with just a few clicks - awaiting release of specific backup & restore related API’s from Atlassian

Alternate console for accessing backup data

The Revyz Data Manager User Interface is embedded within Atlassian’s Jira console - We do not support a separate console outside of the Jira console at this point of time.

Configuration Management

Configuration Rollback

Configuration Diff

Sandbox to Production (Cross-site) Data Transfer

Jira Site Analytics

Issue Deletion Log

A very critical feature - Enables the admin to understand who is deleting what and when

Jira Site Summary

Attachment Analytics

Jira Site Optimization

Configuration Usage Analysis

Bulk Configuration Deletion

Accidental config deletion prevention

Check to see if a config object is present in your backup before deleting

Log of all deletion actions

Additional Features

Detailed Error Logging

Notifications via Jira Project integration (Email / Slack / Teams)

Selective Data Export (JSON / CSV)

Bulk Data Export (JSON / CSV / Parquet)

Roadmap

Free plan

We do not offer a free plan at this point of time, although we offer a free trial which ranges between 30 - 59 days and is extendable on a case by case basis

Jira Object Support

Projects

Backup

Restore

Comments

Projects

Project categories

Project components

Project features

Only for Software projects.

JSM is not supported due to API limitations

Project versions

Filters

Dashboard

Roadmap

Roadmap

Gathering Interest

Project properties

Backup runtime consideration

Project property keys

Backup runtime consideration

Project avatars

Backup runtime consideration

Issues

Backup

Restore

Comments

Issue attachments

Issue comments

Issue votes

API Limitation

Backup runtime consideration

Issue watchers

Backup runtime consideration

Issue worklogs

Configuration Objects

Backup

Restore

Comments

Issue types (Epics, Story etc)

Sub tasks

Issue type screen schemes

Issue link types

Boards

Sprints

Workflows

Workflow schemes

Workflow scheme drafts

Workflow schemes project associations

Workflow transition properties

Screens

Screen schemes

Issue type screen schemes

Screen tabs

Screen tab fields

System Fields

System fields cannot be overwritten

Custom fields

Field configurations

Field configuration Scheme

Issue attributes and features

Backup

Restore

Comments

Status(s)

Resolutions

Priorities

Issue security schemes

Notification schemes

Permission schemes

Priority schemes

Roadmap

Roadmap

Issue linking

Issue properties

Backup runtime consideration

Issue property keys

Backup runtime consideration

Issue remote links

Roadmap

Roadmap

Gathering Interest

Security

Backup

Restore

Comments

Project roles

Permission types

Types are created by default

Groups

Jira Service Management

Backup

Restore

Comments

Service Desks (as Projects)

Requests (as Issues)

Request Type

Request Type / Portal Groups

Portal groups - Roadmap

Form Templates

Service Desk Queues

Roadmap

Roadmap

Gathering Interest

Organization

Roadmap

Roadmap

Gathering Interest

Customers

Roadmap

Roadmap

Gathering Interest

Assets

Backup

Restore

Comments

Assets Object Schema

Assets Object Types

Assets Object Type Attributes

Assets Object Schema Statuses

Inbound and Outbound references in Jira Assets

Limited to certain scenarios

Linked issues in Jira Assets

Limited to certain scenarios

Assets Object Schema Reference types

Assets Object Schema Roles

API Limitations

Internal Assets Custom Field

API Limitations

Assets Objects Attachments

API Limitations

External Assets Custom Field

API Limitations

Additional

Backup

Restore

Comments

Automation Rules

Restore is manual at this point of time, we would love your feedback

Advance Roadmap

Roadmap

Roadmap

Gathering Interest

Third party app data is not backed-up as that data is not available in Atlassian Cloud. Our app is dependent on the API’s that are published by Atlassian. Thus far no other third-party app vendor has been open to providing a mechanism for backing & restoring up third party app data that is stored in their own cloud.