Retain a usable operating baseline
Keep the records someone needs to understand a scan or review without repeating the investigation. For each onboarded application, retain its scanner profiles and project scope, the source revision, the relevant pipeline and scanner jobs, and any findings assigned for action. Record the owner and review date for exclusions or unsupported parts of the application.
- In Secure > Security configuration > Scanners, open each scanner's details and record the project's profile source, status and last scan. Use Secure > Security inventory to review coverage across the group.
- In the project's Build > Pipelines, open the pipeline for the change or default-branch revision being reviewed. Keep its URL and SHA, each relevant scanner job's outcome, and the job log needed to explain any failure or exclusion.
- Where retention requires the original scanner output, use the job's artifact browser or Build > Artifacts to download it before expiry. Keep each job's files separately. The job artifacts documentation explains access and expiration; a pipeline link alone won't preserve expired files.
- Keep real findings linked to their triage decisions and remediation merge requests. For DAP, include the review threads or assessment, the flow session when available, and the human decision. After deployment, link the fix to the artifact and environment that actually received it.
Store these records in the organization's approved access-controlled location with the required retention and protection against alteration. Missing output needs investigation; a later successful run doesn't reconstruct an earlier missing result.
Maintain the service runbook
Keep the information an operator will need to change or recover the service alongside its operating procedures:
- The service owner, policy administrator, release operator and incident contacts.
- Where application, policy, runner and deployment configuration are maintained, and who can change them.
- How to find a release's source revision, pipeline, artifact digest, approval and current deployment.
- How credentials are issued, rotated and revoked, including the responsible owner and recovery access.
- How to stop current work, suspend a release and restore an approved artifact.
- Where logs and release records are retained, who can access them and when they expire.
- Known limitations, the person responsible for each, and changes that require another review.
Turn the local release result into production work with the release and platform owners. They need to define the production artifact store and immutable reference, build provenance source, signing identity and key custody, promotion rule, deployer identity, target readback and rollback source. Exercise that actual path with an approved artifact, then connect its source revision, pipeline, provenance, digest, release decision, deployment record and runtime identity in the runbook. Until those records agree, the local signing walkthrough remains a practice result rather than production provenance.
Likewise, assign the Audit and response owners to configure the streams, retention and access needed for consequential actions in GitLab and every connected system. Trace one ordinary deployment and one harmless response exercise across those records. Record missing events or identities as specific integration work; an incident-time API export can't substitute for monitoring that was never configured.
Use your existing service-management and incident processes for these records. After an incident, measure time to containment and time to verified remediation separately because they answer different questions. Containment ends when the affected activity has stopped across the systems in scope. Verified remediation requires the corrected software or configuration to be present there, with security, functional, and health checks complete. A revoked token or merged fix alone doesn't establish recovery.
Recheck the part that changed
Use the operating baseline to choose a focused check after a change:
| Change | Practical recheck | Decision to retain |
|---|---|---|
| Scanner profile, language, dependency input, exclusions or runner | Review the affected profile and scope, then inspect scanner activity on the next normal merge-request and default-branch pipelines. Investigate missing or failed coverage. | Whether the intended sources and dependencies still receive the required scans. |
| DAP flow, agent setup, trigger or triage preset | Review the effective permissions and runner, then inspect the next review or real-finding assessment and any proposed fix with its human reviewer. | Whether the flow runs within its intended scope and its output receives the required review. |
| Application or policy membership, custom role, branch rule or policy link | Repeat the relevant paired permission checks with the actual restricted identity and trusted administrator. Inspect inherited grants as well as direct ones. | Whether the same authority separation still holds. |
| Verification or admission mechanism | Repeat the permitted change and the prohibited path affected by the change, including the target readback. | Whether admission still depends on the required independent verification. |
| Credential, task runtime or response procedure | Exercise the affected stop/revocation path and confirm its observed reach before resuming delegated work. | Which activity was stopped and which systems still need a response. |
| Artifact, promotion or deployment path | Follow the accepted artifact through the changed path and verify its digest and health in the affected environments. | Which deployments are verified and which remain unresolved. |
Keep the earlier record and create a new one for the recheck. When a formerly prohibited action succeeds, record that result before restoring the control. A later successful check doesn't erase the interval when the control was ineffective. Where the detailed procedure is still being established, keep that outcome open instead of substituting a settings inspection for a behavior check.
Review the workflow's delegated authority
Services, permissions, delivery paths, threats, product behavior, and owners all change over time. Give each workflow a maintenance owner and a review rhythm that fits its impact. Recheck after a change to policy, identity, runner, build environment, registry, deployment path, agent, tool, integration, or affected service. Also recheck after a bypass, incident, failed recovery, unexplained result, or expired exception.
Product versions matter when they change a capability the workflow relies on, but a version difference alone doesn't require repeating every assessment. Focus the review on permissions, behavior, availability, and failure modes that changed, while retaining the earlier results that still apply.
Use operating results to decide whether autonomy should expand, remain in place, or narrow. Useful signals include missing or incomplete scans, time to review urgent findings, failed boundary tests, interventions, unexplained actions, expired exceptions, deployment gaps, and recovery exercises. Read counts in context: a falling vulnerability total may reflect fixes, dismissals, or reduced scan coverage.
Keep a short decision record for the workflow. For the Foundation and each stage, link the observed result, record whether the outcome is demonstrated, and identify any gap and its owner. Then name the autonomy level those results support. A stage that isn't required for the chosen level can remain pending; a required stage can't be marked complete merely because a product feature is configured.
When considering an authority increase, compare the recorded results with the Standard's prerequisites. Exercise the additional permissions, failure cases, volume limits, and affected-system limits before enabling them. Success in preparing code changes doesn't establish permission to alter security policy, release to production, or revoke credentials.
A waived check, successful prohibited action, or failed intervention changes that decision. Restrict the workflow to authority whose prerequisites remain demonstrated. If the Foundation or Authorize is unproven, even Suggest hasn't met the Standard's prerequisites. Assign the gap, correct the policy or implementation, and repeat the relevant checks before restoring delegated authority.
Apply improvements one workflow or environment at a time. Keep the official Standard's Foundation and five stages as the outcomes being pursued, while letting the service, risk, and operating context determine the practical controls. The result should remain concrete: a clear owner, an authorized task, contained reach, trustworthy verification, the same approved software in release, and a response path that works when needed.