Security Practices
Project Overview & Status Hub for Jira is designed as an Atlassian Forge app for Jira Cloud, with permission-aware access and human review of generated project context.
Jira Cloud and Atlassian Forge. No Jira Data Center, Connect or separate vendor-hosted product backend is used for project overview content.
Generated overviews, settings and access policies are stored in Atlassian Forge app storage for the Jira site.
The app relies on Jira authentication, Jira permissions, global app permissions and section-level access rules.
Architecture
The app uses Forge Custom UI, Forge resolvers, Forge app storage, Forge permissions and Atlassian-hosted Forge LLM capabilities. The app does not require Forge Remote and does not store project overview content in a vendor-managed database outside Atlassian Forge.
Authentication and authorization
- Users access the app through Jira Cloud and Atlassian authentication.
- The app relies on Atlassian Forge context and Jira permissions for user and site context.
- Jira global permissions control who can use the app, view portfolio information and manage portfolio generation.
- Project-level editing checks are enforced in the backend resolver, not only in the browser.
- Section access rules can restrict sensitive overview sections inside a saved project overview.
Least privilege scopes
- read:jira-work - to read Jira project and issue work data needed for overviews, status calculations, links, dates and risk signals.
- read:jira-user - to show people, ownership, project roles and last-updated-by information.
- read:license:jira - to check license-related information used by the app experience and usage limits.
- storage:app - to store generated overviews, settings, access policies, refresh state and temporary generation records in Forge app storage.
External egress
The app manifest allows backend fetch egress to Google Analytics for product analytics. The manifest marks this egress as analytics and not in scope for Atlassian End User Data. Product analytics payloads are sanitized and restricted to an allowlist of event names and simple parameters.
AI processing
AI-assisted text is generated through Atlassian-hosted Forge LLM capabilities. The app does not call a vendor-hosted AI provider. AI output is shown as a suggestion or summary and should be reviewed by users.
Logging
Logs should avoid personally identifiable information, credentials, Jira issue text, saved overview text and sensitive customer content. Analytics debug logging, if enabled for troubleshooting, logs compact sanitized analytics payload information only.
Vulnerability reporting
Security issues can be reported to Mederak Apps Service Desk. Please include reproduction steps, impact, affected tenant context and screenshots where appropriate. Do not include secrets, credentials or unnecessary customer data.
Incident response
Security incidents are handled according to the Security Incident Response page.