Skip to main content
The Controls page is your unified library of security controls. Each control is mapped to one or more compliance frameworks, so implementing a control contributes to your readiness scores across all relevant frameworks simultaneously — no duplicate work required.

Understanding the controls list

When you open Controls, you see all controls organized by category, sorted so that categories with the lowest average maturity appear first. Within each category, not-started controls appear before in-progress ones. Each control row shows:
  • Control key — a unique identifier (for example, SUC-12)
  • Title — a short description of what the control covers
  • Category — one of 16 domains such as Access Control, Data Protection, or Incident Response
  • Severity — 1 to 5, described below
  • Status — not started, in progress, implemented, or not applicable
  • Maturity — your self-assessed implementation level from 1 to 5
  • Evidence count — the number of evidence items linked to this control

Filtering controls

Use the filter bar at the top to narrow the list:
Choose Not Started, In Progress, or Implemented to focus on a specific lifecycle stage. Selecting All Status removes the filter.

The severity scale

Severity reflects how critical a control is to your overall security posture.
SeverityLabelPriority
5CriticalRequired — address first
4HighHigh priority
3MediumStandard priority
2LowAddress when capacity allows
1MinimalNice to have
Focus on severity 5 (Critical) controls first. These have the largest impact on your risk score and are typically required by your compliance baseline profile. Unimplemented severity-5 controls are flagged in the Tasks page.

Implementing a control

Click any control row to open the control drawer and take action.
1

Update the status

In the control drawer, change the status to reflect where you are:
  • Not started — no work has begun
  • In progress — implementation is underway but not complete
  • Implemented — the control is fully in place
  • Not applicable — this control does not apply to your environment
Changing status immediately recalculates your risk score.
2

Set the maturity level

Rate your implementation maturity on the 1–5 scale:
LevelMeaning
1Initial — ad hoc, undocumented
2Developing — partially documented
3Defined — documented and consistent
4Managed — measured and monitored
5Optimized — continuously improved
Higher maturity amplifies a control’s contribution to your risk score. A control marked Implemented at maturity 1 contributes less than the same control at maturity 4.
3

Link evidence

Click Link Evidence to attach one or more existing evidence items to the control, or upload a new item directly from the drawer. Evidence types include screenshots, PDFs, policies, audit reports, config exports, and attestations.Once evidence is linked and validated by an owner or admin, the control’s effective maturity updates. Effective maturity is what actually counts toward your score.

Automated evidence from integrations

If you have connected integrations (such as AWS Security Hub or Microsoft Secure Score), some controls may already have automated evidence attached. These appear with a provider badge and a “last collected” timestamp. You can supplement automated evidence with manual uploads.

Stats bar

The five stat tiles at the top of the Controls page give you a quick overview:
  • Total — all controls in your library
  • Implemented — controls with status = implemented
  • In Progress — controls actively being worked on
  • Not Started — controls with no work begun (shown in red when above 20)
  • Avg Maturity — the average maturity rating across all controls, out of 5
Use the Not Started filter alongside the severity filter to build a prioritized remediation queue. Start with severity 5 not-started controls — these are the highest-impact tasks in your program.