Zenthas

Card Wall: Security

Version 3.0.0, 11 November 2026.

Architecture

A Forge app for Jira Cloud with a Custom UI built with Atlaskit. It has a global page, entries in the board, backlog, issue and search-result menus, a resolver, and a trigger that sends a Forge Realtime signal without issue data when issues change. The PDF is created in the browser of the person using the app. There is no database of our own.

Data and egress

The manifest declares no remotes and no external egress, and the app calls no external services. Jira is accessed only as the calling user. Templates and the export history (last 20 exports, without issue content) are stored in Forge app storage of the customer's site. After a print the app writes a print mark as an issue property, if the person may edit the issue. Zenthas has no access to this data.

Permissions

read:jira-work: read issues and fields.
read:jira-user: show the assignee.
read:board-scope:jira-software and read:board-scope.admin:jira-software: read boards and their configuration.
read:sprint:jira-software: sprints of a board.
read:project:jira: project list for templates.
write:jira-work: the print mark (issue property kartenwand.print).
storage:app: templates and export history.
report:personal-data: reports the Atlassian account IDs the app stores, as required by the Personal Data Reporting API.

Controls

Cards contain only issues the person creating them may see, because Jira calls run with asUser. JQL is limited to 5000 characters and validated by Jira. Keys, names and extra fields are checked against whitelists and length limits in the resolver. Text in the preview and the PDF is escaped, and an uploaded logo is re-encoded in the browser. Automated unit tests cover the logic.

Known limits

There has been no external penetration test. Printed cards can contain personal and confidential data and are the responsibility of the customer.

Report a vulnerability

Write to support@zenthas.com. Fixes ship as new app versions through Atlassian Marketplace.