Security and Compliance

This page is written for security reviewers, internal audit and procurement. It describes what the app enforces, what it records, and — just as importantly — what it does not claim to do.

Access control

Access is decided by a single grant table with three fields: who, where, and what role. Every decision is traceable to exactly one row, which means an access review can be completed without reading application code or database state. See Access and Permissions for the model in full.

Segregation of duties

The app checks segregation of duties in two places, because two clean roles can still add up to a dirty combination:

  • Inside a role — the role builder blocks or warns on conflicting permission combinations as you build.
  • Across every grant a person holds — a separate check looks at the whole person, not one role at a time. This deliberately ignores scope boundaries, because a duty split across two registers is still one person doing both halves.

Independence

A workspace can be marked as sealed, meaning only members of the independence group that owns it may enter — including the platform administrator, who is otherwise able to reach everything.

Stated honestly: a software constraint on an administrator is a promise made by software. Provable independence — the kind an external auditor will accept without qualification — additionally requires a write-once destination outside the application. We would rather say this than overclaim it.

Audit trail

Every grant change and every elevated action is written to an append-only log with the actor, the timestamp and the object affected. The log can be searched and exported as evidence. An administrator can read it and cannot edit it.

Data, retention and residency

The app runs on Atlassian Forge and stores its data within the Atlassian Cloud platform, inheriting the platform’s residency options and security posture.

Needs an engineering answer before publication. Exact residency regions, per-object retention periods, deletion behaviour on uninstall, and sub-processor list. Do not publish this section until those are confirmed.

Accessibility

Target: WCAG 2.1 Level AA. A current conformance statement will be published here before general availability. Enterprise procurement routinely requires this, so treat it as a release blocker rather than a nice-to-have.

Framework support

The app ships installable control packs for ISO 27001 Annex A, NIST Cybersecurity Framework 2.0 and SOC 2 Trust Services Criteria. Installing a pack populates your control library and maps each control to the clause it satisfies. See Compliance frameworks.