Zenthas

Security: Component Tree for Jira

Version 21 October 2026.

Architecture

The app runs on Atlassian Forge. There is no server, database or external API run by the vendor. Data lies in the Forge storage of the customer's Jira site.

Permissions

  • Changing the tree or any component requires the Jira permission "Administer projects" for that project, or Jira administrator. The backend checks this on every change.
  • Changes to components run as the signed-in user, so Jira's own checks apply as well.
  • Reads (components, issue counts, JQL results) run as the app.
  • Scopes: read:jira-work, read:jira-user, manage:jira-project, read:app-data:jira, write:app-data:jira, storage:app.

Data

Only component IDs, parent links and a change history (with the account ID and display name of the person who made the change) are stored. No issue content, no e-mail addresses.

Network

The app calls no external hosts. No analytics, no third parties.

Incident response

We keep a written incident response plan: receive and log, assess, contain with a fixed version, notify affected customers and Atlassian without undue delay, recover and review. The full plan is below. Before each release, npm audit for production dependencies shows no high or critical findings.

Reporting a vulnerability

Write to security@zenthas.com. Please give details and allow reasonable time for a fix before you disclose. We reply to security reports as quickly as we can, without a fixed deadline.

Incident response plan

Version 22 October 2026. Owner: Zenthas, security@zenthas.com.

Scope

This plan covers security incidents in the app Component Tree for Jira: a vulnerability in the app code or its dependencies, unwanted access to app data, or a faulty release that exposes data. The app runs on Atlassian Forge and stores data only in the Forge storage of the customer's Jira site. We run no server, so we hold no copy of customer data.

Reporting

  • Anyone can report to security@zenthas.com. Customers can also use support@zenthas.com.
  • Reports from Atlassian (Marketplace Security, Bug Bounty, Forge platform notices) reach the same mailbox.
  • We confirm receipt and keep the reporter informed.

Steps

  1. Receive and log. Note date, reporter, affected version and what is known. One person owns the incident (the vendor).
  2. Assess. Decide the severity: does it expose data, allow changes without permission, or only affect availability? Check which sites and versions can be affected.
  3. Contain. Fix in code, or switch the affected function off. Release a fixed version through Forge. Forge apps update on the customer's site through Atlassian. If a permission scope has to change, customers must approve the new scope, and we tell them.
  4. Notify. Without undue delay we tell affected customers by e-mail and by a note on the support page. We inform Atlassian through the Marketplace partner channel. Where the law requires a report to a data protection authority, the customer as controller decides and we support with the facts. We state what happened, what data was involved, what we did and what the customer should do.
  5. Recover. Verify the fix on a test site. Check the Forge function logs for signs of misuse.
  6. Review. Write a short post-incident note: cause, fix, and what we change so it does not repeat. Update the dependency check and tests.

Prevention

  • npm audit for production dependencies without high or critical findings before every release.
  • Permission check in the backend for every change, minimal Jira scopes, input validation.
  • No external hosts and no third-party processors called by the app.

Contacts

  • Security reports: security@zenthas.com
  • Privacy requests: privacy@zenthas.com
  • Support: support@zenthas.com