Run your ISMS, not a folder of spreadsheets.
Statement of Applicability, risk treatment, signed approvals, incidents and documents, linked and ready for the auditor.
Request a demoThe problem
The SoA is a spreadsheet that no longer matches the controls you actually run.
Risk acceptances and approvals are e-mails an auditor cannot verify.
Incidents, policies and evidence live in different tools.
How ActiveERM handles it
- 1Assets and risksRegister IT assets and assess information-security risks on the same register as every other risk.
- 2Statement of ApplicabilityDecide each of the 93 Annex A controls: applicable, reason, status, owner, evidence.
- 3Treat and acceptPlan treatment actions; residual risks are accepted by named owners until a review date.
- 4ApproveIssue SoA versions and documents for approval, each decision signed with a passkey.
- 5OperateLog incidents, keep evidence, review and improve.
ERMAPP keeps its own information security management system on ActiveERM: the policy, the Statement of Applicability, the risks and the acceptances. The gaps we find become product work.
What you get
SoA of 93 controls
Applicability, reasons for inclusion, implementation status, owner, evidence, linked risks and actions per control; export to PDF and Excel.
Versioned SoA
Issue version N and name the approvers; an issued version keeps its own snapshot and the next draft shows only what changed.
Risk acceptances
Who accepted which residual score, why and until when; optional rules such as "high scores need two approvers"; reminders before expiry.
Passkey approvals
Approving a document, an SoA version, a risk acceptance or a risk takes a fresh passkey signature, stored with the decision.
Incidents with GDPR fields
Personal data involved, data categories, approximate number of people, risk decision and the 72-hour clock to the authority.
Documents
Policies with versions, a new approval for every new version, and read acknowledgments.