ProbePilot for Jira security

Reporting a problem

Report a suspected vulnerability to contact@probeflow.net. Include what you found and how to reproduce it. Please do not test against other people’s Jira sites.

How it is built

  • Hosting. ProbePilot is built entirely on Atlassian Forge. It declares no remote servers and no external network permissions.
  • Tenant isolation. Each installation has its own Forge storage. The code has no cross-tenant queries.
  • Identity and authorization. Identity comes from Forge and is checked against Jira. Authorization is decided on the server for each request, using Jira permissions as the acting user. The browser is treated as untrusted.
  • Input handling. Inputs are validated with schemas, and database statements use bound parameters only.
  • Least privilege. The app asks for five scopes, each explained on the permissions and scopes page.
  • CI endpoint. The one inbound web trigger needs a per-source token, stored only as a hash, and accepts bounded requests.
  • Audit. Changes are written to an audit log that records the acting account ID, the action and the entity, and is kept for 365 days. Application logs contain no personal data or request payloads.
  • Dependencies. The lockfile is frozen and dependencies are audited in continuous integration.