Secure Fields for JIRA
Page tree
Skip to end of metadata
  • Created by Unknown User (robert.dzido@infodesign.pl), last modified by Inga on Jun 29, 2020
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 30 Next »

When storing sensitive data such as passwords or license keys, the main concern is to ensure its proper protection.
Secure Password Custom Field enables you to store private information behind a secure mask and prevent unauthorized access to it.

Secure Password Configuration

Secure Password Field uses the Advanced Encryption Standard with a 256-bit key.
You can set your own Encryption key to ensure the highest protection and prevent your secure data from being accessed by the system administrator.
If the Encryption key is not specified, the system will use the default one (will be generated from your Jira instance server key).

You can add one Encryption key for all Password fields or set specific keys for each one.
To set custom key you need to add a special property to the properties file.

Adding property for all Password fields:
com.coresoftlabs.secureFields.global.password.secret
com.coresoftlabs.secureFields.global.password.secretFilePath

Adding property for a specific Password field:
com.coresoftlabs.secureFields.{FIELD_ID}.password.secret
com.coresoftlabs.secureFields.{FIELD_ID}.password.secretFilePath
Example: com.coresoftlabs.secureFields.customfield_10201.password.secretFilePath=c:/test.txt

Manage apps → Secure fields → Secure Password Settings

Extra authentication

Protect the sensitive information that you keep by enforcing extra authentication every time the user is trying to access it.

Issues → Fields → Custom fields → Edit Password field authentication configuration

Extra authentication enabled - a user will be prompted to authorize before accessing the Secure Password Field. If authorization fails, none of the options (show/edit/copy the value) are available. A user will get an error message.

Permissions

Define who can access the field, decrypt, change or copy its value.

Issues → Fields → Custom fields permission schemes

Users with only View field permission can see the Password field on issue screen.  
The value of the field is shown encrypted and cannot be unmasked or edited by the current user.

If a user with Edit field value permission clicks on (blue star), the Overwrite value button appears. It enables the user to enter new data into the Password field.
The current value will be not shown as the user does not have permission to decrypt the field.

After clicking on (blue star)and successful authorization (if Extra authentication enabled), users with Decrypt field value permission get the next options:

  • Show value - data will be decrypted and the field value is shown:

  • Edit value - data will be decrypted and the field value is available for editing:

  • Copy to clipboard - allows the user to copy the field value to the clipboard.

History

Know if and when someone accessed sensitive data.

Every attempt to decrypt, edit, or copy the value of the Password field is recorded in the field's history. Furthermore, unsuccessful attempts are stored as well. In order to view the history of the field, a user needs to have the respective permission - View field history.

Depending on the Search mode you set, Password Field searching will be limited or disabled.

Performance mode - a user is only able to check the field's last modification date.

Strict mode - Secure Password Field is not searchable.

  • No labels