DocumentaciónHelp

Migrate to a newer catalog revision

When Argunis publishes a new revision of a standard, review what changes (new, retired and remapped requirements, controls to create) and apply it.

On this page

Each adopted standard keeps the catalog revision it was adopted with: its requirements are resolved using that revision's mappings. When the Argunis CISO publishes a new revision, your standard doesn't change on its own: you decide when to migrate.

Before you start

  • Any role can see what changes. To migrate you need the Editor or Administrator role.

  • Migration can't be undone, but it doesn't delete anything.

Steps

  1. Open the standard from Standards → Adopted standards.

  2. If there's a newer published revision, you'll see the notice A newer published catalog revision is available (2026.2). Press Review and migrate (with Read only, See what changes).

  3. Review the change, which isn't applied yet:

    • New requirements: those the standard adds. If any doesn't apply because of the company's classification (for example, an obligation only for Operators of Vital Importance), the reason is shown and it comes in excluded.

    • Retired requirements: those the standard no longer has. They'll become not applicable.

    • Requirements with different mappings: which ISMS controls covered them before and now, with their coverage (equivalent, partial or related).

    • ISMS controls that would be created: those the new revision requires and your ISMS doesn't have yet. You can choose whether their catalog KPIs are also created.

  4. Press Migrate to revision 2026.2 and confirm with Yes, migrate. If the new revision doesn't change this standard's requirements or mappings, only the revision is updated.

What happens next

You'll see a message with what was applied and the new compliance.

  • The standard is on the new revision and the notice disappears.

  • New requirements appear in Requirements as Pending (or excluded with their reason).

  • Retired requirements become Not applicable with the justification "Retired from the catalog…". Their evidence, links and answers are kept.

  • New controls appear in ISMS → ISMS controls as Pending.

  • The standard's compliance (and that of the other standards sharing controls) is recalculated.

If something goes wrong

  • The catalog published another revision since you reviewed the change: review it again. Close the window and press Review and migrate again.

  • The standard already uses the newest published catalog revision. There's nothing to migrate.

Related

Search SofIA Governance

Type at least 2 characters to search SofIA Governance.

↑↓ to navigate · Enter to open · Esc to close