Skip to content

Control Governance

Control governance illustration

The GOVERNANCE tab holds the governance record for one in-scope control. It shows why the control is an obligation, the maturity level it must reach, and whether it is material. It also shows the procedure that operates it, its open deficiencies, any compensating controls, and when it was last validated. Use it when you set a control’s priority, defend an exclusion, or prepare evidence for a governing body or auditor.

These features support the SCRMS Prioritized Implementation Guide (PIG). Each section below lists the PIG steps it helps with.

  1. Open Control Library in the sidebar (under CONTROLS & FRAMEWORKS).
  2. Open a control that is in scope. The In Scope view lists only those. In the Full Library view, click Open implementation record on an in-scope control.
  3. In the Implementation record panel on the right, select the GOVERNANCE tab. If the panel is closed, click Implementation record to open it.

The tab has seven panels, in this order: Obligation basis, Target maturity, Materiality, Procedure document, Deficiencies, Compensating controls and Validation.

Everyone in the organisation can read the tab. Editors manage the day-to-day record; overrides that change a control’s obligation are for admins. See Who can change what for the full table.


Supports PIG steps 1c, 1d, 1f and 27.

A control’s obligation basis says whether you must meet it or have chosen to. It is Mandatory (MCR), Discretionary (DSR) or Unclassified. By default, the control takes the strongest basis of the classified frameworks in scope that map it. You set a framework’s basis on Framework Scoping (see Framework Management). An admin can override the basis for a single control.

  1. On the GOVERNANCE tab, find the Obligation basis panel and click Override basis.
  2. Under Basis, choose Mandatory (MCR) or Discretionary (DSR).
  3. Enter a Reason. You must give one.
  4. Click Save.

What you’ll see: the badge shows the new basis, and the line under it reads “Set on this control:” followed by your reason. The control’s MCR or DSR badge in the Control Library list changes to match.

  1. Click Change override.
  2. Under Basis, choose Derive from frameworks (no override).
  3. Click Save.

The control takes its basis from the frameworks again. If no classified framework maps it, the panel suggests classifying frameworks under Framework Scoping.

Who can do it: admins only.

Common refusals

MessageWhat to do
A basis override needs a reason.Fill in Reason before you save.
This control has no scope record yet, so it has no obligation basis.Add the control to scope first.

Supports PIG steps 1g and 30.

The target maturity is the C|P-CMM level the control should reach. Every in-scope control inherits the target set for its domain. For example, a control in the GOV domain inherits the GOV domain’s target. An admin can override the target for a single control and must give a reason.

  1. Open Org Settings in the sidebar (under ADMIN) and go to MATURITY TARGETS.
  2. For each domain, pick a level from L0 - Initial to L5 - Optimized, or No target.
  3. Click Save maturity targets.

What you’ll see: the toast “Maturity targets saved”, and the count of domains with a target updates. Every control in that domain without its own override now shows the new target.

Who can do it: admins. Other members can read the targets. They see “Only an organisation administrator can change maturity targets.”

  1. On the GOVERNANCE tab, find the Target maturity panel and click Override target.
  2. Under Target, pick a level.
  3. Enter a Reason.
  4. Click Save.

What you’ll see: the panel shows the level (for example, L5 - Optimized) and “Set on this control:” followed by your reason. Without an override, the panel says the target is inherited from the domain target set in Org Settings.

  1. Click Change override.
  2. Choose the first option, “Inherit the … domain target (no override)”. It names the control’s domain.
  3. Click Save.

Who can do it: admins only. Overriding a control’s target departs from the domain target, so it needs the same role as setting domain targets.

Common refusals

MessageWhat to do
A target override needs a reason.Fill in Reason.
Neither this control nor the … domain has a target.Set a domain target under MATURITY TARGETS, or override the target on the control.
This control has no scope record yet, so it has no target maturity.Add the control to scope first.

Supports PIG steps 3c, 5b and 2d.

A material control is one your organisation cannot let drop quietly. A control is Material by default when its catalogue weighting is 10. An admin can override that either way and must give a reason. The admin is recorded as the approver.

What being material changes:

  • Only an admin can exclude a material control from scope or mark it not applicable. An editor who tries is refused with “Excluding a material control needs an admin of this organisation” or ”… is a material control. Marking it not applicable needs an organisation admin …”.
  • Removing a framework that would take a material control out of scope needs an admin and a change rationale.
  • A compensating control for a material control must name an accepted risk with an approval in force (see Compensating controls).
  1. On the GOVERNANCE tab, find the Materiality panel and click Override materiality.
  2. Under Override, choose Material or Not material.
  3. Enter a Reason.
  4. Click Save.

What you’ll see: the badge reads Material or Not material, with “Set on this control:” followed by your reason. Without an override, the panel explains the default, for example “Material by default: its catalogue weighting is 10.”

  1. Click Change override.
  2. Choose None: follow the catalogue weighting.
  3. Click Save.

If you change the choice, the reason box empties. A reason argues for one value, so it never carries over to another. Suppose you clear a Material override on a control weighted below 10. That makes the control not material, so you are asked for a new reason before you can save.

Who can do it: admins only. The change is recorded against the admin’s own account. An admin acting through an API key with no user account is refused.

Common refusals

MessageWhat to do
A materiality override needs a reason.Fill in Reason.
Clearing this override makes the control not material, so it needs a reason.Explain why the control is no longer material.
Save stays greyed outNothing has changed yet. Change the choice or the reason.
This control has no scope record yet, so its materiality cannot be overridden.Add the control to scope first.

Supports PIG steps 3c, 5b and 2d.

Link the approved procedure that describes how the control is operated. Only procedure documents that are approved or published can be linked.

  1. On the GOVERNANCE tab, find the Procedure document panel and click Link procedure.
  2. Under Document, pick a procedure. The list shows only approved or published procedures.
  3. Click Save.

What you’ll see: the procedure’s title and its status. To change or remove the link later, click Change procedure and pick another document or No procedure linked.

Who can do it: editors and admins.

Common situations

What you seeWhat to do
No approved or published procedure documents yet.Approve a procedure under Generated Documents, then link it.
This procedure has changed since it was linked and needs signing off again under Generated Documents.Someone edited the procedure after it was linked, which sent it back for review. The link stays. Approve the new version under Generated Documents.

Supports PIG steps 3f, 8–26, 27 and 28.

The Deficiencies panel lists the deficiencies raised against this control, open and closed. It shows a count line such as “2 open · 1 overdue · 3 closed”. Click Raise deficiency to raise one with the control already filled in. Editing, completing, cancelling and reopening work here as they do on the Deficiencies page.

Who can do it: viewers can read the panel. Only editors and admins can raise or change a deficiency.

For the full workflow, see Deficiencies (POA&M).


Supports PIG steps 6f and 27.

Record a compensating control when this control has a gap and something else reduces the risk. Each record states the gap, what compensates for it, how effective it is, and the risk it addresses.

  1. On the GOVERNANCE tab, find the Compensating controls panel and click Record compensating control.
  2. Fill in Gap (what the control does not meet) and Compensating control (what compensates for it).
  3. Choose the Effectiveness: Full, Partial or Minimal.
  4. Under Risk, choose the risk this compensation addresses. The list shows assessed risks linked to this control, with each risk’s acceptance state.
  5. Optionally, add Risk reduction notes.
  6. Click Record.

On a material control, the risk is required. Only risks that are accepted with an approval in force can be chosen; the others are shown but greyed out. If none qualifies, accept a risk in the Risk Register first, or link a risk to the control.

What you’ll see: a new row with an effectiveness chip, an acceptance chip, the gap and compensation text, and a link to the risk.

ChipMeaning
Risk accepted · approvedThe named risk is accepted, with an approval in force.
Accepted · not approvedThe risk is accepted but has no approval.
Acceptance expiredThe approval has lapsed.
Risk not accepted / Risk not assessed / Risk no longer linkedThe risk does not currently support the record.
No risk namedThe record names no risk.
Not accepted, or no longer linkedThe risk has no acceptance in force, and the panel could not read the control’s risk links to say why (for example, while they are still loading). Check the risk on the Risk Register.
Not justifiedThe control is material, and this record has no accepted risk with an approval in force.

The Not justified flag updates as things change. For example, it appears if an acceptance lapses or the control becomes material.

  • Edit: click Edit on the row, change what you need, then click Save.
  • Withdraw: click Withdraw on the row and confirm. Withdrawing deletes the record. Only the audit log keeps what it said.

Who can do it: editors and admins. Viewers see “Only an editor or admin can record or change a compensating control.”

Common refusals

MessageWhat to do
… is a material control: compensating for it needs an accepted risk linked to it with an approval in force …Name a qualifying risk. Accept and approve one in the Risk Register first if none exists.
… is not a risk linked to …Link the risk to the control, or choose a linked one.
… is not a risk this organisation has assessedAssess the risk in the Risk Register first.

Supports PIG steps 2c, 27, 28 and 30.

The Validation panel shows when this control was last checked to be working and when the next check is due. The Cadence is the control’s validation cadence, normally the SCF catalogue’s. The platform can date four cadences: annual, semi-annual, quarterly and monthly.

StateMeaning
CurrentValidated within its cadence.
Due soonThe next validation is due within 30 days.
OverdueThe next validation is past its due date.
Never validatedNo validation has been recorded.
Cadence unknownThe control has no cadence the platform can date, so no next date can be given.

Only Current and Due soon count as validated within cadence.

  1. On the GOVERNANCE tab, find the Validation panel and click Record validation.
  2. In What was checked and what was found, describe the check and its result. For example: “Sampled ten joiners against HR records; all had approved access requests.”
  3. Click Record.

What you’ll see: the toast “Validation recorded”. The state changes to Current (on a monthly cadence it can show Due soon straight away, because the next due date falls inside the 30-day window), Last validated shows today’s date and your name, and Next due moves one cadence ahead. If the cadence is unknown, the state stays Cadence unknown.

Who can do it: editors and admins. Viewers see “Only an editor or admin can record a validation.”

Common refusals

MessageWhat to do
This control is not in scope, so it has no validation schedule.Add the control to scope first.
Record stays greyed outEnter a note. You can’t record a validation without one.

ValueDefaultOverride
Obligation basisStrongest basis among classified in-scope frameworks that map the controlAdmin, per control, with a reason
Target maturityThe domain’s target in Org Settings → MATURITY TARGETSAdmin, per control, with a reason
MaterialityMaterial when the catalogue weighting is 10Admin, per control, with a reason
Validation cadenceThe SCF catalogue’s cadenceNot set on this tab

Every change on this tab is written to the Audit Log.

Everyone in the organisation can read the tab. The table shows who can change each part. Without the right role, the button is not shown. The server checks the role again when you save.

PanelViewerEditorAdmin
Obligation basis overrideReadReadChange
Target maturity overrideReadReadChange
Materiality overrideReadReadChange
Procedure documentReadChangeChange
DeficienciesReadChangeChange
Compensating controlsReadChangeChange
ValidationReadRecordRecord

Editors manage the day-to-day record. The decisions that change a control’s obligation are left to admins.

PanelWhat an editor sees
Obligation basis, Target maturity, MaterialityThe current value and where it comes from. There is no Override basis, Override target or Override materiality button.
Procedure documentLink procedure or Change procedure, as for an admin.
Deficiencies, Compensating controls, ValidationThe same buttons as an admin.
Org Settings → MATURITY TARGETSThe targets, with the level lists greyed out and the line “Only an organisation administrator can change maturity targets.”

Viewers see every panel read-only. The Deficiencies, Compensating controls and Validation panels add a line saying only an editor or admin can make changes.

If you are an editor and need an override, ask an organisation admin to make it. The admin is recorded as the person who made the change.