Security
Our apps are built so that the safest option is the default one.
SpecLens: architecture
- Built on Atlassian Forge. All computing happens on Atlassian infrastructure; Klob Apps runs no servers for SpecLens.
- No external requests: the app declares no external permissions, so it cannot send data outside Atlassian.
- No storage: SpecLens does not save specifications, settings outside the macro, or usage data.
- SpecLens only reads files attached to the page where the macro is. Signed-in readers read them as themselves, so Confluence applies their own permissions; Forge may ask them once to allow access. Guests and anonymous visitors of public spaces, who cannot grant access, are served with the app's read-only permission.
- SpecLens only changes pages when someone runs the migration from another OpenAPI app on its settings screen, and it edits each page as that person, so it can only change pages they can already edit.
SpecLens: permissions and why
| Permission | Reason |
|---|---|
read:attachment:confluence | List the attachments of the current page so the editor can pick the specification. |
readonly:content.attachment:confluence | Download the selected specification to render it. |
read:content.permission:confluence | Ask Confluence whether a guest, an anonymous visitor or the person exporting can read the page before the app reads its attachment. |
search:confluence | Migration: find the pages of a space that contain macros of the other OpenAPI apps. |
read:space:confluence | Migration: list the spaces the person running it can choose from. |
read:page:confluence, read:blogpost:confluence | Migration: read those pages and blog posts, and their previous version to undo. |
write:page:confluence, write:blogpost:confluence | Migration: replace the old macros with SpecLens, as the person who runs it. |
| Content: inline styles | Required by the Swagger UI, Redoc and AsyncAPI viewers. |
| Content: runtime script evaluation | Required by the AsyncAPI parser, which compiles JSON schemas at runtime. The viewer runs in Forge's isolated frame, whose policy blocks scripts and data connections to sites outside Atlassian. |
Klob Approvals: architecture
- Built on Atlassian Forge. All computing happens on Atlassian infrastructure; Klob Apps runs no servers for Klob Approvals.
- No external requests: the app declares no external permissions.
- Approval state is kept in Forge storage, which Atlassian hosts in the same location as your Jira site. Only the app can read it.
- Before every action in the panel, the app asks Jira whether that person can browse the issue, and to request approval, whether they can transition it.
- The approval rule always comes from your Jira workflow, never from the browser.
Klob Approvals: permissions and why
| Permission | Reason |
|---|---|
read:jira-work | Read the issue, its status and its change history to evaluate approvals. |
write:jira-work | Send Jira's own notification to approvers, reporter and assignee. |
read:jira-user | Show approvers' names and check their group membership. |
read:workflow:jira | Read the approval rule configured on the issue's workflow. |
read:permission:jira | Check the person's permissions on the issue before every action. |
report:personal-data | Report weekly to Atlassian which account IDs the app stores, as Atlassian's privacy rules require, and erase the decisions of closed accounts. |
storage:app | Keep approvals and their history in Forge storage. |
Reporting a vulnerability
Write to support@klobapps.com with "Security" in the subject. We acknowledge within 48 hours and fix vulnerabilities within the timeframes of the Atlassian Marketplace security requirements.