Critical-risk tools in Atlassian
5 of the 51 tools in Atlassian are classified as critical risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at critical risk
-
confluence_delete_pageDestructiveDelete a page. By default, moves to trash. Use purge option for permanent deletion.
-
jira_delete_boardDestructiveDelete a board. Warning: This is permanent and cannot be undone. All board configuration will be lost.
-
jira_delete_issueDestructiveDelete a Jira issue. This action cannot be undone unless the issue is in the trash.
-
jira_delete_sprintDestructiveDelete a sprint. Note: Can only delete sprints that have not been started (future state). Cannot delete active or closed sprints.
-
jira_remove_issue_linkDestructiveRemove/delete a link between two issues. Requires the link ID.
Attacks that target this class
Critical-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.