Security
How the Jira app is built
- Runs on Atlassian. The app is built on Atlassian Forge and runs entirely on Atlassian's infrastructure. We operate no servers of our own, and the app sends no data to any external host.
- Read-only, least privilege. It requests only the scopes it needs: reading Jira work and users, and Forge storage for each user's own settings (their team list and saved views). It never creates, changes or deletes issues or worklogs.
- Jira permissions are respected. Every Jira request is made as the signed-in user, so people see only the worklogs they can already see in Jira.
- No secrets, no credentials. The app never asks for passwords or API tokens and stores no secrets.
- Input validation. Filters are validated by Jira before use; all output is escaped by the UI framework.
- No sensitive logging. The app does not log personal data, tokens or credentials.
Development practices
- Source code is kept in a private repository; accounts used for development and publishing are protected with multi-factor authentication.
- Third-party dependencies are checked for known vulnerabilities (npm audit) before every release and updated when an advisory affects them.
- Automated tests run before every release; each release is checked on a test Jira site before it reaches production.
- We follow the OWASP Top 10 guidance relevant to Forge apps.
Vulnerability handling
Report a suspected vulnerability to support@appaq.dev with "Security" in the subject. We acknowledge reports within 2 business days. We fix vulnerabilities within the Atlassian Marketplace Security Bug Fix Policy timeframes for cloud apps — critical within 10 days, high within 4 weeks, medium within 12 weeks and low within 25 weeks — and tell affected customers when a fix needs action on their side.
Incident response
- Detect and assess — confirm the incident, its scope and the data that may be affected.
- Notify — notify Atlassian through an app security incident ticket in the Atlassian ecosystem support portal promptly and no later than 24 hours, and keep it updated.
- Contain and fix — disable the affected feature or roll back the release, fix the cause and deploy the fix.
- Inform customers — tell affected customers what happened, the likely impact and any steps they need to take.
- Review — record what happened and what we changed so it does not happen again.
Contact
Security contact: support@appaq.dev · Appaq Labs, Kazakhstan