Trust Center

Security and Incident Response

Last updated: .

To report a vulnerability, see Vulnerability Reporting.

Security responsibilities

Every Limbus Lab app runs on Atlassian Forge. Under Atlassian’s Forge shared responsibility model, Atlassian operates the runtime, network security, storage encryption at rest, tenant isolation, authentication of users before the app is invoked, DoS protection, platform monitoring and platform vulnerability management. Each app is responsible for its application logic, input validation, dependency management, secure use of storage and app-level retention. Vulnerability management, security incident response and disaster recovery are shared.

Each app requests only the permissions (scopes) listed for it and at installation. What else each app is responsible for, and its built-in safeguards, are on the app’s own page (see Each app).

Incident notification

Customers affected by a security incident involving their data are notified directly, without undue delay and no later than 72 hours after we confirm a breach affecting their data. A written post-incident summary is shared with affected customers within 10 business days. We report security incidents to Atlassian promptly, as required by the Atlassian developer terms.

Logging

How the apps log, who reads the logs and how long they are kept is in Data Logging and Retention.

Each app

Incident response plan

This plan applies to every Limbus Lab app: Hooq for Jira, SmartDash, PortalPilot, Simple Workflow Automation and MacroMint, running on Atlassian Forge. Each of these apps follows the same documented process: detect, triage and classify, communicate, resolve, and post-incident review. Current service state is on the status page.

Scope

An incident is any event that degrades or interrupts an app’s service, or that puts customer data at risk (suspected unauthorized access, cross-tenant exposure, data corruption). What this means for each app is on the app’s page, under Incidents.

Roles

  • Incident lead. Runs the incident, owns communications and the decision to close it.
  • Engineer on call. Investigates and fixes.
  • Communications owner. Posts to the status page and writes customer notices. May be the incident lead.

1. Detect

Sources: customer reports to the support or security contact; Atlassian notices (Forge platform incidents, Partner Security Incident Response Program, Marketplace notices); the app’s own monitoring (the developer reads the app’s logs through the Atlassian Forge logging tools to find issues before they are reported). Anyone who suspects an incident tells the incident lead immediately.

2. Triage and classify

Promptly after detection: confirm the problem, assign severity (below), name the incident lead, decide whether customer data or availability is affected, and decide whether Atlassian must be notified. Security incidents are reported to Atlassian promptly, as the Atlassian developer terms require.

Severity definitions
SeverityDefinition
SEV1 CriticalConfirmed or likely exposure, loss or corruption of customer data; or the app unavailable for most customers
SEV2 MajorCore function degraded for many customers, workaround exists, no data exposure
SEV3 MinorLimited impact: one feature, a few customers, or cosmetic
SEV4 InformationalNo customer impact (for example an internal error pattern or a near miss)

Examples for each app are on the app’s page.

3. Communicate

  • Status page: post an incident that affects customers, update it until it is resolved, and mark it resolved when done.
  • Direct notice: affected customers are told directly when their data is involved, without undue delay and no later than 72 hours after confirmation of a breach affecting their data.
  • Atlassian: reported through the partner incident channels for security incidents and for suspected Forge platform causes.
  • Customer names, site URLs and work item or page content are never posted publicly.

4. Resolve

Mitigate first (turn off the faulty feature, roll back, or deploy a fix), then fix the root cause. Each app is verified in real use before the incident is closed; how is on the app’s page. Security fixes follow the fix targets in Vulnerability Reporting.

5. Post-incident review

For every SEV1 and SEV2 (and any security incident): a written review within 10 business days, covering timeline, root cause, customer impact, what went well and badly, and corrective actions with owners and dates; shared with affected customers and summarized on the status page. Corrective actions are tracked until done, and recurring causes feed prevention work (tests, monitoring, design changes). The review is blameless.

Status page

The status page shows the current state of each app. The apps run on the Atlassian Forge platform and on Jira Cloud or Confluence Cloud, so when Atlassian has an incident an app may be affected. Atlassian publishes its status at status.atlassian.com (developer platform: developer.status.atlassian.com).

Review of this plan

This plan is reviewed at least once a year and after every SEV1.