💡 Still using the classic Drata experience? Refer to Apply default mapping between controls and requirements or Apply default mapping between controls and monitoring tests for the original UI.
Overview
Drata provides default mappings between:
Controls and framework requirements, and
Controls and monitoring tests
You can customize these mappings at any time by linking, unlinking, or replacing requirements or tests. If you want to return to Drata’s recommended configuration, you can revert to the default mappings at any time. This allows you to:
Safely experiment with custom mappings
Restore Drata’s baseline guidance
Align controls with updated or improved default mappings
💡 Important:
Custom controls, custom requirements, and custom tests are not affected. These mappings always remain under your control.
Prerequisites
The following roles can apply default mappings:
Administrator
Guest Administrator
Workspace Manager
Information Security Lead
Service Group User
Apply default mappings for an individual control
You can compare and restore default mappings for a single Drata Control Framework (DCF) control.
Open any DCF control.
Select the desired tab
Monitoring: Comparison to default mapped tests
Frameworks: Comparison to default mapped requirements
Select Compare to defaults.
Review the differences between your current mappings and Drata’s default mappings.
Depending on the control, this comparison may include:
Framework requirements
Monitoring tests
In the comparison modal, choose one of the following:
Keep current configuration to retain your custom mappings
Apply defaults to restore Drata’s default mappings
If your current mappings already match Drata’s defaults, a notification appears indicating that no changes are required.
When should you use default mappings?
Apply default mappings when:
You want to undo extensive customization
Drata has updated mappings for improved accuracy
You’re troubleshooting unexpected control coverage
You want to return to a known baseline before an audit
Key takeaways
You can customize mappings freely and safely
Default mappings can be restored at any time
Custom controls, requirements, and tests are never changed
Default mappings can be applied at the control level
Framework-level resets apply only to control-to-requirement mappings