How do you silo JIRA database/restrict view of approvers on customer ticket for HR projects

Question

Hello fellow Atlassian peoples!

We are looking to implement an HR portal that will handle personnel action requests, as such this portal will contain sensitive data so we are wondering what our options are to restrict or set up a silo database ? has anyone done so?

Any help would be greatly appreciated!

Thank you,

Rose

Nic Brough -Adaptavist- · Answer

The same applies, exactly as @Jack Brickey suggests - your administrators will always be able to get to the data.   It doesn't matter what encryption you place on it, if a system can serve it up to a user, a Jira admin can get access to it.

An encrypted database would make it very hard for the DBAs to get there, which might be good enough?  I've seen this done with Jira in a couple of places, but I'm not clear on the details of how they did it.

Rose Sahagun · Answer

Yeah :/  I was looking at the encrypted plugin as it mentioned the encryption is in the DB and file system.

We were also looking into just having HR use jira service desk in the cloud but we need to have the nfeed plugin or something similar to kick off approvals based on ADP hierarchy.

Jack Brickey · Answer

@Nic Brough -Adaptavist-, as you may recall there was a similar thread a few weeks back. Unfortunately the system admin will always have access. The only thought I had was to use encryption on attachment but that would have to be aplies outside of Jira. Moreover, this would only be for attachments so if dat in the fields were sensitive, e.g having a Salary field, that would not be encrypted.  I’m unsure if there is any suggestions posed to Atlassian to handle encrypted data w/in the application. I would be interested in knowing how this is handled by HR systems, e.g. Workday and others. I would have to imagine the system admin would still have access.

@Rose Sahagun, probably not the answer you were hoping for.