Security

Security & Data Residency

Last reviewed: April 2026

Forge-native architecture

All 3T Apps products are built entirely on Atlassian Forge. Forge is Atlassian's serverless platform that runs all app code within Atlassian's own infrastructure. There are no external servers, no third-party backends, and no data leaving the Atlassian ecosystem.

Data storage

All application data — configuration, technician availability, location data, API keys, and feedback — is stored exclusively in Forge KVS (Key Value Store), which is Atlassian's own managed storage layer. Data residency follows your Atlassian organisation's configured data residency region.

Input validation & authorisation

All user inputs are validated and sanitised server-side. All write operations require server-side authorisation checks. Admin functions are protected by a three-tier permission check. XSS protection via React's built-in escaping. AQL injection prevention via character escaping and query sanitisation.

Permission scopes

TechDesk for JSM

ScopePurpose
read:jira-work, write:jira-workReading and updating JSM tickets, comments, time logs
read:jira-userDisplaying assignee and user information
read:servicedesk-request, write:servicedesk-requestHandling JSM service requests and forms
manage:jira-configurationReading project configuration for admin settings
manage:jira-projectFetching project statuses and request types
read:cmdb-*Asset field AQL discovery and display
storage:appForge KVS for storing app configuration

DispatchDesk for JSM

ScopePurpose
read:jira-work, write:jira-workReading tickets and updating assignments, statuses
read:jira-userDisplaying technician profiles and assignee information
read:servicedesk-request, write:servicedesk-requestReading and transitioning JSM service requests
manage:jira-configurationReading project configuration for dispatcher settings
manage:jira-projectFetching project statuses and request types for filtering
storage:appForge KVS for configuration, availability, and location data

Assets to SQL for JSM

ScopePurpose
read:cmdb-*Reading Jira Assets schemas, object types, and records for export
manage:jira-configurationReading project and Assets configuration for schema discovery
storage:appForge KVS for API keys, export configuration, and sync schedules

External endpoints

TechDesk: The only external API call is to api.atlassian.com. No third-party services.

DispatchDesk: Contacts api.atlassian.com for all Jira data. Map tiles load via Leaflet npm package from OpenStreetMap — no user data is transmitted to tile servers.

Assets to SQL: Reads Assets data from api.atlassian.com. The pull endpoint is served by Forge's own runtime. Webhook push sends export payloads to the URL configured by the admin — no default external endpoint.

Vulnerability management

We use npm audit as part of our development process to identify and remediate dependency vulnerabilities. All vulnerabilities with available fixes are resolved before release. Remaining unfixable vulnerabilities are confined to upstream Atlassian SDK packages (@atlaskit/*, @forge/react) where no patched versions are currently available from Atlassian.

Incident response

In the event of a confirmed security incident or critical vulnerability, we will notify affected customers via email within 72 hours and notify Atlassian per the Atlassian Security Incident Management Guidelines. Critical vulnerabilities will be patched within the timeframes defined in the Atlassian Marketplace Security Bug Fix Policy.

Security controls

Our development environment requires Multi-Factor Authentication (MFA) on all source code access (GitLab). All Forge app secrets are stored using Atlassian's Forge Secrets API — no credentials or API keys are hardcoded in source code or committed to repositories. Input validation and sanitisation is applied to all user-supplied data both client-side and server-side.

Reporting a vulnerability

Email support@3t-apps.com with a description of the vulnerability, steps to reproduce, and potential impact. We will acknowledge within 2 business days and aim to resolve confirmed vulnerabilities within 30 days in accordance with Atlassian's bug fix policy. Please do not report security vulnerabilities through public channels.

Documentation requests

Detailed DATA-RESIDENCY.md and PRIVACY.md documents are available for enterprise security reviews. Contact support@3t-apps.com to request them.