Security Policy — Export My Requests for Jira Service Management
Last updated: 10 November 2026
This policy describes how the Atlassian Marketplace app Export My Requests for Jira Service Management (the "App"), published by Jules Imbert (individual publisher, France, the "Publisher"), is built and operated securely, and how to report a security issue.
1. Hosting: Runs on Atlassian
- The App is built on Atlassian Forge and runs on Atlassian's infrastructure and in the user's browser. It is eligible for the Atlassian “Runs on Atlassian” program (checked with
forge eligibilityfor version 2.3.0 in production). - No egress: the App does not call any server outside Atlassian. There is no remote back end, no web trigger, no Connect module, no analytics, no tracking and no cookies.
- The Publisher operates no servers and has no access to customers' requests, customers, users or settings.
2. Data handling
- Requests are read as the portal customer (or the agent) who starts the export, with the Forge bridge
requestJirafrom their browser. Jira Service Management applies its own permissions, so users export only what they can already see. - Read-only server-side fallback: if that browser request fails at the network level (for example a blocked cross-origin request or a proxy), the App repeats the same read-only request, as the same user, from its Forge function (
proxyGet), inside Atlassian's infrastructure, and returns the result to the browser. Only the GET endpoints the App already uses are accepted, and every query parameter is validated against a whitelist. The endpoints for request types and fields are available only on the admin page, to Jira administrators. Nothing returned through the fallback is stored or logged. - The export file (CSV or Excel) is generated in the user's browser and downloaded directly. It is never uploaded or stored by the App.
- The only data the App stores is the export configuration chosen by the Jira administrator, in Forge app storage. It contains no personal data. No End-User Data is stored by the App, inside or outside Atlassian.
- Details: privacy policy.
3. Access control and permissions
- All reads of Jira Service Management data are made as the current user (browser
requestJira, orasUser()in the fallback). The App never reads requests as the app itself. - Settings: the admin function checks, server-side on every call, that the call comes from the Jira admin page module and that the user has the global Administer Jira permission. The portal function can only read the configuration and use the read-only fallback; the fallback is refused when the export is disabled or the licence is inactive.
- Every configuration value is validated against a whitelist (known column ids, custom field ids, numeric project ids, bounded lengths and counts).
- Exports are protected against spreadsheet formula injection: in CSV, cells starting with
=,+,-,@, tab or carriage return are prefixed with an apostrophe; in Excel, values are written as text, never as formulas. - Scopes requested (least privilege, all read-only on product data):
read:servicedesk-request,read:organization:jira-service-management,read:permission:jira,storage:app. The App has no write scope on Jira or Jira Service Management data.
4. Encryption
Data read by the App stays in Atlassian's cloud and the user's browser. The export configuration is kept in Forge app storage, protected by the Atlassian platform, including encryption in transit (TLS) and at rest. The App stores no data elsewhere and keeps no credentials, passwords or API tokens.
5. Logging
When a server-side operation fails, the App writes only the operation name and the error message to the Forge logs, which are hosted by Atlassian. The App does not log request content and sends no logs to third parties.
Vulnerability disclosure
If you believe you have found a security vulnerability in Export My Requests for Jira Service Management, please report it by e-mail to contact@menuiserieestivale.fr with the subject “SECURITY”. Please include the affected feature, steps to reproduce, the potential impact and, if possible, your Atlassian site URL. Do not include passwords, API tokens or customer data in the report.
- We acknowledge security reports within 2 business days (Monday to Friday, 9:00–18:00 Paris time (Europe/Paris, CET/CEST), excluding French public holidays).
- We assess severity (CVSS), keep you informed of progress, and tell you when a fix is released.
- We ask you to give us reasonable time to fix the issue before any public disclosure, and not to access, modify or delete data that does not belong to you.
Incident response and customer notification
We follow Atlassian's guidance for Marketplace partners on preparing for and managing security incidents:
- Detect: Atlassian Marketplace and ecosystem notifications, customer and researcher reports, dependency audits (
npm audit) and Forge platform logs. - Triage (within 24 hours of acknowledgement): confirm the issue, rate its severity and identify affected versions and customers.
- Contain: disable the affected functionality or roll back to the last safe version with a new Forge deployment.
- Notify: for critical issues, notify Atlassian and affected customers without undue delay, using Atlassian's vulnerability notification process and within the deadlines of the Marketplace Security Bug Fix Policy.
- Fix and verify: patch, run the automated tests and dependency audit, deploy to production and verify.
- Review: write a short timeline and root-cause analysis and update this policy and our dependencies.
Security updates
- Security fixes are released within the timeframes of Atlassian's Marketplace Security Bug Fix Policy for cloud apps: critical (CVSS ≥ 9.0) within 10 days, high (≥ 7.0) within 4 weeks, medium (≥ 4.0) within 12 weeks and low within 25 weeks of the report or triage.
- Updates are deployed through the Forge platform. Updates that do not change the app's permissions are applied to customer sites automatically, so customers do not need to take any action. An update that requests new permissions requires a site administrator's approval.
- Dependencies are monitored with
npm auditand updated when a vulnerability affects the App.
Contact
Security contact: contact@menuiserieestivale.fr (subject “SECURITY”). General support: support page. Privacy: privacy policy.
Material changes to this policy will be published on this page with a new date.
Export My Requests for Jira Service Management