Security
Architecture
A Forge app for Jira Cloud with a Custom UI built with Atlaskit and a resolver. There is no server or database of our own.
Data and egress
The manifest declares no remotes and no external egress. Jira is called only as the signed-in user, so Jira permissions apply. Drafts, baselines, saved views and the change journal are stored in Forge app storage of the customer's site; they contain Atlassian account IDs and issue keys with dates. The app does not log End-User Data. Zenthas has no access to this data.
Permissions
read:jira-work: read issues, fields and links.write:jira-work: write dates after you press Apply, and undo.read:jira-user: show people (assignee, owner of saved views).storage:app: drafts, baselines, saved views, journal.
Controls
Every resolver checks that the user may browse the project; the resolvers that write also require an active licence. Automated unit tests cover the logic. There has been no external penetration test.
Report a vulnerability
Write to support@zenthas.com. Fixes ship as new app versions.