Committees
Chair, secretary, members and meeting frequency.
Argunis/SofIA Governance/Governance
When you call the management review, the inputs are built from the actual state of the ISMS. What the committee decides applies on the spot and is followed up.
Each committee has a chair, a secretary, members and a frequency. You call management reviews, security committees and extraordinary sessions, upload the minutes as evidence and, on close, the inputs are frozen as they were seen.
"Which indicators are below target?"
Meets every 3 months · next session Dec 12
Approving a document, accepting a risk, approving the audit program or the statement of applicability takes effect when the decision is recorded. Any decision can create action plans and is followed until marked done.
A version is a full snapshot of the ISMS: the statement of applicability, each standard’s requirements, the risks, approved documents and indicators. It is saved with its fingerprint, cannot be changed and can be compared with another.
Chair, secretary, members and meeting frequency.
Inputs built from the state of the ISMS when it is called.
Security committee and meetings whenever needed.
Uploaded as evidence; they freeze the inputs on close.
Those of every session, with their follow-up.
Approve documents, the SoA or the audit program, and accept risks.
A committee commitment becomes an action plan.
Immutable, fingerprinted snapshots you can compare.
On Home, the state of the ISMS and the decisions awaiting leadership.
No. When you call it, the platform gathers what ISO/IEC 27001 clause 9.3 requires with the ISMS data of that moment.
The inputs are frozen as they were seen, the minutes stay as evidence and, for a management review, an ISMS version is saved.
To show what the ISMS looked like on a date and what changed between two. Each version is saved with its fingerprint and cannot be changed or deleted.
We show you Argunis on your own operations and answer your questions in one call.