Argunis/SofIA Governance/Standards

What you already did counts everywhere.

You adopt a standard on your ISMS and see up front how much of it you already cover. Its requirements are met with the controls you have, and what is missing goes into its roadmap.

Cross-coverageFrom ISO/IEC 27001:2022
Your ISMS covers
Law 21.663Adopted68%
NIST CSF 2.0Not adopted61%
Law 21.719Adopted47%
ISO 22301:2019Not adopted35%

Adopt in seven steps

You choose the standard, confirm the company data, answer its questionnaire and review the proposed diagnosis. Then you set scope, owner and phases, and the platform adds only the controls you are missing.

  • How much you already cover, before adopting
  • Assessment questionnaire per standard
  • Diagnosis of requirements and controls
  • Classification under Law 21.663
Ask SofIA

"How much of Law 21.719 does ISO 27001 cover?"

cobertura_normas
Adoption · Law 21.719
Already covered41%
New controls9
Own requirements12
  1. 1Standard
  2. 2Company
  3. 3Assessment
  4. 4Diagnosis
  5. 5Scope
  6. 6Roadmap
  7. 7Confirm

Cross-coverage

Each requirement is tied to ISMS controls with equivalent, partial or related coverage. You pick a source and a target standard, and see how much is met today, how much is planned and what is missing, with the reason.

  • Equivalent, partial or related
  • Met today and planned
  • What is missing, requirement by requirement
  • Target adopted or still to adopt
ISO/IEC 27001:2022 → Law 21.719
Met today47%
Planned72%
Missing
Data subject rightsIts control is not in the ISMSMissing
Data protection officerPartly covered: the standard’s own part is missingPartial
Processing security measuresIts control is in the ISMS but not yet compliantIn progress

Roadmap and audit package

Each standard comes with suggested phases you can reschedule, an analysis of baseline documents that proposes what they support, and an audit package with current evidence, in PDF and in ZIP with each file’s fingerprint.

  • Dated phases in My work
  • Proposals from your baseline documents
  • PDF with the SoA and embedded evidence
  • ZIP with a SHA-256 manifest
Roadmap · ISO/IEC 27001:2022
Phase 1 · Context and scopeDone
Phase 2 · Risk and statement of applicability80%
Phase 3 · Control implementation45%
Phase 4 · Internal auditMarch

Everything in Standards

Standards catalog

ISO/IEC 27001:2022, ISO 22301:2019, NIST CSF 2.0, Law 21.663 and Law 21.719.

Guided adoption

Seven steps, with the ISMS coverage from the first one.

Initial assessment

Each standard’s questionnaire, to start from a diagnosis.

Own requirements

What the standard asks for on top, where coverage is partial or there is no control.

Cross-coverage

How much of one standard is covered by what you did for another.

Roadmap

Suggested phases you can reschedule, with their dates.

Document analysis

Upload a policy and review which controls and requirements it supports.

Audit package

PDF and ZIP with current evidence and its fingerprint.

Per-standard dashboard

On Home, where the gap of each adopted standard is.

Frequently asked questions

Which standards can I adopt?

ISO/IEC 27001:2022, ISO 22301:2019, NIST CSF 2.0, Chile’s Law 21.663 (Cybersecurity Framework) and Law 21.719 (Personal Data Protection).

Does adopting another standard double the work?

No. Existing controls are reused as they are and only the missing ones are added, with their indicators.

What do I hand to the auditor?

The standard’s audit package: a PDF with the scope, the statement of applicability, the roadmap and the evidence, and a ZIP with the originals and each one’s fingerprint.

See the failure before your customers do.

We show you Argunis on your own operations and answer your questions in one call.

Let’s talk

Tell us what you need and we will get back to you shortly.

Book a demo

Choose a day and time. The meeting is on Google Meet and lasts 30 minutes.

Day
Time · Chile time (Santiago)

Looking for free times…