Security
This is the security policy for Delete & Append Actions for Assets in Jira, a Forge app that adds delete and append actions for Jira Service Management Assets to the Automation rule editor. It covers the first listed version and every later version published under the same app key, ua.pp.maxpetrov.assets-automation-actions.
The app is written and maintained by one person, Max Petrov. There is no second office, no subcontractor and no sub-processor: the whole of it is the Forge app you install.
The app runs entirely inside Atlassian Forge, on Atlassian's own infrastructure. Its manifest declares no permissions.external block and no remotes entry: every call is requestJira, which Forge excludes from the egress quota, so no data of yours leaves Atlassian.
There is no vendor server to breach, no vendor database to leak and no vendor log to subpoena, because none of the three exists. Authentication is Forge's own; the app holds no credential, no API token and no secret of its own, and it asks you for none.
Nothing, in this version. Forge app storage (storage:app) is declared so a later version could remember a setting without a new permission prompt; no Assets object, no attribute value and no work item content is written anywhere by this version.
Seven scopes, each the narrowest one that does the job, including three Assets scopes and one delete scope — deletion is this app's stated purpose, not an incidental grant.
read:jira-work - Resolves the work item an append-field action targets and reads field metadata (GET /rest/api/3/field) so a field name can be matched to its id.
write:jira-work - Writes the merged list of Assets objects back onto a work item's Assets field (PUT /rest/api/3/issue) when the append-field action adds one or more objects.
read:servicedesk-request - Looks up the site's Assets workspace id (GET /rest/servicedeskapi/assets/workspace) at the start of every run; every action needs it before it can call Assets at all.
read:cmdb-object:jira - Resolves objects by key or AQL and reads an object's current attributes and its type's attribute definitions (POST /object/aql) before any delete or append.
write:cmdb-object:jira - Writes the merged value list back onto an Assets attribute (PUT /object/{id}) when the append-attribute action adds one or more values.
delete:cmdb-object:jira - Deletes the Assets objects the delete action names (DELETE /object/{id}); this is the whole of that action's purpose.
storage:app - Declared now so a possible future version could remember a setting without asking your site admin for a new permission grant. This version, v1.0.0, stores no data: nothing is written to it.
Report a suspected vulnerability in this app to support@maxpetrov.pp.ua with the words SECURITY REPORT in the subject. Reports are acknowledged and triaged by the person who wrote the code.
The app runs entirely inside Atlassian Forge. Its manifest declares no permissions.external block and no remotes entry — every call is requestJira, which Forge excludes from the egress quota — so it has no internet-facing attack surface outside Atlassian.
The app collects no Atlassian credential and no API token from anybody. It authenticates through Forge's own connection to the rule, and holds no secret of its own.
Every call runs as the person who connected the rule (asUser), never as the app, so the app can only delete, add to or read an Assets object or a work item that person could already reach in Jira.
The app can delete and write Assets data and a work item's Assets field: that is its stated purpose, limited to the seven scopes it declares, and every destructive action is named in the rule's audit log with the object keys and counts it touched.
A fix for a confirmed vulnerability ships as a new Forge version; Forge apps on Atlassian cloud are upgraded by Atlassian, so there is no customer-side patch step.
Email support@maxpetrov.pp.ua with the words SECURITY REPORT in the subject. The report reaches the person who wrote the code; nobody else reads that mailbox.
One person reads that mailbox — the one who wrote the app — and every request gets a first reply within two business days, Monday to Friday. That is the window a part-time maintainer can hold every week rather than on a good one; most replies land sooner.
Please include the app version, the Jira site you saw it on and the steps to reproduce. A confirmed vulnerability ships as a new Forge version; Atlassian upgrades Forge apps on Cloud itself, so there is no patch for you to install and no action for your administrators to take.
The privacy policy covers what the app does and does not process, and the documentation page covers how to use it. Both are linked from the app's Marketplace listing.