<aside>
ℹ️
Consolidates the Marketplace-facing security architecture statement (SFD-2) and the repository's vulnerability disclosure policy, formerly a separate SECURITY.md (SFD-16).
</aside>
Last updated: 2026-09-22
Contact: [email protected]
This statement describes the security architecture of Smart Field Defaults, a Jira Cloud app built entirely on the Atlassian Forge platform. For data retention specifics, see ‣.
Platform
Smart Field Defaults runs entirely inside Atlassian's Forge infrastructure. Workflowly operates no independent servers, databases, or hosting of its own — there is nothing outside Atlassian for an attacker to target, because there is nothing outside Atlassian at all. The app inherits Forge's platform-level security controls, including Atlassian's SOC 2 Type II and ISO 27001 coverage for the infrastructure the app runs on.
Authentication and authorization
- The app authenticates to Jira's REST API using Forge's built-in app identity (
api.asApp()), a managed OAuth 2.0 credential issued and rotated by Atlassian. The app never handles, stores, or has visibility into user passwords or long-lived API tokens.
- Requests run with the minimum Forge scopes declared in
manifest.yml: read:jira-work, write:jira-work, read:jira-user, and storage:app. No scope grants access to Confluence, admin APIs, or other Atlassian products.
- Only Jira project administrators can access the app's settings page, create or edit rules, or view execution logs — enforced by Forge's
jira:projectSettingsPage module, which Atlassian restricts to admin-level users.
Data storage and encryption
- All app data (rules and execution logs) is stored in Atlassian's Forge Entity Store (KVS), a managed, multi-tenant-isolated key-value store operated by Atlassian.
- Data in transit is encrypted via HTTPS/TLS on every connection, enforced by the Forge platform — the app cannot open an unencrypted connection even if it tried.
- Data at rest is encrypted under Atlassian's standard Forge storage encryption; Workflowly has no access to underlying storage infrastructure or encryption keys.
- No customer data is transmitted to, or stored on, any server outside Atlassian's platform.
What the app does not do
- Does not operate external servers, webhooks to third-party services, or any egress path off the Forge platform.
- Does not store payment or billing details — Marketplace billing is handled entirely by Atlassian.
- Does not use browser cookies, third-party trackers, or analytics SDKs.
- Does not access issue content beyond the specific field values needed to evaluate configured rule conditions at the moment an issue is created or updated.