Mapping Controls to Frameworks

When you activate a compliance framework, CloudAnzen automatically maps a set of controls based on the framework's requirements.

Automatic Mapping

CloudAnzen ships with pre-built control mappings for all supported frameworks. When you activate a framework, controls are automatically created and mapped to the relevant requirements.

Reviewing Mappings

Navigate to Frameworks → [Your Framework] → Controls to see all mapped controls. Each control shows:

Control name and description
Framework requirement(s) it satisfies
Current status (passing, failing, needs review, not started)
Evidence sources linked to the control
Assigned owner

Customizing Mappings

You can customize mappings in several ways:

Add a control — Create a new control and map it to one or more framework requirements.

Remove a mapping — Unmap a control from a requirement if it's not applicable.

Edit a control — Modify the control's description, testing criteria, or evidence requirements.

Mark as not applicable — If a requirement doesn't apply to your organization, mark it as N/A with a justification.

Cross-Framework Mapping

If you're running multiple frameworks, CloudAnzen shows which controls are shared. Updating a shared control's evidence or status automatically reflects across all mapped frameworks.