Atlassian tools like Jira and Confluence are well known for their flexibility and customization. When most software developers prefer this flexibility over closed systems, the regulated industries may often fear that this flexibility could affect their compliance. There are aspects that you will have to consider when setting your organization up on Atlassian stack when you are in a regulated domain.
We have broken it down to 3 areas that you must consider when setting your organization up on Atlassian stack when you are working in a regulated domain.
I ARE WE DOING THNIGS IN THE RIGHT WAY?
The first thing to consider is how to set up your organization’s processes in Jira and Confluence. Every organization works differently but regulations require each company to have well defined processes in the form of SOPs (Standard Operating Procedures). It’s crucial that you get most out of your tools by configuring them in a way that supports your existing processes. Read more here.
II WHO CAN SEE WHAT?
The second aspect of configuration consideration in the regulated domains is securing your data so only the authorized users can see them. It is expected that you have procedures that define, at a high level, the different access levels to each tool. Read more here.
III WHERE IS MY DATA?
Last but not least, you should consider data residency. Data residency is about the location in which your data is being stored. It is an important aspect when choosing a cloud operator for the regulated domains. GDPR (EU) requires processing and storing of personal data to be within the EU. Read more about Atlassian data storage here.
For full article, please continue reading here.