Start here
Start here
This chapter builds the base understanding every user needs: what the ISMS App does, how an ISMS works as a control loop, how to find your way around the ISMS Hub, and which roles and permissions exist.
Prerequisites
- Jira Cloud with the ISMS with Jira & Confluence app installed and a valid licence.
- Confluence Cloud is optional but required for the Confluence space, the reports and document control.
- For setup: Jira administration rights. For day-to-day work, access to the “ISMS Home” project is enough.
Pages in this chapter
Quick glossary
| Term | Meaning |
|---|---|
| ISMS | Information Security Management System — the governed loop of recording, assessing, treating and improving information security. |
| ISMS Hub | The app’s user interface — a dedicated app page, identical in Jira and Confluence (The ISMS Hub at a glance). |
| ISMS Home | Both the Jira project created by the app (key ISMS) and the Confluence space carry this name. |
| Domain | One of the four subject areas in the project: assets & risks, requirements, measures, audits & nonconformities (Domains and issue types). |
| Protection need (C/I/A) | Rating of an asset by confidentiality, integrity and availability; the highest value determines the protection need. |
| RACI | Responsible, Accountable, Consulted, Informed — the responsibility roles on every issue (Roles and permissions). |
| SoA | Statement of Applicability — a mandatory document under ISO 27001 (Generating reports). |
| Document control | Approvals and read confirmations for Confluence pages with an audit-proof log (Using document control). |
The full glossary with German–English terminology is at Reference and glossary.
Documentation baseline: app version 1.1.15 · 2026-08-20