OneClickComply
    Book a demo

    Cross-Framework Control Mapping

    Cross-framework control mapping: do the work once, count it towards every standard

    OneClickComply is compliance software for IT, security and compliance leads who work to more than one standard. Cross-framework control mapping links each control to equivalent, partial and related controls in other frameworks, so one task and its evidence count towards every standard it satisfies. One control set covers 240+ standards.

    Book a demo
    3 types
    of mapping: equivalent, partial, related
    One task
    counts towards every matching standard
    240+
    standards on one control set
    THE PROBLEM

    Why multi-framework compliance multiplies the work

    ISO 27001, SOC 2, NIS2 and customer security schedules ask for many of the same things in different words. Run each framework on its own and the same access policy, backup check or training record is written, evidenced and reviewed several times. A home-made crosswalk spreadsheet helps for a while, then falls out of date and nobody can say which rows still hold. Mapping the controls inside the platform removes the duplicate work and shows what each piece of evidence supports.

    FEATURES

    How control mapping works in OneClickComply

    Three kinds of mapping

    Each mapping between two controls is recorded as equivalent, partial or related. Equivalent means the controls ask for the same thing, partial means one covers only part of the other, and related means they touch the same topic without being interchangeable.

    One control set across the library

    One control set sits behind 240+ standards. Controls are held once and linked to the requirements they satisfy in each framework, instead of being copied into a separate checklist per standard.

    One task, several standards

    A catalogue task can name the controls it satisfies in more than one standard. Adopt several of those standards and you get a single task. Complete it, and it counts towards each matching control. Adopting a further standard later links the existing task rather than creating a duplicate.

    Cross-mapped controls on every control

    Open a control in Standards and its Cross-mapped controls group lists the controls it is mapped to in other frameworks, with a search box to find one. Customers see these mappings as read-only.

    Custom frameworks alongside the library

    Create a custom framework and add your own controls beside the published standards. How many custom frameworks and controls you can add depends on your plan.

    Mappings maintained by OneClickComply

    In the app, mappings are read-only for customers and edited by OneClickComply administrators, so the crosswalk stays consistent rather than drifting between customers. There is no standalone mapping matrix view: you read mappings control by control.

    See Cross-Framework Control Mapping working on your own setup.

    Book a demo
    BENEFITS

    What you gain from mapped controls

    Implement and evidence a control once, then reuse it for each standard it supports

    See at a glance which other frameworks a control also relates to

    Adopt a second or third framework without starting its task list from scratch

    Tell equivalent controls apart from partial ones, so you know when extra work is still needed

    Keep your own custom requirements in the same place as the published standards

    FAQ

    Cross-Framework Control Mapping: common questions

    Cross-framework control mapping links a control in one standard to the controls in other standards that cover the same or similar ground. It lets you implement a control once and show it against several frameworks, instead of keeping a separate checklist for each.

    Each mapping connects two controls and is typed as equivalent, partial or related. Catalogue tasks also name every control they satisfy across standards, so completing one task counts towards each of them.

    Equivalent controls ask for the same thing. A partial mapping means one control covers only part of the other, so you may still need extra work, and a related mapping marks controls that cover the same topic without being interchangeable.

    Not in the app. You can view the Cross-mapped controls for any control, but mappings are edited by OneClickComply administrators. If you need a requirement of your own, add it as a custom framework control instead.

    Not in the same way. Most catalogue tasks name the controls they satisfy across several standards, but Cyber Essentials is deliberately kept separate, with its question-set tasks each tied to a single Cyber Essentials control.

    No. Control mapping reduces duplicate implementation and evidence work, but each standard is still assessed on its own terms. Your certification body or auditor decides what evidence they accept for each one.

    Frameworks Cross-Framework Control Mapping supports

    Read what each framework asks for and how OneClickComply covers it.

    See Cross-Framework Control Mapping on your own stack

    Book a 30-minute demo and see how Cross-Framework Control Mapping works with the tools and frameworks you already have.

    Book a demo See pricing