Skip to content

Running a PIG-aligned engagement

PIG engagement illustration

The SCRMS Prioritized Implementation Guide (PIG) sets out a prioritised path for building a cybersecurity and data protection programme on the Secure Controls Framework. This page shows where you record each PIG decision in the platform, and which journey checks confirm it has been made.

  • Your journey carries the flow. The platform does not set the order of an engagement. You import a journey template that follows the PIG, and each stage lists the checks that must pass before a practitioner signs it off. See Journey.
  • The catalogue already matches the PIG. When the platform was checked against PIG v2026.1 (platform v0.45.0), every control in PIG Appendix A carried the same weighting and validation cadence, and every Appendix B evidence request ID was present. You don’t enter any of that.
  • What you record is your organisation’s decisions. That means why a control is in scope, what is material, what is deficient, what risk you accept, and what the board has reviewed. The rest of this page shows where each of those decisions lives.
  1. Scope your frameworks. In Framework Scoping, select the frameworks you must or choose to meet. An organisation admin then uses Set basis to mark each one as mandatory (MCR) or discretionary (DSR). See Framework Management.
  2. Import your PIG journey. No PIG template ships with the platform. Use a template your practice maintains; the check types it can use are listed in Journey.
  3. Set maturity targets. An organisation admin sets a target maturity in Org Settings for each domain you are working on. Controls inherit it. See Control Governance.
  4. Record your systems. In Systems Registry, give each system its boundary, criticality and recovery objectives.
PIG stepsWhat you recordWhere in the platformJourney checks that confirm it
1a, 1f, 4a, 4c, 4f, 4g, 7c, 7eSystem boundary, criticality, recovery objectives, data classification and hosting; vendor data location and responsibilitiesSystems Registry, Vendor Inventorysystems_with_criticality (systems only)
1c, 1d, 1f, 27Why each framework, and each control, is in scope (MCR or DSR)Framework Scoping → Set basis; control GOVERNANCE tabframeworks_with_basis, controls_with_basis
1e, 2a, 30The approved control set (your Statement of Applicability, pinned as the Living Control Set revision)Generated Documentsdocuments_approved with a generator filter
1g, 30Target maturity per domain, with per-control overridesOrg Settings; control GOVERNANCE tabcontrols_with_target, controls_at_target
2d, 3c, 5bWhich controls are material, the procedure document that operates each, and working through them in weighting orderControl GOVERNANCE tab; Control Library filtersmaterial_controls_at_status
2b, 3b, 3e, 28Risk you accept, with an approver and an expiry dateRisk Register → a risk → Risk acceptancerisks_accepted_without_approver_max
3f, 8–26, 27, 28Each control deficiency, its owner, due date and closure (POA&M)Deficiencies (POA&M)open_deficiencies_max, material_deficiencies_max
6f, 27Compensating controls for a deficient or material controlControl GOVERNANCE tab—
2c, 27, 28, 30When each control was last validated against its cadence; monthly posture snapshots; the Governance Oversight ReportControl GOVERNANCE tab; Dashboard; Generated Documentscontrols_validated_within_cadence; documents_approved with generator: "governance-report" and within_days
29Capability tests and their findingsCapability Testscapability_tests_within_days

Steps 8–26 are where controls are actually implemented. Use the existing control, evidence and task features for that work, and raise a deficiency whenever a control falls short. See Control Management and Evidence Management.

  1. Scope frameworks and set their basis.
  2. Override the basis on individual controls only where a contract or regulation reaches a single control.
  3. Set domain maturity targets.
  4. Review which controls are material. Controls with a catalogue weighting of 10 are material by default; override only with a reason.
  5. Record your systems and vendors.
  6. Record risk acceptances, each with an approver and an expiry date.
  7. Link the procedure document that operates each material control.
  8. Where a control can’t be met, record a compensating control on its GOVERNANCE tab (step 6f).
  9. Approve your Statement of Applicability so it stands as the Living Control Set revision.
  1. Work through controls in Control Library, with ORDER set to Material first, then weighting.
  2. Raise a deficiency in Deficiencies (POA&M) for every gap you find, with an owner and a due date.
  1. Record a validation on each control when its cadence comes due. Where scheduled notifications are enabled, the notification bell tells you when one is due.
  2. Take the month’s posture snapshot from the Dashboard.
  3. Generate the Governance Oversight Report for the board.
  4. Record capability tests, and add a finding for anything that failed.
  5. Close deficiencies with a retest note.
ActionViewerEditorAdmin
Read every PIG recordYesYesYes
Raise and close deficiencies; record capability tests, compensating controls and validations; link a procedure document; take the posture snapshotNoYesYes
Set a framework or control basis, set target maturity, override materiality, accept a riskNoNoYes
Remove an MCR framework, an MCR control or a material control from scopeNoNoYes
Attest a journey stageNoYesYes
Import or re-issue a journey templateNoNoYes
Generate a document and submit it for reviewNoYesYes
Approve or publish a document, such as the Statement of Applicability or the Governance Oversight ReportNoNoYes

The feature guides give the exact rules for each action.