Sprint Scope Guard — Security Overview
Sprint Scope Guard runs on Atlassian Forge for Jira Cloud. It diagnoses supported company-managed Scrum board scope and a selected user's Manage Sprints permissions. The app's Jira behavior is read-only; configuration changes and remediation remain administrator actions outside the app.
Access and permissions
Each interactive app action checks the current caller's Jira administrator permission on the server. Interactive scope evidence is read in that administrator's context. Scheduled scope evidence is read in the installed app's context. Selected-user Manage Sprints checks use the selected user's permission context. When required evidence cannot be established, the app reports INDETERMINATE rather than assuming access or healthy coverage.
The app's required scopes are:
| Scope | Purpose |
|---|---|
storage:app | Store Guard baselines, outcomes, concurrency coordination, and privacy lifecycle state in Forge storage. |
read:board-scope:jira-software | List and inspect Scrum boards and their associated projects. |
read:issue-details:jira | Required by the supported Jira board/project API permission set; SSG does not query or persist Jira issue content. |
read:board-scope.admin:jira-software | Read board configuration needed to identify the filter and validate supported scope. |
read:project:jira | Validate project IDs, keys, types, and management boundaries. |
read:jira-work | Read the saved filter and project evidence used by the bounded diagnosis. |
read:permission:jira | Check administrator access and the selected user's Manage Sprints permission; selected-user evaluation requires impersonation. |
report:personal-data | Report retained account identifiers and follow Atlassian's personal-data lifecycle. |
No Jira write scope is required. Customers do not provide passwords, Personal Access Tokens, API tokens, or shared secrets to the app.
Data protection in the app
Guard records are scoped to the Forge installation and contain the minimum account-linked baseline and outcome data described on the privacy page. The app has no external backend, Forge Remote, customer-data database outside Atlassian, or third-party app analytics destination.
Deterministic scope validation checks complete and consistent evidence. Healthy baselines initialize only from a fresh SUFFICIENT result. Missing permissions or indeterminate evidence preserve the last valid baseline. Concurrent updates and deletion are coordinated through native Forge storage locks. Corrupt records are not treated as healthy.
The privacy lifecycle tracks retained-data age, reporting cycle, and pending erasure. Account update or closure instructions remove that account's Guards and privacy metadata. Uninstall cleanup is best effort and remains subject to Atlassian's platform lifecycle. Scheduled app logging uses aggregate counts; it does not intentionally log raw account IDs or customer payloads.
Atlassian provides the underlying Forge hosting and platform controls. This app-specific overview does not claim that FrisForge has an independent security certification, penetration-test report, or Marketplace bug-bounty status.
Reporting a concern
Report an SSG security concern to [email protected], the existing FrisForge company security contact. Include the affected app/version, a description, and safe reproduction details. Do not send passwords, API tokens, or unnecessary customer data. See Support, Privacy, and Documentation.