6 posts tagged with "security"

The Atlassian Marketplace has thousands of apps, and installing the wrong one can expose your Jira and Confluence data to a vendor you have never vetted. The good news is that Atlassian surfaces most of what you need to make a safe decision directly on each listing — if you know where to look. This guide is a practical checklist for evaluating any Marketplace app before it lands on your site, written for the admins who get asked "is this app okay to install?" and need to answer with confidence.

Installing a Marketplace app in an enterprise Atlassian environment is not the same as installing a browser extension. The app gains access to your Jira issues, Confluence pages, and potentially your entire collaboration surface — so the evaluation process needs to be rigorous. This guide covers the ten criteria that security, procurement, and IT teams should check before approving any app for enterprise deployment.

Audit logs are the paper trail of your Jira instance. They record who did what, when, and where — essential information for compliance audits, security investigations, and change management.

Without proper audit logging, you cannot prove who deleted that issue, when permissions changed, or whether someone accessed restricted data. This guide covers how to access, export, and analyze Jira audit logs.

Permissions in Jira control who can do what. Without proper configuration, either everyone can see everything (security risk) or the permissions are so locked down that work stops (productivity risk).

The key is finding the balance: enough access for people to do their jobs, not so much that sensitive data is exposed. This guide covers how to configure Jira permissions without breaking workflows.