Control Mapping

See where two compliance frameworks ask for the same thing, so one piece of evidence can answer several requirements instead of being gathered twice.

Most organisations satisfy more than one framework (a published set of security or compliance requirements, such as NIS2 or ISO 27001), and many frameworks ask for the same underlying control (a specific safeguard, such as multi-factor sign-in) in different words. Control Mapping lays those overlaps out side by side. Its first workbench, Cross-Framework Alignment, shows which controls correspond across frameworks, how strong each overlap is, and where the same evidence (the proof a control works) could be reused.

This screen reads the mappings that already exist and presents them four ways: headline counts, a relationship diagram, an overlap matrix, and a searchable table. A Manager or an Admin can also add, edit and delete a mapping from it, and copy evidence links along direct mappings from one framework to another; for everyone else it is read-only.

Who uses it

The page requires only a signed-in account, and everyone sees the same counts, diagrams and table. The controls that change something — Add Mapping, Edit, delete and the Propagate evidence links panel — need the compliance-update permission, which only a Manager or an Admin holds. Without it those controls are not shown at all.

The sibling Deduplication tab has actions of its own: generating, accepting or rejecting an AI suggestion there needs the compliance-update permission, which only Manager and Admin hold. A Contributor or Viewer can open that tab and read it, but cannot act on a suggestion.

What's on this screen

Two tabs sit at the very top: Cross-Framework (the view you land on) and Deduplication. Below them is the page heading Cross-Framework Alignment, a one-line description, and a Refresh button on the right (a Manager or an Admin also sees Add Mapping there) that re-fetches the figures without reloading the page. The captured screen was taken as a Contributor, so it shows Refresh alone.

Under the heading is a row of four summary cards: Total Mappings (715 in the captured screen), Direct Mappings in green with an average-overlap line beneath it (270, Avg 92% overlap), Efficiency Score with a potential-reuses line beneath it (11%, 993 potential reuses), and Frameworks (11).

Next come two panels side by side. On the left, Framework Relationships draws a labelled bubble, with its control count as a caption beneath, for every framework that has at least one mapping — ten in the captured screen, from CyberFundamentals Framework, NIS2 Directive and DORA round to NEN 7510, NEN 7512, NEN 7513, ISO 22301, ISO 27001 and ISO 9001:2015. Coloured lines join them; a line's thickness reflects the number of mappings and its colour the average overlap. A legend beneath reads High overlap (80%+), Good (60-79%) and Partial (40-59%). On the right, Framework Overlap Matrix lists every framework with at least one recorded mapping, by its full name, down the rows and across the columns; each cell gives the mapped-control count for that pair, the shaded diagonal the framework's own control count. It is wider than its panel, so it scrolls sideways.

Below the fold sit the Evidence Efficiency panel and the Control Mappings table with its search box, two filter lists and, when there are more than 100 mappings to show, Previous and Next buttons. A Manager or an Admin also finds the Propagate evidence links panel at the very foot.

Opening Control Mapping and getting oriented

  1. In the left menu, open the COMPLIANCE group and select Control Mapping. The Cross-Framework Alignment view opens on the Cross-Framework tab.
  2. The ? in the top bar slides in the help panel from the right, with help topics for this page and a search box. The page stays open behind it.
  3. The book icon beside it opens the in-app User Guide in the content area, at the chapter for the screen you came from. The sidebar and top bar stay where they are.
  4. Your name and initials sit at the top right and open your profile, with Sign out beside them. Your role decides only whether the editing controls appear; the figures on this page are the same for everyone.
  5. The Framework Overlap Matrix on the right is the fastest read of the page: any cell above zero is a framework pair that already shares mapped controls. Drag it sideways for the columns beyond the panel edge.
Cross-Framework Alignment, the first Control Mapping workbench — /compliance/cross-framework.
Cross-Framework Alignment, the first Control Mapping workbench — /compliance/cross-framework.

Reading the four headline cards

The cards give the shape of the picture before you read any single mapping.

  1. Read Total Mappings for the recorded relationships between controls across every framework in scope — 715 in the captured screen.
  2. Read Direct Mappings for the one-to-one equivalents, and the line beneath for their average overlap. These are where evidence reuse is most likely to hold up.
  3. Read Efficiency Score for how much evidence is already doing double duty, and the line beneath for how many more reuses look possible — 11% and 993 potential reuses in the captured screen. When there is nothing to score, the card shows N/A and the line beneath says why: no controls overlap by 70% or more yet, the overlapping controls carry no linked evidence yet, or there is not enough data to compute reuse.
  4. Read Frameworks for how many frameworks are switched on in your tenant and covered by your licence — 11 in the captured screen, whether or not any of them has a mapping yet. Select Refresh after work elsewhere to pull current figures.
Every figure counts every mapping

The four cards, the Framework Relationships diagram and the Framework Overlap Matrix are all built from the full set of mappings between frameworks that are switched on and licensed, so they agree with one another. Only the Control Mappings table works a page at a time — 100 rows per page — and its search and filters still look across the whole set.

Reading the Framework Relationships diagram

  1. Find each framework bubble and read its control count in the caption beneath it.
  2. Follow the lines between bubbles. A thicker line means more mappings connect that pair, and the small number on it is the mapping count for the pair — in the captured screen, a line labelled 229 joins CyberFundamentals Framework and ISO 27001, and a green band labelled 120 joins NEN 7510 and ISO 27001. Thickness stops growing at fourteen mappings, so every busy pair looks alike.
  3. Check the colour against the legend: green is a high overlap (80% or more), blue good (60–79%), amber partial (40–59%). A pair averaging under 40% is drawn red, which the legend does not list. A thick amber line therefore means many mappings that each only partly match.

With ten or more frameworks the ring gets crowded: in the captured screen several names and line labels overlap. Use the diagram for the overall shape and the matrix for an exact pair. If no mappings exist yet, the panel reads No cross-framework mappings yet. Create control mappings to see how your frameworks relate.

Reading the Framework Overlap Matrix

  1. Find your framework in the row headings down the left — CyberFundamentals Framework, DORA, GDPR, ISO 22301, ISO 27001 and ISO 9001:2015 — Quality Management System head the rows in the captured screen, with more below.
  2. Read across. The shaded cell where the row meets its own column gives that framework's control count (ISO 27001, 116 controls); every other cell gives the mapped count for the pair (229 mapped where ISO 27001 meets CyberFundamentals Framework).
  3. Scroll sideways for the remaining columns. A row of near-zeros — DORA shows 2 mapped against GDPR and 5 mapped against ISO 9001:2015 in the captured screen — means that framework has barely been mapped yet, not that it has nothing in common with the others.

When only two frameworks have mappings, this panel becomes Framework Overlap instead: two overlapping circles with the shared count in the middle and each framework's control count beneath. With no mappings at all it reads No framework mappings available.

Judging evidence reuse

Below the two panels, Evidence Efficiency restates the score as a coloured badge — green from 75%, amber from 50%, red below, grey when there is no data. Three tiles follow: Already Shared (evidence items attached to both controls of a mapping), Reuse Opportunities (items attached to one side that could serve the other) and Potential Savings (the redundant uploads that reuse would avoid). Beneath them, High-Overlap Mappings counts mappings at 70% or more. The Efficiency Recommendations box gives standing advice rather than named mappings: review the reusable evidence items (it names how many), and concentrate on mappings at 70% or more. A score below 60% adds a line saying the score is below target; a score of 75% or more adds one saying evidence is already well used.

Every figure in this panel is drawn only from mappings at 70% overlap or more, so it describes your strongest candidates rather than all your evidence. Read it as a shortlist, not a scorecard: it shows where reuse looks plausible, and your team still confirms the evidence answers both requirements.

Finding and comparing a specific mapping

The Control Mappings table lists mappings 100 to a page, highest overlap first, under the columns Primary Control, Related Control, Type, Overlap (a bar and a percentage), Description and Actions. Each control shows a small chip with its framework's name, then its reference, with the control title beneath.

  1. Type into Search mappings... to match a control reference, title or mapping description. After a short pause the table reloads with Loading mappings… and shows the matches from the whole mapping set, starting again at page one.
  2. Narrow by relationship using the type list — All Types, Direct, Partial, Complementary or Parallel Process.
  3. Narrow by framework using the framework list, which offers every framework switched on and licensed in your tenant. If nothing matches, the table shows No mappings found. If the request fails, it shows Could not load mappings. Try refreshing.
  4. When there are more than 100 results, a footer appears beneath the table with the range (for example Showing 1–100) and Previous and Next buttons. Step through the pages; your search and filters stay in place.
  5. Select a row, or Compare in its Actions column, to open the Control Comparison dialogue: mapping type and overlap at the top, the Mapping Relationship description, the two controls side by side with their Requirements and Status, then Shared Requirements and Key Divergences with their counts, and an Overlap Percentage bar at the foot.
  6. Read the divergences before reusing anything — they are the parts still needing separate work. Close returns you to the table with your filters intact.

A Manager or an Admin also sees two controls in each row's Actions column. Edit opens Edit mapping, where the two controls are shown for context only — a different pair is a different mapping, so delete and add instead. Change the Type, the Overlap (a whole number from 0 to 100) or the Description, then select Save changes; the cards, diagram, matrix and table all reload. The bin icon deletes the mapping after you confirm, and cannot be undone. Add Mapping opens a form beneath the heading for a new pair — a primary and a related framework, then a control from each — and refuses a pair that is already mapped with A mapping between these two controls already exists. Each change is recorded in the audit log.

Mapping type What it means for your evidence
Direct The two controls ask for the same thing. Evidence for one usually answers the other, subject to the listed divergences.
Partial They overlap, but one asks for more. Reuse part of the evidence and add to it.
Complementary Same risk, different angles. Both are usually needed; evidence is rarely interchangeable.
Parallel Process Separate processes running alongside each other. Related reading rather than a reuse opportunity.

Propagating evidence links along direct mappings

A Manager or an Admin sees a Propagate evidence links panel at the foot of the page whenever more than one framework is in scope. It turns the reuse the page points at into real links: every evidence item linked to a control in one framework is linked to that control's Direct-mapped counterpart in another. The captured screen was taken as a Contributor, so the panel does not appear in it.

  1. Choose the source in From framework and the target in To framework. They start on ISO 27001 and ISO 27002 when both are in scope. Propagate stays disabled while the two are the same.
  2. Select Propagate. A confirmation line appears asking whether to link the evidence of every source control to its direct-mapped target control, and warning that each link can only be removed one at a time.
  3. Select Confirm to run it, or Cancel to back out. When it finishes, a message reports how many evidence links were created — or No new links were needed. — and the cards and panels reload.

Existing links are kept, only Direct mappings are followed, and the run goes one way: to link the other direction, swap the two frameworks and run it again. Every new link is recorded in the audit log. Linking evidence does not recalculate any control's status; your team still reviews whether the evidence meets the target requirement.

The Deduplication tab

Select Deduplication at the top of the page to switch to the second Control Mapping workbench, Cross-Framework Deduplication. Where the Cross-Framework view explains how frameworks relate, Deduplication works on the controls themselves: it gathers near-identical controls into one unified view, estimates the implementation effort that saves, and lists suggested groupings for a person to accept or reject. Filter pills limit it to chosen frameworks; status tabs separate undecided suggestions from handled ones.

The AI assist

The Cross-Framework view has no AI in it — every number comes from mapping records already in your tenant, and evidence propagation follows those records without any AI. On the Deduplication tab, AI proposes which controls belong in the same group, and those proposals stay suggestions: a Manager or Admin has to accept or reject each one, and nothing is grouped until they do. AI assists; the organisation decides.

Tips and limits

Where this connects