Heartbeats for JSM: security policy
Last updated: November 16, 2026
This policy describes how Zeustable (“we”), the developer of Heartbeats for Jira Service Management (“Heartbeats”), protects customer data, handles security issues and incidents, and manages vulnerabilities. For what data the app handles and why, see the privacy policy.
1. Scope and architecture
Heartbeats is an Atlassian Forge app. All of its code runs on Atlassian's Forge platform, and all of its data is stored in Forge storage on Atlassian's infrastructure. We do not run any servers, databases or other infrastructure that receive or store customer data.
- Inbound: job check-ins (“pings”) arrive through a Forge web trigger. The app reads only the heartbeat ID and the secret token; the request body is ignored and nothing else from the request is stored.
- Outbound: the app's only permitted egress is
https://api.atlassian.com, declared in the app manifest and enforced by Forge. It is used to open and close alerts in the customer's own Jira Service Management site. - Permissions: the app requests a single Atlassian scope,
storage:app. It has no permission to read Jira issues, users or other site content.
2. Technical and organizational controls
Access control and least privilege
- The app requests only the minimum scope it needs (
storage:app) and only one external egress domain. - The Heartbeats settings page is a Jira admin page, shown only to Jira administrators. Every server-side action also checks for an authenticated Atlassian user before it runs.
- We, the developer, have no access to customer data stored in Forge storage, including heartbeat definitions, ping tokens and integration keys. Forge storage is isolated per installation.
- Access to the developer accounts that can deploy the app (Atlassian developer account and source code repository) is limited to the developer. We use strong, unique credentials for these accounts, never share them, and review who has access at least quarterly.
Data protection and encryption
- All traffic to and from the app uses HTTPS (TLS), provided by the Forge platform for web triggers and by Atlassian for api.atlassian.com.
- Data at rest is held in Atlassian Forge storage, which Atlassian encrypts at rest. The Jira Service Management integration key is stored with Forge's secret storage API and is never sent back to the browser after it is saved.
- Each heartbeat has its own random 192-bit ping token generated with a cryptographically secure random number generator. The token is sent in a request header, never in the URL, so it does not end up in proxy or server logs. Tokens are compared in constant time, and admins can regenerate a token at any time.
- The heartbeat list returned to the admin page never includes tokens; a token is fetched only when an admin opens that heartbeat's setup dialog.
- Data stays in the data residency region of the customer's Atlassian site.
Platform isolation
- Each Forge function runs in Atlassian's sandboxed Forge runtime. Each customer installation has its own isolated storage, so one customer's data cannot be read by another installation.
- Customer data never leaves Atlassian infrastructure; there is no developer-hosted backend.
Monitoring and logging
- We monitor the app's health through the Forge developer console (invocation errors and metrics). The app does not write customer data, tokens or keys to logs.
- Errors that affect a customer (for example a rejected integration key) are shown to that customer's admins on the Heartbeats settings page.
- The app uses no analytics, tracking or third-party scripts.
Secure development
- Source code is kept in a private repository. Automated unit tests run on every deployment, and a deployment stops if they fail.
- Dependencies are kept to a minimum (Atlassian's Forge packages and React) and are reviewed and updated for security advisories.
- Input from admins and from pings is validated before it is stored.
- Secrets are never committed to source code.
3. Vulnerability management
How to report a vulnerability
Email support@norynta.com with the subject “Security report: Heartbeats”. Please include a description of the issue, steps to reproduce, the affected component and its potential impact. Please do not access or change other customers' data, and give us reasonable time to fix the issue before disclosing it publicly. We will not take action against good-faith research that follows this policy. Vulnerabilities can also be reported through Atlassian's Marketplace security programs.
Triage and fix timelines
We acknowledge reports within 2 business days and confirm or rule out the issue within 5 business days. We rate confirmed issues by severity (using CVSS) and aim to fix them within these timelines:
- Critical: within 7 days
- High: within 28 days
- Medium: within 56 days
- Low: within 175 days
Forge platform updates and security advisories from Atlassian are applied as soon as they are released. We keep the reporter informed until the fix is deployed. Because Forge apps update automatically, fixes reach all customers without any action on their part (unless a fix needs new permissions, which customers must approve).
4. Security issue and incident handling
Identification
Security issues are identified through reports from customers and researchers, Atlassian notifications and advisories, dependency advisories, and errors seen in the Forge developer console.
Response
- Assess: confirm the issue, determine which customers and data are affected, and rate its severity.
- Contain: stop the exposure, for example by deploying a fix, disabling the affected function or rotating credentials. Customers can also rotate ping tokens and their integration key from the settings page.
- Fix and recover: deploy the fix to all installations and verify it works.
- Review: record the cause and the steps taken, and change processes to prevent a repeat.
Communication to customers
If an incident affects customer data, we notify affected customers and Atlassian without undue delay, and in any case within 72 hours of confirming it. The notice explains what happened, what data was affected, what we have done and any steps customers should take. We use the contact details of the site admins available to us through Atlassian and update customers until the incident is closed.
5. Contact
Security reports and questions: support@norynta.com. See also the privacy policy and the app overview.