Source: https://sprinto-test.docs-staging.pageloop.ai/compliance/controls

# Controls

A **control** in Sprinto is a specific measure or safeguard that addresses a compliance, security, or operational requirement. Controls help your organisation meet industry standards, frameworks, and regulatory mandates.

Once a control is created—either by default through a mapped framework or as a custom control—you can manage it to keep it relevant and aligned with your compliance needs. This includes updating its details, mapping or unmapping checks, and managing linked frameworks and criteria.

### Why Managing Controls is Important

Managing controls is not a one-time activity—it is an ongoing process. Business processes, technology stacks, and regulatory landscapes change over time. Regularly reviewing and updating controls helps you:

- Ensure that compliance requirements are always met
- Maintain accurate mapping to frameworks and criteria
- Avoid unnecessary checks or redundant control monitoring
- Deactivate controls that are obsolete or no longer in scope
- Provide auditors with clear, up-to-date evidence of compliance coverage

### Actions Available When Managing a Control

| Action                       | Purpose                                                                                                                                                                         |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Map/Unmap Checks**         | Link relevant monitoring checks to the control to verify its effectiveness, or remove checks that are no longer needed. Checks can be searched, filtered, and mapped in bulk.   |
| **Edit Control Details**     | Update the control’s name, description, category, or configuration to reflect internal changes or regulatory updates.                                                           |
| **Disable Control**          | Temporarily deactivate a control if it is under review, or permanently disable it if it is no longer applicable. This helps keep your compliance environment clean and focused. |
| **Manage Mapped Frameworks** | View, add, or remove frameworks associated with the control to ensure the right compliance standards are covered.                                                               |
| **Map Framework Criteria**   | Select specific clauses or requirements from a framework that the control satisfies. This provides traceability and proof of compliance during audits.                          |

### Example Use Cases

| Scenario                   | Action Taken                                                                 | Benefit                                                                         |
| -------------------------- | ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| **Compliance Alignment**   | Add a new framework to an existing control and map its criteria.             | Avoids duplicating controls while ensuring new regulatory requirements are met. |
| **Operational Change**     | Unmap outdated checks and replace them with relevant ones.                   | Keeps monitoring activities aligned with current operational practices.         |
| **Framework Optimisation** | Remove a retired framework while retaining links to other active frameworks. | Streamlines compliance coverage and reduces unnecessary framework management.   |

### Benefits of Regular Control Management

By consistently reviewing and managing your controls, you gain:

- **Audit Readiness:** Always have up-to-date framework mappings and checks for faster, smoother audits.
- **Risk Reduction:** Ensure no gaps exist in compliance coverage due to outdated control details.
- **Efficiency:** Reduce overhead by disabling unnecessary controls and streamlining monitoring activities.
- **Clarity:** Maintain clear associations between controls, checks, and framework requirements.
