Security Policy

Overview

This Security Policy describes the secure design and operational practices for MigrationMonitor, a Jira Cloud migration monitoring app built on the Atlassian Forge platform.

Hosting and Infrastructure

MigrationMonitor is built on the Atlassian Forge platform and runs entirely within Atlassian's infrastructure. There are no external servers, databases, or third-party backends hosted by Appcento. All compute resources are provided by Atlassian as part of the Forge runtime.

Data Handling

MigrationMonitor is designed with a zero-external-storage architecture:

• Runs within Jira: All processing occurs inside your Jira Cloud instance via Atlassian Forge. No data leaves your Atlassian workspace.
• Atlassian KVS storage: Migration monitoring data is stored in Atlassian Key-Value Store (KVS), which is encrypted at rest by Atlassian. Data is only accessible within your Jira Cloud instance.
• No external storage: The App does not store any data on external servers, cloud storage, or third-party services.
• User-controlled deletion: All stored data can be cleared at any time via the "Clear History" feature. Uninstalling the App automatically deletes all stored data.

Authentication

Authentication and authorization are handled entirely by the Atlassian Forge runtime:

• Forge-managed authentication: The App has no separate login and stores no Jira credentials or API tokens. Authentication is provided by Atlassian and never leaves Atlassian's infrastructure.
• Runs as the invoking user: Jira API calls run under the identity of the user who triggered them, so Jira enforces that user's own permissions on every request. No additional accounts or passwords are required.
• Admin-only access: The App is available only to Jira administrators, enforced by the hasGlobalPermission: ADMINISTER display condition on the module.

Data Access and Permissions

The App uses Atlassian's OAuth mechanism to access Jira data. Only the minimum required API scopes are requested:

Scope	Purpose
read:jira-work	Read custom fields (/rest/api/3/field/search) and project metadata (/rest/api/3/project/search)
manage:jira-configuration	Read published workflows (/rest/api/3/workflow/search), which requires this scope
read:jira-user	Read account profiles (/rest/api/3/user/search) for the duplicate-account report
manage:jira-project	Read permission schemes (/rest/api/3/permissionscheme) and workflow-to-project associations
storage:app	Store scan snapshots in Atlassian Key-Value Store inside your Jira Cloud instance

These are the five scopes declared in the app manifest and the minimum required for it to function. The app issues read-only requests only: it creates, edits, and deletes no issues, projects, or Jira configuration.

Encryption

All encryption is handled by Atlassian's infrastructure:

• Data in transit: All communication between the App and Jira's REST API is encrypted via TLS as enforced by Atlassian's infrastructure.
• Data at rest: Data stored in Atlassian KVS is encrypted at rest by Atlassian's platform-level encryption.
• No custom encryption: The App relies on Atlassian's industry-standard encryption rather than implementing custom encryption layers.

Network Security

The App makes no network calls to external third-party services.

• All API communication is with Jira's REST API through Forge's secure runtime.
• Declared egress is limited to Atlassian-owned endpoints (api.atlassian.com and *.atlassian.net), plus *.cdn.prod.atlassian-dev.net, which loads the App's frontend assets.
• The optional change-alert feature can post to a Slack or Microsoft Teams webhook URL supplied by an administrator, validated against a provider allowlist over HTTPS. This path is disabled in the current release and no external destination is declared in the manifest, so no request leaves Atlassian infrastructure in version 2.4.0.
• The App does not use external analytics, monitoring, or telemetry services.

Vulnerability Reporting

Appcento takes security seriously. If you discover a security vulnerability in MigrationMonitor, please report it responsibly:

• Email: Send a detailed report to [email protected]
• Response time: We will acknowledge receipt within 48 hours and provide an initial assessment within 5 business days.
• Disclosure: We request that you do not publicly disclose the vulnerability until we have had a chance to address it.

Compliance

MigrationMonitor complies with the following standards and frameworks:

• Atlassian Marketplace compliance: The App has passed Atlassian's security review and listing requirements.
• GDPR: The App processes data only inside your Jira Cloud site and makes no external data transfers, so it is designed to support GDPR compliance for installed instances. Atlassian acts as processor for data held in your Jira Cloud site.
• SOC 2: Atlassian's Forge platform is SOC 2 compliant and MigrationMonitor inherits these platform-level controls. Appcento LLC does not hold an independent SOC 2 or equivalent attestation; SOC 2 status for this App derives solely from Atlassian's Forge platform.
• Atlassian Trust Center: The App inherits Atlassian's platform-level security controls and certifications. Refer to:

• Atlassian Trust Center
• Atlassian Cloud Security Practices

Incident Response

In the event of a security incident or vulnerability discovery:

• Appcento will coordinate with affected customers and Atlassian as required.
• Notifications will be sent to impacted contacts via the support email channel.
• Patches and mitigations will be applied as quickly as possible through the Forge deployment pipeline.
• For security issues, contact: [email protected]

Changes to This Policy

We may update this Security Policy from time to time. Any changes will be reflected by updating the "Effective Date" at the top of this document.

Contact

For security questions or to report a vulnerability, contact:

Email: [email protected]
Website: https://appcento.com

---