Evidence repository
Every ISMS file, with what each one supports.
Argunis/SofIA Governance/Evidence and documents
Each file is linked to what it supports, with its validity and a fingerprint that proves nobody changed it. Your policies have versions, approval and read acknowledgment.
The same file supports a control, a requirement, a risk, a plan, an incident, a finding or an asset. You filter by standard, object type and status, and see what each one is linked to.
"Which evidence expires this month?"
Uploaded by the security manager · valid until Nov 14
Each file is stored with its SHA-256 fingerprint and cannot be replaced. Whoever uploaded it gets a notice before it expires, and retiring it keeps it stored for audit instead of deleting it.
Each policy, procedure, work instruction, plan or record has a code, versions and a cycle from Draft to Approved. It is reviewed at its set frequency and, when required, staff confirm they read it.
Every ISMS file, with what each one supports.
To controls, requirements, risks, plans, incidents, findings, documents and assets.
Expired, expiring within 30 days and a notice to whoever uploaded the file.
SHA-256 per file, verifiable at any time.
The file is retired and kept; it is never deleted.
Policy, procedure, work instruction, plan or record, each with its code.
Draft, in review, approved or obsolete.
Frequency in months and a notice to the owner before the date.
Staff confirm they read the policy.
It is not deleted: it is retired and kept for audit. If you delete the object it was linked to, only that link is removed.
Each file is stored with its SHA-256 fingerprint. Verify integrity computes it again and compares it with the recorded one.
An editor or administrator in the platform, or the committee through a decision in Governance, which applies on the spot.
We show you Argunis on your own operations and answer your questions in one call.