Skip to content
English
  • There are no suggestions because the search field is empty.

How to Use Crosswalks to Reuse Scores Between Frameworks

A crosswalk is your own mapping between two frameworks in your workspace, which lets you carry the scores from a framework you have already assessed onto another, one control or one framework at a time.

If you have already assessed one framework, a crosswalk lets you reuse that work in another instead of scoring it from scratch. You upload a mapping that says which controls in the framework you have assessed (the source) correspond to each control in the framework you want to fill in (the destination). Each destination control then shows the average score of the source controls mapped to it, and you can apply that average as the control's score. Nothing changes in your assessment until you apply an average.

Both frameworks must already be in your workspace. To add one, see How to upload a security framework.

Crosswalks, the Master Control Framework and framework translation

CyberHQ has three ways to carry assessment work between frameworks. They work differently, and you can use more than one.

  • The Master Control Framework mapping. Every framework in CyberHQ is mapped to the Master Control Framework. With objective scoring switched on, a framework's scores are worked out from your answers to the Master Control Framework questions behind each control, and keep updating as those answers change. The Master Control Framework remains the basis for risk scoring and for integrations, and adding a crosswalk doesn't change that. See Understanding Your Capabilities Scoring & The 'Master Control Framework'.
  • Framework translation. CyberHQ uses AI to match each control in the framework you are translating to with similar controls in a framework you have already answered, and suggests a score, evidence and other fields for it. You review the suggestions on Assessments > Coverage and confirm them in one pass. See How to Translate a Framework.
  • A crosswalk. A mapping you supply yourself, as a CSV, listing which source controls correspond to each destination control. Nothing is matched automatically: the crosswalk holds exactly the pairs in your file. Once saved, it stays visible on the Scoring tab of every control it reaches and can be applied as often as you need. A crosswalk carries scores only, as an average of the mapped source controls. Many standards bodies publish crosswalks between their own frameworks, which can serve as the basis for your file.

Adding a crosswalk

  1. From the navigation menu, click Assessments > Capabilities and open the tab of the framework you want to fill in. This will be the crosswalk's destination.
  2. Click the Add crosswalk icon (the link icon) in the toolbar to open the Add crosswalk drawer.
  3. Enter a Crosswalk name, for example NIST ISO crosswalk. A name is required.
  4. Check the Destination framework. It is always the framework you have open and can't be changed here. To build a crosswalk into a different framework, close the drawer and open that framework's tab first.
  5. Choose the Source framework: the framework you have already assessed, whose scores you want to reuse. The list offers every other framework in your workspace; the Master Control Framework isn't offered. Choose the source before downloading the template, so the template also lists the source framework's control IDs for reference.
  6. Click Download template. The template already carries every control ID in the destination framework in its ID column, exactly as it appears in CyberHQ, so only the Mapping column is left to fill.
  7. Fill in the Mapping column. For each destination control, enter one or more IDs of the source controls that correspond to it, separated by semicolons (;), for example GV.OC-01;GV.OC-02. Use the IDs exactly as they appear in CyberHQ, and use the IDs of the controls you score, not the headings of the groups they sit in. Leave the Mapping cell empty for any control with no equivalent: rows with an empty Mapping cell are skipped, so leaving a control unmapped is fine. If the same pair appears more than once, it is counted once.
  8. Drag the completed file onto the upload area in the drawer, or click Open to choose it. Only .csv files are accepted. Click Clear to remove a file and choose another.
  9. Click Preview matches. It becomes available once the drawer has a name, a source framework and a file. The preview shows how many mappings were found and across how many destination controls (for example 2 mappings across 1 destination control), and lists each matched destination control with the number of mapped controls found for it. Any destination or source IDs that didn't match are listed under Skipped; they are not imported, and don't stop the rest of the file from being saved. If nothing in the file matches, the preview says so and asks you to check the control IDs. If the preview shows IDs you expected to match, correct them in the file and upload it again.
  10. Click Confirm & save crosswalk, which takes the place of Preview matches once the preview is shown. A message confirms the crosswalk was saved and how many mappings it holds. The crosswalk is saved exactly as the preview showed it, all in one go: if saving fails, nothing from the file is saved.

Saving a crosswalk doesn't change any scores. Scores only change when you apply an average, as described below. Once the framework has a crosswalk, two new controls appear at the top of its assessment: a Scoring selector beside View, and the Apply average across this assessment from bar.

Seeing crosswalk scores on a control

Open any control in the destination framework and select its Scoring tab, the first icon tab in the detail panel.

  • One row per crosswalk. Each crosswalk that maps into this control has its own row, showing the average score of the source controls mapped to it, with a button to apply that average as the control's score.
  • A combined row. When two or more crosswalks reach the same control, a combined row also appears. It averages every mapped source control from all of those crosswalks together, rather than averaging each crosswalk's average, so each source control counts equally.
  • No crosswalk. A control that no crosswalk reaches says N/A, No crosswalk maps to this control.

How the average is worked out

  • The average is a plain average of the mapped source controls' current scores, with each source control counting equally.
  • Source controls marked Not Applicable are left out of the average entirely.
  • Source controls that haven't been answered count as zero, so they pull the average down rather than being skipped.
  • Each row shows how many source controls were left out as Not Applicable and how many unanswered controls were counted as zero.
  • If every mapped source control is Not Applicable, the row shows N/A instead of a score.

The average reflects the source controls' scores as they are now, so it moves as you reassess the source framework. A score you have already applied doesn't change with it.

Simple and Advanced views

Once at least one crosswalk reaches a framework, a Scoring selector appears beside View at the top of the assessment, with Simple and Advanced options. It changes how much scoring detail each control shows, including whether the Master Control Framework row appears alongside the crosswalk rows.

Applying an average

You can apply an average to one control, or to every control a crosswalk reaches at once.

  • To one control: on the control's Scoring tab, use the apply button on the crosswalk row, or on the combined row.
  • To every control: use the Apply average across this assessment from bar at the top of the assessment. Choose the crosswalk from the drop-down, or, where two or more crosswalks reach the framework, all of them combined, then click Apply to all mapped controls.

Either way, you must choose between two options before anything is applied. There is no default:

  • Fill only the controls that haven't been scored yet, leaving controls that already have a score as they are.
  • Overwrite existing scores as well, so every control the crosswalk reaches takes the average, including controls already scored.

Whichever you choose, a destination control marked Not Applicable is never changed, and a control whose score already equals the average is left as it is. An applied score is an ordinary score: you can change it afterwards like any other, and the change is recorded in the control's activity log.

Overwriting existing scores replaces the scores already entered on every control the crosswalk reaches, including scores entered by hand, so check the option you have chosen before applying an average to the whole framework.

Managing your crosswalks

Go to Settings > Capabilities and open the Crosswalks tab to see every crosswalk in your workspace. For each one:

  • Mappings is the number of source controls mapped in.
  • Controls covered is the number of destination controls the crosswalk reaches.

The list also shows each crosswalk's Name, Source framework and Destination framework. For example, a crosswalk from NIST CSF 1.1 to NIST CSF 2.0 might show 151 mappings covering 87 controls, because several source controls can map to the same destination control.

To remove a crosswalk, click the bin icon in its Delete column and confirm in the Delete crosswalk dialog. The crosswalk then stops appearing on every control it maps into, and in the framework-wide apply bar. Scores already applied from it stay as they are. A crosswalk can't be edited once saved, so to change one, delete it and add a corrected crosswalk from the assessment.

With a crosswalk in place, the scoring you have done in one framework carries across to another on your own terms, and stays available to reapply as your source framework is reassessed.

Related articles: How to Assess your Capabilities; How to Translate a Framework; Understanding Your Capabilities Scoring & The 'Master Control Framework'; Understanding Framework Coverage; How to upload a security framework.