🔐 Can I store confidential data like passwords?
👥 Can I control who has access to the stored data?
🛡️ Can that data be encrypted?
📜 Can I check who viewed/modified the password and when?
🆔 Can I perform an additional credential check before accessing the stored data?
Use Secure Fields for Jira DC: https://marketplace.atlassian.com/apps/1212681/secure-fields-data-security-privacy?hosting=datacenter&tab=overview
Companies have various IT resources with restricted and protected access. These resources can include applications, physical or virtual servers, and other IT services. Such resources include web servers, virtual and physical machines, mail servers, or network drives. Typically, secure access to these resources is managed through IAM (Identity and Access Management) systems, which centralize credential management. However, using such a centralized system in certain situations may be impossible or inefficient.
Here are three examples of such cases:
1️⃣ The System Does Not Support User Accounts
Some IT systems operate in a model with only one shared password for all users. These systems cannot be integrated with centralized identity management.
2️⃣ Immediate Access Is Required
Creating a new user account in a system can be time-consuming, especially if it requires administrator approval.
3️⃣ Emergency Access
Despite centralized access management, emergencies can arise. For example, if the only person responsible for access suddenly becomes unavailable, the company may lose control over a critical resource.
4️⃣ A Technical Account Not Linked to a Specific Person
A technical account is shared among multiple individuals, meaning different people need access to the password.
Jira can effectively manage IT resources by creating projects and issues, where each issue corresponds to a specific resource.
In this system, key information about each resource can be stored, such as:
Storing sensitive data like passwords or credentials in Jira requires proper security measures to mitigate the risk of security breaches. This is where the Secure Fields app comes in, providing secure storage for such information, restricting access to unauthorized users, monitoring access, and ensuring full auditability in compliance with best security practices.
🛡️ Data Encryption
Due to the high sensitivity of passwords, they are encrypted in the database using AES-256. This ensures that the password remains unreadable even if someone gains access to the database.
🔒 Access Permissions
Secure Fields ensures maximum security for passwords and access credentials stored in Jira. Only selected users can view stored passwords, while unauthorized individuals are denied access.
👥 Access Auditing
Every attempt to access a field—successful or not—is logged in Secure Fields' history, ensuring complete control over who attempted to decrypt the value. Additionally, users may be required to provide a reason for accessing the data.
🆔 Additional Authorization
Administrators can require extra authentication for users attempting to view or modify a field’s value. This effectively safeguards against unauthorized access, such as someone physically trying to access a Jira user’s computer.
To better illustrate how Secure Fields works, here are several screenshots depicting the process:
1️⃣ Additional Authorization – When attempting to access a field, the user must go through an additional verification step
.
2️⃣ Secure Password Field in a Jira Issue – This is how a password field securely appears within a Jira issue.
3️⃣ Access History – Every attempt to view the field’s value is logged and available only to authorized users.
4️⃣ Authorization Confirmation – The user must confirm their credentials before accessing the value.
5️⃣ Permission Schema – It shows that only users with appropriate permissions can view and edit the Secure Password field.
Secure Fields ensures that sensitive credentials stored in Jira remain protected, auditable, and accessible only to authorized users when necessary. 🚀
Jakub Kochańczyk
1 comment