AboutWhat's newContact & demo
Compliance ManagementAvailable now

Your controls, extracted, connected and governed.

RiskVantis uses the Secure Controls Framework as its canonical control layer. Your own controls, including those written inside policies, live in one register mapped to it, so every framework is reached through a single set of controls.

Illustration with sample data

Overview

What Control Library & Document Controls does

Most organisations already describe their controls inside policies nobody has time to re-read. RiskVantis extracts those controls and keeps them as Control Register records, each with a CTRL- identifier, objective, owner, frequency and applicable assets. Documents reference the controls rather than copying them, and each approved document version pins the control versions it contains.

Adding, changing or removing a document control is a governed proposal: a draft control version linked to a draft document version, approved by the affected Control Owners, the document owner and a CISO. Look for Similar Controls flags likely duplicates, and the SCF crosswalk relates your controls to every installed framework. You can also bring your own framework, such as an internal standard or customer contract, into the Framework Library.

Stacks of paper documents and file folders
Capabilities

Key capabilities

01

Canonical SCF layer

The Secure Controls Framework connects every installed framework.

02

Extraction from policies

Controls pulled from documents into the register, with their source recorded.

03

One control record

Documents reference register controls; approved versions pin them.

04

Governed change

Control changes are proposals that must be approved before they apply.

05

Duplicate detection

Similar controls suggested for consolidation, never merged automatically.

06

Your own frameworks

Add internal standards or contractual requirements alongside shipped frameworks.

Benefits

The business case.

Efficiency, multi-framework alignment, reduced complexity and streamlined processes: what Control Library & Document Controls changes for your programme.

Multi-compliance alignment
>60%

Fewer duplicate controls

A common control set mapped across frameworks removes redundant controls.

Reduced complexity
Single source

Policy ↔ control alignment

Control wording and policy text can never drift apart.

Potential savings
>70%

Less initial inventory work

Extraction replaces manual control cataloguing.

Achieving compliance
Statement of Applicability

Built on real controls

Mappings and applicability decisions give you a ready SoA.

Efficiency figures compare the effort of each workflow cycle in RiskVantis with the same work done manually or in a traditional GRC tool. Your result depends on your starting point; we will model it with you in a demo.

How it works

From setup to outcome.

Upload policies

Add documents to the library.

Extract

AI identifies controls and their attributes.

Map

Relate controls to SCF and every framework through the crosswalk.

Govern

Changes flow through approval with versioning.

Framework alignment

Supports your obligations.

Control Library & Document Controls contributes evidence and coverage to these frameworks and regulations.

Secure Controls Framework (SCF)ISO/IEC 27001:2022 Annex ANIST CSF 2.0PCI DSS v4.0.1SOC 2ITGC

All supported frameworks

FAQ

Common questions.

Is there a separate control list per document?

No. There is one Control Register. Documents reference its controls, and approved versions pin the control versions they contain.

What if I change a control's wording?

The change becomes a draft proposal and is applied only when the document version that shows it is approved.

Can we add our own framework?

Yes. Create a framework in the Framework Library, or import one from Excel.

See Control Library & Document Controls in action.

Book a 30-minute walkthrough tailored to your frameworks, vendors and team.