Encryption for Jira logo white Encryption for Jira

Encryption for Jira is the leading Jira app for protecting sensitive data in Jira.

Jira’s out-of-the-box permissions will protect your information from unwanted access on the front end. However, in the backend file systems and databases, your data could easily be exposed and abused.

Using Encryption for Jira you can ensure this data is securely encrypted making it significantly more difficult for unwanted users to access.


  • Encryption for Jira gives you peace of mind that you have taken the necessary steps to secure your Jira data.
  • Help protect your organisation against (internal and external) data breaches and their associated negative reputational and financial consequences.
  • Secure your Jira data and become more compliant with data protection policies, regulations, and laws.
  • Save time by easily encrypting your data with only a few clicks.
  • Encryption for Jira is fully supported and Jira Service Desk Compatible.

Choose what you encrypt

Using AES (Advanced Encryption Standard) encryption technology, you can encrypt the following Jira information:

Encrypt project attachments

Attachments, such as PDFs, images or text files, associated with Jira projects often contain sensitive client, personal or organisational information. If your file system is exposed as a result of a hacking attack or similar incident, any information stored in these attachments could easily be copied and misused. Encrypting these attachments will protect your Jira data by making this information illegible to anyone who does not have the key to decrypt them.

Project level flexibility

Have the flexibility to select which projects’ attachments are encrypted (rather than encrypting all attachments at once), or encrypt all at once if needed.

Encrypt text data

The encrypted Custom Field function in Encryption for Jira enables you to secure particular sections of sensitive text data.

Key management

Administrators can decide on where they store their encryption keys (passwords). The level of security and method of storage can all be easily managed from the Configuration window.

Common use cases:

  • Organisations such as healthcare companies, are able to protect sensitive patient information in their Jira system by encrypting it in their databases and file systems.

  • Protecting information in the database and/or file system helps protect this organisation from:
    • Hacking attacks - if unwanted users break through your firewall they will not be able to read your encrypted sensitive information
    • Unwanted admin access - certain database/file system admins will have access to all company data. There may be more junior admins or even external/outsourced admins who you would not wish to have access to this data. E4J allows you to restrict access to only those with the encryption key.
  • A Human Resources Jira instance may contain sensitive salary details stored in a text field. Use Encryption for Jira’s Encrypted Custom Field to secure this information in the database.

  • If you only need to protect certain projects, you can encrypt attachments at a project level only. Perhaps when storing information related to a client who has requested you sign a Non-Disclosure Agreement (NDA).