Crosswalks
Most frameworks ask overlapping questions. An access-control requirement in one standard usually has a close cousin in the next, and re-proving the same practice framework by framework is wasted work. Crosswalks are how SolveGRC removes that waste: framework requirements are mapped to a shared catalog of unified controls, so one implemented control can count toward equivalent requirements in every framework you have activated.
Where crosswalk credit shows up
When controls in a framework are satisfied through the crosswalk rather than a direct assessment, the compliance score card shows a chip: how many controls are satisfied via crosswalk, and how many of those are also evidenced. These are already included in the score above the chip and are never double-counted against a direct assessment. Credit that would come only from an unreviewed AI mapping appears as a separate chip, n via unreviewed AI mapping · not counted, and adds nothing to the score.
Crosswalk credit goes only to requirements you haven't assessed directly, and it needs one of your controls to be Implemented or Monitored and the mapping to be approved. It does not need evidence, which is why evidenced is counted separately.
Adopt suggested controls
Inside an active framework's control tree, requirements that the crosswalk maps to unified controls show them as suggested controls. Each suggestion carries an Adopt action: adopting brings the unified control into your organization's register. It earns credit once you set it to Implemented or Monitored and the mapping behind it is approved.
Each requirement row also shows its coverage at a glance: Met when an implemented control has evidence linked within the past year, n fulfilled · needs evidence when it does not, how many controls you've adopted, and an AI-suggested badge where relevant. Use Attach evidence on the row to link evidence directly.
AI-suggested mappings are reviewed by SolveGRC
The mappings themselves come from a crosswalk engine, and the system is honest about which ones a person has confirmed. A requirement whose path to satisfaction relies on a mapping not yet approved carries a purple AI-suggested badge, so you always know whether a piece of crosswalk credit rests on a reviewed equivalence or a machine's proposal. Where the engine finds requirements no existing unified control addresses, it drafts additions to the catalog, and those drafts are approved before they exist at all.
Mappings are shared across all SolveGRC customers, so SolveGRC's crosswalk reviewers approve them, not your team. An approval lapses if the wording of the requirement or the control changes, and the mapping goes back for review.
Treat the AI-suggested badge the way you treat any unreviewed claim: fine as a lead, not yet proof. The badge disappears once the mapping is approved.
Sync a verdict across frameworks
Crosswalks also work at assessment time. After an AI analysis, a control card that has counterparts elsewhere shows a related count and a collapsible Cross-Framework Sync panel listing them. From there you can apply your verdict to the eligible equivalent controls in your other activated frameworks, behind a confirmation dialog (Confirm Cross-Framework Sync), with per-control results reported back. Sync copies the status only, never the evidence.
Browse the unified catalog
The Unified Controls tab on the Frameworks page is the reference view: the global catalog of unified controls and the framework requirements each one maps across. Use it when you want to understand the mapping fabric itself rather than any one framework's score.
Crosswalk credit does not carry evidence with it. Evidence links are not copied between frameworks, and an audit engagement takes the evidence you attach to each of its requests. Link evidence where an auditor will look for it, as described in Assess controls.