OGRL Standard Library · bundle--ogrl-library

Open framework & control catalog.

Standard operational controls, starter baselines, library tests, reviewed multi-framework crosswalks, and normalized requirements with NIST assessment objectives. Authoritative YAML sources live in ogrl-library and are built and validated by ogrl-rs.

Bundle bundle--ogrl-library
Version 0.3.0
Frameworks 4
Standard controls 113
Baselines 4
Library tests 12
Requirements 1,395 (215 withdrawn)
Objectives 3,203
Mappings 810 (413 reviewed)
Projection digest sha-256:5f96dd185fd5…

Published Frameworks (4)

Starter Baselines (4)

Library baseline 12 controls
OGRL Core Security Baseline
baseline--ogrl-core
4 framework(s) Multi-framework core
Library baseline 8 controls
OGRL ISO/IEC 27001:2022 Starter Baseline
baseline--ogrl-iso27001
1 framework(s) 8 pinned requirements
Library baseline 9 controls
OGRL NIST SP 800-171 Rev 3 Core Baseline
baseline--ogrl-nist-800-171-r3
1 framework(s) 8 pinned requirements
Library baseline 113 controls
OGRL SOC 2 Baseline
baseline--ogrl-soc2
1 framework(s) 61 pinned requirements

Standard Controls (113)

OGRL-AC-01 Account Provisioning and Lifecycle Governance ac preventive event-driven 6 crosswalks
control--ogrl-ac-01 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Approve every user and service account request through {{ approver_role }} prior to provisioning, and revoke or disable accounts within {{ deprovision_sla }} of personnel termination or role change.

Objective

Ensure only authorized personnel and services hold active accounts on in-scope systems.

Implementation guidance

Integrate the identity provider with HR lifecycle events so terminations automatically trigger session revocation and account suspension within the defined SLA.

Parameters (2)

  • {{ approver_role }} — Account approval authority (default: the system owner or manager)
  • {{ deprovision_sla }} — Termination deprovisioning SLA (default: 24 hours)

Library tests (1)

  • automated · daily · required — Verify Account Provisioning Approvals and Termination Revocation: Confirm newly provisioned accounts have linked approval tickets and all terminated personnel accounts were disabled within the configured deprovisioning SLA.

Reviewed framework crosswalks (6)

  • equivalent-to → requirement--iso-iec-27001-2022-a-5-16 reviewed
  • subset-of → requirement--nist-sp-800-171-r3-03-01-01 reviewed (maps a_03_01_01_odp_01←approver_role, a_03_01_01_odp_04←deprovision_sla)
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-2#e reviewed (maps ac_02_odp_03←approver_role)
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-2#h.2 reviewed (maps ac_02_odp_07←deprovision_sla)
  • equivalent-to → requirement--soc2-tsc-2017-cc6-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-3 reviewed
OGRL-AC-02 Periodic User Access Review ac detective quarterly 5 crosswalks
control--ogrl-ac-02 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Review all active user accounts, privileged roles, and service accounts {{ review_cadence }} and remediate unauthorized or unneeded entitlements within {{ remediation_window }}.

Objective

Detect and remove privilege creep, orphaned accounts, and stale entitlements before misuse.

Implementation guidance

Generate account rosters directly from authoritative identity providers and production systems, require reviewer sign-off from managers or system owners, and retain ticketed removal evidence.

Parameters (2)

  • {{ remediation_window }} — Revocation remediation window (default: 5 business days)
  • {{ review_cadence }} — Access review cadence (default: at least quarterly)

Library tests (1)

  • manual · quarterly · required — Verify Quarterly Access Review Completion: Examine completed quarterly user access review records to confirm reviewer sign-off and timely removal of revoked entitlements.

Reviewed framework crosswalks (5)

  • equivalent-to → requirement--iso-iec-27001-2022-a-5-18 reviewed
  • subset-of → requirement--nist-sp-800-171-r3-03-01-01 reviewed (maps a_03_01_01_odp_06←review_cadence)
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-2#j reviewed (maps ac_02_odp_10←review_cadence)
  • intersects-with → requirement--soc2-tsc-2017-cc6-2 reviewed
  • equivalent-to → requirement--soc2-tsc-2017-cc6-3 reviewed
OGRL-AC-03 Least Privilege and Role-Based Access Enforcement ac preventive continuous 6 crosswalks
control--ogrl-ac-03 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Restrict logical access to systems, administrative interfaces, and sensitive data using role-based access control scoped to least privilege, requiring {{ privileged_elevation }} for administrative actions.

Objective

Limit blast radius by preventing unauthorized read, write, or administrative operations.

Implementation guidance

Avoid standing administrative privileges on production environments; use scoped IAM roles, just-in-time elevation, and separation between developer and production-deployment permissions.

Parameters (1)

  • {{ privileged_elevation }} — Privileged elevation mechanism (default: time-bound just-in-time elevation)

Library tests (1)

  • automated · daily · required — Verify Least-Privilege Role Assignments: Check IAM role bindings and administrative group memberships to verify no unauthorized wildcard permissions or standing administrative privileges exist.

Reviewed framework crosswalks (6)

  • equivalent-to → requirement--iso-iec-27001-2022-a-5-15 reviewed
  • equivalent-to → requirement--nist-sp-800-171-r3-03-01-05 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-3 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-6 reviewed
  • equivalent-to → requirement--soc2-tsc-2017-cc6-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-3 reviewed
OGRL-AC-04 Network Boundary and Logical Access Restriction ac preventive continuous 2 crosswalks
control--ogrl-ac-04 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Enforce default-deny network ingress policies at system boundaries, allowing only explicitly documented service ports and restricting administrative access to {{ admin_access_path }}.

Objective

Prevent unauthorized network traffic and direct internet exposure of internal or administrative services.

Implementation guidance

Manage security groups, firewall rules, and private network peering via infrastructure-as-code with automated drift detection.

Parameters (1)

  • {{ admin_access_path }} — Authorized administrative network path (default: authenticated VPN or zero-trust bastion endpoints)

Library tests (1)

  • automated · daily · required — Verify Default-Deny Network Ingress Policies: Inspect cloud security groups and firewall rules to confirm administrative ports (SSH, RDP, database ports) are not exposed to 0.0.0.0/0.

Reviewed framework crosswalks (2)

  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
  • equivalent-to → requirement--soc2-tsc-2017-cc6-6 reviewed
OGRL-AC-05 Multi-Factor Authentication Enforcement ac preventive continuous 4 crosswalks
control--ogrl-ac-05 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Enforce {{ mfa_standard }} multi-factor authentication on all interactive workforce, remote, and privileged accounts across identity providers and in-scope systems.

Objective

Prevent account compromise from stolen, reused, or phished single-factor credentials.

Implementation guidance

Prefer FIDO2/WebAuthn security keys or platform authenticators for privileged accounts, and block legacy single-factor protocols.

Parameters (1)

  • {{ mfa_standard }} — Required MFA factor strength (default: phishing-resistant (FIDO2/WebAuthn or TOTP))

Library tests (1)

  • automated · daily · required — Verify MFA Enforcement on All Active Accounts: Query the identity provider and cloud IAM directories to confirm MFA is enrolled and enforced for 100% of active interactive accounts.

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--iso-iec-27001-2022-a-8-5 reviewed
  • equivalent-to → requirement--nist-sp-800-171-r3-03-05-03 reviewed
  • superset-of → requirement--nist-sp-800-53-r5-ia-2 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc6-1 reviewed
OGRL-AC-06 Secret and Authenticator Lifecycle Management ac preventive quarterly 3 crosswalks
control--ogrl-ac-06 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Manage passwords, API keys, and cryptographic credentials in an approved secrets vault, rotate non-ephemeral credentials at least every {{ rotation_period }}, and revoke immediately upon {{ revocation_triggers }}.

Objective

Protect authenticators from unauthorized disclosure and limit exposure windows if leaked.

Implementation guidance

Prefer short-lived workload identities (OIDC/IAM roles) over static API keys, run secret scanning on source repositories, and replace default credentials prior to deployment.

Parameters (2)

  • {{ revocation_triggers }} — Immediate revocation events (default: suspected exposure, personnel departure, or system decommission)
  • {{ rotation_period }} — Maximum static credential lifetime (default: 90 days)

Library tests (1)

  • automated · weekly · required — Verify Secret Vaulting and Credential Rotation Age: Confirm static API keys and service credentials do not exceed the configured rotation age and repository secret scanning reports zero unresolved leaks.

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--iso-iec-27001-2022-a-5-17 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ia-5#f reviewed (maps ia_05_odp_01←rotation_period, ia_05_odp_02←revocation_triggers)
  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
OGRL-AC-07 Privileged Access Management ac preventive continuous 7 crosswalks
control--ogrl-ac-07 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain an approved roster of individuals authorized to hold administrative access to {{ privileged_scope }}, limited to {{ privileged_roles }}; require those individuals to use dedicated privileged accounts or elevated roles that are not used for email, browsing, or other routine work; alert {{ privileged_alert_recipient }} on every grant of a privileged role and every change to a privileged role definition; and reconcile actual privileged assignments against the roster {{ privileged_review_frequency }}, removing any that are not approved.

Objective

Keep the set of people who can alter security configurations, production systems, or audit data small, known, and monitored.

Implementation guidance

Define privileged roles in the identity provider and cloud IAM and treat cloud root, organization admin, IdP super-admin, database superuser, and security tooling admin as in scope. Use separate admin identities or just-in-time role elevation (see OGRL-AC-03) instead of permanently privileged daily accounts. Stream IAM and IdP role-change events to the SIEM for alerting, and export privileged group membership for the reconciliation. Break-glass accounts belong on the roster with sealed credentials and alerting on use.

Parameters (4)

  • {{ privileged_alert_recipient }} — Recipient of privileged change alerts (default: the security team)
  • {{ privileged_review_frequency }} — Privileged roster reconciliation frequency (default: monthly)
  • {{ privileged_roles }} — Personnel eligible for privileged access (default: named members of the infrastructure and security teams)
  • {{ privileged_scope }} — Systems and functions treated as privileged (default: cloud provider organizations, identity provider administration, production databases, and security tooling )

Reviewed framework crosswalks (7)

  • equivalent-to → requirement--nist-sp-800-53-r5-ac-2-7 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-6-1 reviewed (maps ac_06_01_odp_01←privileged_roles)
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-6-2 reviewed (maps ac_06_02_odp←privileged_scope)
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-6-5 reviewed (maps ac_06_05_odp←privileged_roles)
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-6-7 reviewed (maps ac_06_07_odp_01←privileged_review_frequency, ac_06_07_odp_02←privileged_roles)
  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-3 reviewed
OGRL-AC-08 Separation of Duties ac preventive continuous 3 crosswalks
control--ogrl-ac-08 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Document the duties that must be separated, including at minimum {{ separated_duties }}, configure system access so that no single individual can perform both duties in a conflicting pair without independent approval, and record any approved exception together with its compensating control.

Objective

Prevent a single individual from introducing and concealing unauthorized or erroneous changes.

Implementation guidance

Enforce separation technically where possible: branch protection requiring a reviewer other than the author, access-request workflows that block self-approval, and audit log storage that system administrators cannot modify. Small teams that cannot fully separate duties should document compensating detective controls such as after-the-fact review of administrator activity.

Parameters (1)

  • {{ separated_duties }} — Duties that must be separated (default: authoring and approving production code changes, requesting and approving access grants, and administering systems and reviewing their audit logs )

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-ac-5 reviewed (maps ac_05_odp←separated_duties)
  • intersects-with → requirement--soc2-tsc-2017-cc5-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-3 reviewed
OGRL-AC-09 Inactive and Temporary Account Disablement ac preventive daily 3 crosswalks
control--ogrl-ac-09 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Automatically disable user accounts that have been inactive for {{ inactivity_period }}; disable accounts that have expired, are no longer associated with an active individual, or violate policy within {{ disable_window }} of detection; and configure temporary and emergency accounts to be {{ temporary_account_action }} automatically after {{ temporary_account_lifetime }}.

Objective

Eliminate dormant and leftover accounts that could be used for unauthorized access.

Implementation guidance

Use identity provider inactivity policies or a scheduled job that compares last-login data from the IdP and directly-managed systems against the threshold. Set expiration dates on contractor, vendor-support, and break-glass accounts at creation. Service accounts are excluded from the inactivity rule but must have an owner and appear in access reviews (OGRL-AC-02).

Parameters (4)

  • {{ disable_window }} — Time to disable expired, orphaned, or non-compliant accounts (default: 24 hours)
  • {{ inactivity_period }} — Inactivity threshold (default: 90 days)
  • {{ temporary_account_action }} — Automatic action for temporary accounts (default: disabled or removed)
  • {{ temporary_account_lifetime }} — Maximum temporary or emergency account lifetime (default: the approved expiration date, not to exceed 30 days)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-ac-2-2 reviewed (maps ac_02_02_odp_01←temporary_account_action, ac_02_02_odp_02←temporary_account_lifetime)
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-2-3 reviewed (maps ac_02_03_odp_01←disable_window, ac_02_03_odp_02←inactivity_period)
  • intersects-with → requirement--soc2-tsc-2017-cc6-2 reviewed
OGRL-AC-10 Session Lock and Termination ac preventive continuous 3 crosswalks
control--ogrl-ac-10 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Configure workforce endpoints to lock the screen after {{ device_lock_timeout }} of inactivity, requiring re-authentication to unlock, and configure in-scope applications, administrative consoles, and remote access sessions to terminate after {{ session_termination_conditions }}.

Objective

Prevent unattended or hijacked sessions from being used to access systems and data.

Implementation guidance

Enforce screen lock through MDM configuration profiles and session lifetimes through identity provider and cloud console session policies. Apply shorter timeouts to production and administrative access than to collaboration tools. Evidence is typically the MDM profile, IdP session policy, and cloud console session settings.

Parameters (2)

  • {{ device_lock_timeout }} — Endpoint inactivity lock timeout (default: 15 minutes)
  • {{ session_termination_conditions }} — Session termination conditions (default: 30 minutes of inactivity or 12 hours of total session duration)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-ac-11 reviewed (maps ac_11_odp_02←device_lock_timeout)
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-12 reviewed (maps ac_12_odp←session_termination_conditions)
  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
OGRL-AC-11 Remote Access Security ac preventive continuous 3 crosswalks
control--ogrl-ac-11 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Document each permitted remote access method to in-scope systems with its usage restrictions and configuration requirements, authorize each method before it is enabled, and require all remote access to production environments to pass through {{ remote_access_gateway }} that enforces single sign-on with multi-factor authentication, encrypted transport, and session logging; review the permitted methods {{ remote_access_review_frequency }}.

Objective

Ensure remote connections to production are made only through known, approved, and monitored paths.

Implementation guidance

For cloud SaaS, remote access usually means administrative paths into production: cloud consoles and CLIs, SSH or database sessions via a bastion or identity-aware proxy, and Kubernetes API access. Prefer identity-aware proxies or SSM-style session managers over static SSH keys and public bastions. Network-level exposure restrictions are covered by OGRL-AC-04.

Parameters (2)

  • {{ remote_access_gateway }} — Approved remote access gateway (default: an approved identity-aware proxy, session manager, or VPN)
  • {{ remote_access_review_frequency }} — Remote access method review frequency (default: annually)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-ac-17 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-6 reviewed
OGRL-AC-12 Information Flow Enforcement and Tenant Data Segregation ac preventive continuous 3 crosswalks
control--ogrl-ac-12 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Enforce tenant isolation in every data path of the service so that each request, query, background job, and export is constrained to the authenticated customer's tenant at {{ isolation_enforcement_layer }}, and run automated cross-tenant access tests {{ isolation_test_trigger }}.

Objective

Prevent one customer's data from flowing to, or being accessed by, another customer.

Implementation guidance

Enforce tenancy in a shared layer rather than in each handler: row-level security, tenant-scoped repository or ORM helpers, per-tenant encryption keys, or per-tenant databases. Derive the tenant from the authenticated session, never from client-supplied parameters alone. Include cross-tenant negative tests in CI and in periodic penetration tests.

Parameters (2)

  • {{ isolation_enforcement_layer }} — Layer where tenant isolation is enforced (default: the data access layer through row-level security or mandatory tenant-scoped queries )
  • {{ isolation_test_trigger }} — When cross-tenant isolation tests run (default: on every release to production)

Reviewed framework crosswalks (3)

  • subset-of → requirement--nist-sp-800-53-r5-ac-4 reviewed
  • intersects-with → requirement--soc2-tsc-2017-c1-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
OGRL-AC-13 Unique Identification and Centralized SSO ac preventive continuous 6 crosswalks
control--ogrl-ac-13 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Assign each workforce member a unique identifier in {{ identity_provider }}, authenticate access to in-scope systems through single sign-on from that provider wherever the system supports it, prohibit shared or generic user identifiers other than inventoried service and break-glass accounts, and do not reassign a retired identifier for {{ identifier_reuse_period }}.

Objective

Make every action on in-scope systems attributable to one individual and manageable from one place.

Implementation guidance

Connect SaaS and cloud consoles to the IdP via SAML or OIDC and provision via SCIM where available. Maintain an inventory of in-scope systems that cannot use SSO, with compensating local account management. Do not recycle email addresses or usernames of departed personnel. MFA requirements are in OGRL-AC-05; account approval is in OGRL-AC-01.

Parameters (2)

  • {{ identifier_reuse_period }} — Minimum period before an identifier may be reused (default: at least two years)
  • {{ identity_provider }} — Central workforce identity provider (default: the organization's designated workforce identity provider)

Reviewed framework crosswalks (6)

  • equivalent-to → requirement--nist-sp-800-53-r5-ia-2 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ia-4#b reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ia-4#c reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ia-4#d reviewed (maps ia_04_odp_02←identifier_reuse_period)
  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-2 reviewed
OGRL-AC-14 Authenticator Strength and Lockout ac preventive continuous 3 crosswalks
control--ogrl-ac-14 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Configure every in-scope system that accepts passwords, including the identity provider and customer-facing sign-in, to enforce {{ password_composition_rules }}, permit passphrases of at least 64 characters, reject passwords found on a list of breached or commonly used values that is updated {{ blocklist_update_frequency }}, transmit passwords only over encrypted channels, store them only with a salted adaptive key derivation function, require a new password after account recovery, and lock the account or impose increasing delays after {{ max_failed_attempts }} consecutive failed attempts within {{ failed_attempt_window }}.

Objective

Resist credential guessing, stuffing, and offline cracking attacks against password-based authentication.

Implementation guidance

Follow NIST SP 800-63B: favor length and breached-password screening over composition rules and periodic forced rotation. Use a breached-password service (for example k-anonymity range queries) at creation and change. Use bcrypt, scrypt, or Argon2id for storage. Apply lockout or rate limiting per account and per source to blunt credential stuffing without enabling easy denial of service.

Parameters (4)

  • {{ blocklist_update_frequency }} — Breached-password list update frequency (default: at least monthly)
  • {{ failed_attempt_window }} — Failed-attempt counting window (default: 15 minutes)
  • {{ max_failed_attempts }} — Consecutive failed attempts before lockout (default: 10)
  • {{ password_composition_rules }} — Password composition rules (default: a minimum length of 12 characters without arbitrary character-class requirements)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-ac-7 reviewed (maps ac_07_odp_01←max_failed_attempts, ac_07_odp_02←failed_attempt_window)
  • subset-of → requirement--nist-sp-800-53-r5-ia-5-1 reviewed (maps ia_05_01_odp_01←blocklist_update_frequency, ia_05_01_odp_02←password_composition_rules)
  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
OGRL-AC-15 Customer Authentication ac preventive continuous 2 crosswalks
control--ogrl-ac-15 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Require every customer user of the service to authenticate with an individual account, offer {{ customer_mfa_options }} to all customer users and SAML or OIDC single sign-on to {{ sso_eligible_customers }}, verify the requester through a previously registered channel before completing account recovery, and invalidate active sessions on logout, password change, and account recovery.

Objective

Ensure only the intended customer users can access customer accounts and data in the service.

Implementation guidance

Use a mature authentication library or customer identity platform rather than custom code. Allow customer administrators to enforce MFA or SSO for their organization. Issue short-lived, server-revocable session tokens. API keys issued to customers should be scoped, revocable, and attributable to a customer account.

Parameters (2)

  • {{ customer_mfa_options }} — MFA options offered to customers (default: TOTP authenticator apps and WebAuthn passkeys)
  • {{ sso_eligible_customers }} — Customers offered SSO (default: all business-tier customers)

Reviewed framework crosswalks (2)

  • superset-of → requirement--nist-sp-800-53-r5-ia-8 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
OGRL-AM-01 System Component Inventory am detective continuous 3 crosswalks
control--ogrl-am-01 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain an inventory of in-scope system components, including cloud accounts, compute, data stores, network entry points, workforce endpoints, and production SaaS services, that records {{ inventory_attributes }} for each component and assigns each component to exactly one system and environment. Populate the inventory from provider APIs and device management where available, and reconcile it against those sources {{ inventory_review_frequency }}.

Objective

Every component in scope is known, owned, and accounted for once, so that it can be secured, monitored, and assessed.

Implementation guidance

Use cloud provider resource inventories, infrastructure-as-code state, MDM enrollment, and the SaaS management or SSO catalog as sources. Required tags (owner, environment, data classification) enforced by policy keep the inventory accurate. Reconciliation means investigating untagged or unknown resources and unenrolled devices. Evidence: an inventory export and reconciliation records.

Parameters (2)

  • {{ inventory_attributes }} — Inventory attributes (default: unique identifier, type, owner, environment, location or region, and data classification )
  • {{ inventory_review_frequency }} — Inventory reconciliation frequency (default: at least quarterly)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-cm-8 reviewed (maps cm_08_odp_01←inventory_attributes, cm_08_odp_02←inventory_review_frequency)
  • intersects-with → requirement--soc2-tsc-2017-cc3-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
OGRL-AM-02 Data Classification am preventive annual 3 crosswalks
control--ogrl-am-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain a data classification scheme defining {{ classification_levels }} and the handling requirements for each level, including storage, sharing, encryption, and retention. Record the classification of each in-scope data store in the component inventory, have {{ classification_approver }} approve classifications, and review the scheme and recorded classifications {{ classification_review_frequency }}.

Objective

Confidential and customer data can be located and is handled according to its sensitivity.

Implementation guidance

Three or four levels are typical, such as public, internal, confidential, and restricted, with customer data classified confidential or higher. Tag cloud data stores and buckets with their level so automated checks can enforce encryption and access rules. Evidence: the scheme, the inventory showing classifications, and the review record.

Parameters (3)

  • {{ classification_approver }} — Classification approver (default: the data owner)
  • {{ classification_levels }} — Classification levels (default: public, internal, confidential, and restricted)
  • {{ classification_review_frequency }} — Classification review frequency (default: at least annually)

Reviewed framework crosswalks (3)

  • intersects-with → requirement--nist-sp-800-53-r5-ra-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-c1-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
OGRL-BC-01 Business Continuity and Disaster Recovery Plan bc corrective annual 7 crosswalks
control--ogrl-bc-01 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain a documented business continuity and disaster recovery plan, approved by {{ plan_approver }}, that identifies critical services with their recovery time and recovery point objectives, recovery priorities, contingency roles with current contact information, and procedures for continuing operations during a disruption and fully restoring systems afterward; review and update the plan {{ plan_review_cadence }} and after significant changes or tests, and communicate changes to {{ plan_recipients }}.

Objective

Ensure the organization can sustain critical services and restore systems to normal operation within committed timeframes after a disruption.

Implementation guidance

Cover cloud-relevant scenarios such as availability zone and region outages, cloud account compromise or ransomware, loss of a critical SaaS dependency (identity provider, code hosting, payment processor), and loss of key personnel. Derive recovery objectives from the business impact analysis (OGRL-BC-07) and customer SLAs. Keep a copy accessible outside the primary environment in case SSO or the main workspace is unavailable, and restrict edit access. Align with the incident response plan (OGRL-IR-01) and fold in lessons from plan tests (OGRL-BC-02).

Parameters (3)

  • {{ plan_approver }} — Plan approval authority (default: executive leadership)
  • {{ plan_recipients }} — Recipients of plan changes (default: key contingency personnel and critical service owners)
  • {{ plan_review_cadence }} — Plan review frequency (default: at least annually)

Reviewed framework crosswalks (7)

  • subset-of → requirement--nist-sp-800-53-r5-cp-2#a reviewed (maps cp_2_prm_1←plan_approver)
  • equivalent-to → requirement--nist-sp-800-53-r5-cp-2#d reviewed (maps cp_02_odp_05←plan_review_cadence)
  • equivalent-to → requirement--nist-sp-800-53-r5-cp-2#e reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-cp-2#f reviewed (maps cp_2_prm_4←plan_recipients)
  • intersects-with → requirement--soc2-tsc-2017-a1-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-5 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc9-1 reviewed
OGRL-BC-02 Continuity and Recovery Plan Testing bc detective annual 2 crosswalks
control--ogrl-bc-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Test the business continuity and disaster recovery plan {{ dr_test_cadence }} using {{ dr_test_methods }}, document results against recovery time and recovery point objectives, have results reviewed by {{ dr_test_reviewer }}, and track identified gaps to remediation.

Objective

Demonstrate that recovery procedures work and objectives are achievable, and correct weaknesses before a real disruption.

Implementation guidance

Combine a tabletop walkthrough with a technical exercise such as promoting a database replica in another region or rebuilding an environment from infrastructure as code into a clean account. Measure actual recovery time and data loss and compare them with stated objectives. Tests may share a session with incident response tabletops (OGRL-IR-01) but keep separate results records. Feed findings back into the plan (OGRL-BC-01).

Parameters (3)

  • {{ dr_test_cadence }} — Plan test frequency (default: at least annually)
  • {{ dr_test_methods }} — Plan test methods (default: a tabletop walkthrough and a technical failover or restoration exercise for at least one critical service )
  • {{ dr_test_reviewer }} — Test results reviewer (default: the business continuity plan owner)

Reviewed framework crosswalks (2)

  • equivalent-to → requirement--nist-sp-800-53-r5-cp-4 reviewed (maps cp_04_odp_01←dr_test_cadence, cp_4_prm_2←dr_test_methods)
  • subset-of → requirement--soc2-tsc-2017-a1-3 reviewed
OGRL-BC-03 Data Backup bc corrective daily 5 crosswalks
control--ogrl-bc-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Back up {{ backup_scope }} {{ backup_frequency }} using automated backup jobs, encrypt backups, keep at least one copy in {{ backup_storage_location }} that production credentials cannot modify or delete, retain backups for {{ backup_retention }}, and alert {{ backup_alert_recipients }} when a backup job fails.

Objective

Ensure data and system state can be recovered after accidental deletion, corruption, ransomware, or infrastructure loss.

Implementation guidance

Use managed snapshots and point-in-time recovery for databases and a central backup service with vault lock or object lock for immutability. Copy backups to a separate cloud account to isolate them from a compromised production account. Infrastructure as code and application source held in a hosted version control system count as system-level backups if the provider retains history. Periodically compare the backup inventory against the data store inventory to catch unprotected stores, and consider backups of critical SaaS data such as the document workspace.

Parameters (5)

  • {{ backup_alert_recipients }} — Backup failure alert recipients (default: the on-call engineering team)
  • {{ backup_frequency }} — Backup frequency (default: at least daily)
  • {{ backup_retention }} — Backup retention period (default: at least 30 days)
  • {{ backup_scope }} — Data and system state to back up (default: production databases, object storage, and system configuration not reproducible from version control )
  • {{ backup_storage_location }} — Isolated backup location (default: a separate cloud account or region)

Reviewed framework crosswalks (5)

  • equivalent-to → requirement--nist-sp-800-53-r5-cp-9#a reviewed (maps cp_09_odp_01←backup_scope, cp_09_odp_02←backup_frequency)
  • equivalent-to → requirement--nist-sp-800-53-r5-cp-9#b reviewed (maps cp_09_odp_03←backup_frequency)
  • equivalent-to → requirement--nist-sp-800-53-r5-cp-9#d reviewed
  • subset-of → requirement--soc2-tsc-2017-a1-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-5 reviewed
OGRL-BC-04 Backup Restoration Testing bc detective quarterly 3 crosswalks
control--ogrl-bc-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Restore backups of each critical data store {{ restore_test_cadence }} into an isolated environment, verify data completeness and integrity against defined checks, record the restore duration and data recency against recovery time and recovery point objectives, and remediate failed tests.

Objective

Confirm that backups are reliable and can be restored within committed recovery objectives before they are needed.

Implementation guidance

Automate restore tests where possible, for example a scheduled job that restores the latest snapshot to a temporary instance, runs row-count and checksum queries, records timing, and tears down the instance. Rotate which data stores are tested if full coverage each period is impractical, but test every critical store at least annually. Keep the job output or a ticket per test as evidence.

Parameters (1)

  • {{ restore_test_cadence }} — Restoration test frequency (default: at least quarterly)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-cp-9-1 reviewed (maps cp_9_1_prm_1←restore_test_cadence)
  • intersects-with → requirement--soc2-tsc-2017-a1-2 reviewed
  • subset-of → requirement--soc2-tsc-2017-a1-3 reviewed
OGRL-BC-05 Redundant Processing and Storage Sites bc preventive continuous 4 crosswalks
control--ogrl-bc-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Run critical production services across {{ processing_redundancy }} with the ability to resume them at an alternate processing location within {{ failover_time_limit }}, keep backup copies in {{ alternate_storage_location }}, and apply the same security baseline to alternate locations as to the primary environment.

Objective

Ensure the loss of a single facility, zone, or region does not cause prolonged unavailability or loss of data.

Implementation guidance

In cloud environments, alternate sites are additional availability zones and regions rather than separate data centers, and provider agreements cover the facilities. Deploy stateless tiers across zones behind load balancers and use multi-zone managed databases. For regional failover, keep infrastructure as code and container images deployable to a secondary region and replicate backups there. Apply identical IaC modules, IAM guardrails, logging, and encryption settings to every region so the secondary environment is not a weaker target.

Parameters (3)

  • {{ alternate_storage_location }} — Alternate storage location (default: a region geographically separate from the primary data)
  • {{ failover_time_limit }} — Alternate processing resumption time (default: the recovery time objective defined in the business continuity plan)
  • {{ processing_redundancy }} — Processing redundancy (default: at least two availability zones)

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-53-r5-cp-6 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-cp-7#a reviewed (maps cp_07_odp_02←failover_time_limit)
  • equivalent-to → requirement--nist-sp-800-53-r5-cp-7#c reviewed
  • subset-of → requirement--soc2-tsc-2017-a1-2 reviewed
OGRL-BC-06 System Recovery and Reconstitution bc corrective event-driven 3 crosswalks
control--ogrl-bc-06 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

After a disruption, compromise, or failure, recover affected systems to a known-good state within {{ recovery_time_objective }} and with data loss no greater than {{ recovery_point_objective }} using documented recovery runbooks and infrastructure as code, and verify that security configurations and controls are restored and functioning before returning systems to service.

Objective

Return systems to normal, secure operation within committed timeframes and without degrading the controls that protect them.

Implementation guidance

Rebuild from infrastructure as code and trusted images rather than patching compromised hosts in place. Restore data from the most recent clean backup, which may predate the latest backup after ransomware or corruption. Use a recovery checklist that confirms logging, encryption, access policies, and monitoring are active before reopening traffic. Tighten the default objectives per service based on the business impact analysis (OGRL-BC-07). Evidence is the recovery record showing timing and the completed checklist.

Parameters (2)

  • {{ recovery_point_objective }} — Recovery point objective (default: 24 hours)
  • {{ recovery_time_objective }} — Recovery time objective (default: 24 hours)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-cp-10 reviewed (maps cp_10_prm_1←recovery_time_objective)
  • intersects-with → requirement--soc2-tsc-2017-a1-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-5 reviewed
OGRL-BC-07 Business Impact Analysis bc preventive annual 4 crosswalks
control--ogrl-bc-07 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Perform a business impact analysis {{ bia_cadence }} and upon significant changes to services or infrastructure that identifies critical business functions and the systems, data, personnel, and third-party dependencies supporting them, rates their criticality, and determines the maximum tolerable downtime and data loss used to set recovery objectives.

Objective

Ensure recovery priorities and objectives reflect the actual impact of disruption on customers and the business.

Implementation guidance

Keep the analysis lightweight: a table of customer-facing services and internal functions with their supporting cloud resources, data stores, and SaaS vendors, a criticality tier, impact over time (for example at 1 hour, 1 day, 1 week), and the resulting recovery objectives. Draw dependencies from the system inventory (OGRL-AM-01) and vendor inventory (OGRL-TP-01). Feed results into the continuity plan (OGRL-BC-01).

Parameters (1)

  • {{ bia_cadence }} — Business impact analysis frequency (default: at least annually)

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-53-r5-cp-2-8 reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-ra-9 reviewed
  • intersects-with → requirement--soc2-tsc-2017-a1-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc9-1 reviewed
OGRL-BC-08 Capacity Planning and Monitoring bc detective continuous 2 crosswalks
control--ogrl-bc-08 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Monitor utilization of critical compute, storage, database, and network resources and cloud service quotas, alert {{ capacity_alert_recipients }} when utilization exceeds {{ capacity_alert_threshold }}, and review capacity forecasts {{ capacity_review_cadence }} to provision additional capacity, including the capacity needed to operate from alternate locations during contingency operations.

Objective

Maintain sufficient capacity to meet availability commitments as demand grows and during failover.

Implementation guidance

Use cloud-native metrics and alarms for CPU, memory, disk, connection counts, queue depth, and service quota usage, and enable autoscaling with sensible maximums. Confirm that quotas and reserved capacity in the failover region can absorb production load. Record capacity reviews in a recurring ticket or meeting notes with resulting actions.

Parameters (3)

  • {{ capacity_alert_recipients }} — Capacity alert recipients (default: the on-call engineering team)
  • {{ capacity_alert_threshold }} — Capacity alert threshold (default: 80 percent of provisioned capacity or quota)
  • {{ capacity_review_cadence }} — Capacity review frequency (default: quarterly)

Reviewed framework crosswalks (2)

  • superset-of → requirement--nist-sp-800-53-r5-cp-2-2 reviewed
  • subset-of → requirement--soc2-tsc-2017-a1-1 reviewed
OGRL-BC-09 Denial-of-Service Protection bc preventive continuous 3 crosswalks
control--ogrl-bc-09 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Protect internet-facing services against the effects of {{ dos_event_types }} by employing {{ dos_protections }} in front of all public endpoints, and alert {{ dos_alert_recipients }} when attack traffic or rate-limit thresholds are exceeded.

Objective

Keep services available to legitimate users during denial-of-service attacks.

Implementation guidance

Place public endpoints behind a CDN or cloud load balancer with provider DDoS protection, add WAF rate-based rules for login, signup, and expensive API routes, and apply per-tenant or per-key API quotas. Avoid exposing origin servers directly. Keep a runbook for engaging the provider's DDoS response team during large attacks.

Parameters (3)

  • {{ dos_alert_recipients }} — Denial-of-service alert recipients (default: the on-call engineering team)
  • {{ dos_event_types }} — Denial-of-service event types (default: volumetric network floods, protocol attacks, and application-layer request floods )
  • {{ dos_protections }} — Denial-of-service protections (default: cloud DDoS mitigation, web application firewall rate limiting, and API request quotas )

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-sc-5 reviewed (maps sc_05_odp_01←dos_event_types, sc_05_odp_03←dos_protections)
  • intersects-with → requirement--soc2-tsc-2017-a1-1 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc6-6 reviewed
OGRL-CM-01 Peer-Reviewed Production Change Control cm preventive event-driven 5 crosswalks
control--ogrl-cm-01 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Require independent peer review, automated verification checks, and documented approval overseen by {{ change_authority }} before merging or deploying changes to production, retaining change records for {{ change_record_retention }}.

Objective

Prevent unauthorized, untested, or unreviewed modifications to production code and infrastructure.

Implementation guidance

Enforce branch protection rules that prevent self-approval, require passing CI checks, and link deployments to immutable commit hashes and review tickets.

Parameters (2)

  • {{ change_authority }} — Change oversight authority (default: designated code owners and the change advisory workflow)
  • {{ change_record_retention }} — Change record retention period (default: 365 days)

Library tests (1)

  • automated · daily · required — Verify Branch Protection and Peer-Reviewed Deployments: Confirm production repositories enforce required independent pull-request reviews and passing CI status checks with no bypassed merges.

Reviewed framework crosswalks (5)

  • equivalent-to → requirement--iso-iec-27001-2022-a-8-32 reviewed
  • equivalent-to → requirement--nist-sp-800-171-r3-03-04-03 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-cm-3#e reviewed (maps cm_03_odp_01←change_record_retention)
  • equivalent-to → requirement--nist-sp-800-53-r5-cm-3#g reviewed (maps cm_03_odp_02←change_authority)
  • equivalent-to → requirement--soc2-tsc-2017-cc8-1 reviewed
OGRL-CM-02 Baseline Configuration and Hardening Standards cm preventive annual 8 crosswalks
control--ogrl-cm-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Define hardened baseline configurations for {{ baseline_scope }} derived from {{ hardening_benchmark }}, maintain them as version-controlled code or templates, provision new components only from an approved baseline, require documented approval by {{ deviation_approver }} for any deviation, and review and update each baseline {{ baseline_review_frequency }} and whenever covered components are introduced or upgraded.

Objective

Ensure in-scope components start from, and remain traceable to, an approved secure configuration rather than ad hoc vendor defaults.

Implementation guidance

Express baselines as infrastructure-as-code modules, golden machine images, hardened container base images, and organization-level cloud policies (for example AWS SCPs, Azure Policy, or GCP organization policies). Keep a short deviation register linked to the baseline repository. Use CIS Benchmarks or provider security best-practice guides as the starting point and record which settings were tailored and why. Drift detection against these baselines is covered by OGRL-CM-03.

Parameters (4)

  • {{ baseline_review_frequency }} — Baseline review frequency (default: annually)
  • {{ baseline_scope }} — Components covered by hardened baselines (default: cloud accounts and projects, compute images, container base images, managed databases, and network configurations )
  • {{ deviation_approver }} — Baseline deviation approver (default: the security lead)
  • {{ hardening_benchmark }} — Hardening benchmark source (default: CIS Benchmarks or the cloud provider's security best-practice guidance)

Reviewed framework crosswalks (8)

  • equivalent-to → requirement--nist-sp-800-53-r5-cm-2#a reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-cm-2#b.1 reviewed (maps cm_02_odp_01←baseline_review_frequency)
  • equivalent-to → requirement--nist-sp-800-53-r5-cm-2#b.3 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-cm-6#a reviewed (maps cm_06_odp_01←hardening_benchmark)
  • equivalent-to → requirement--nist-sp-800-53-r5-cm-6#b reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-cm-6#c reviewed (maps cm_06_odp_02←baseline_scope)
  • intersects-with → requirement--soc2-tsc-2017-cc5-2 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc7-1 reviewed
OGRL-CM-03 Configuration Drift Detection cm detective continuous 5 crosswalks
control--ogrl-cm-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Continuously compare the running configuration of {{ drift_scope }} against its approved baseline using {{ drift_detection_tooling }}, alert {{ drift_alert_recipients }} on unapproved deviations, and revert or formally approve each detected drift within {{ drift_remediation_sla }}.

Objective

Detect unauthorized or accidental configuration changes quickly so production does not silently diverge from its approved secure state.

Implementation guidance

Run scheduled infrastructure-as-code plan or drift checks (for example terraform plan in CI, AWS Config, or Azure Policy compliance) and a CSPM tool against production accounts. Route findings to the owning team's queue with the SLA as a due date. Evidence is the drift tool configuration plus a sample of alerts showing revert or approval within SLA.

Parameters (4)

  • {{ drift_alert_recipients }} — Drift alert recipients (default: the owning engineering team and the security team)
  • {{ drift_detection_tooling }} — Drift detection mechanisms (default: automated infrastructure-as-code drift checks and cloud security posture management (CSPM) rules )
  • {{ drift_remediation_sla }} — Drift resolution SLA (default: 7 days for security-relevant settings and 30 days for all other settings)
  • {{ drift_scope }} — Components monitored for drift (default: production cloud resources and infrastructure-as-code managed components)

Reviewed framework crosswalks (5)

  • intersects-with → requirement--nist-sp-800-53-r5-cm-2-2 reviewed (maps cm_02_02_odp←drift_detection_tooling)
  • subset-of → requirement--nist-sp-800-53-r5-cm-6-1 reviewed (maps cm_6_1_prm_2←drift_detection_tooling)
  • subset-of → requirement--nist-sp-800-53-r5-cm-6#d reviewed
  • subset-of → requirement--soc2-tsc-2017-cc7-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc8-1 reviewed
OGRL-CM-04 Security Impact Analysis of Changes cm preventive event-driven 3 crosswalks
control--ogrl-cm-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Before implementing {{ significant_change_types }}, document an analysis of the change's potential security and privacy impact, covering affected data, trust boundaries, access paths, and existing controls, and obtain sign-off from {{ impact_reviewer }} prior to deployment.

Objective

Ensure significant changes do not introduce unassessed security or privacy risk into production.

Implementation guidance

Add a security-impact section to the design document or pull-request template that is required when a change matches a significant-change label. Lightweight threat modeling (for example STRIDE on a data-flow diagram) is sufficient for most changes. Organization-level risk re-evaluation for significant business changes is covered by the risk family.

Parameters (2)

  • {{ impact_reviewer }} — Security impact sign-off authority (default: the security lead or a designated security reviewer)
  • {{ significant_change_types }} — Changes requiring security impact analysis (default: significant changes, including new external integrations, changes to authentication or authorization, new data stores holding customer data, and network boundary changes )

Reviewed framework crosswalks (3)

  • subset-of → requirement--nist-sp-800-53-r5-cm-4 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc3-4 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc8-1 reviewed
OGRL-CM-05 Production Change Access Restrictions cm preventive continuous 3 crosswalks
control--ogrl-cm-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Restrict permissions to deploy to or modify production systems to {{ deploy_authorized_identities }} acting through the CI/CD pipeline or infrastructure-as-code workflow, prohibit direct manual changes outside that path except under the emergency change procedure, and review the identities holding production change permissions {{ change_access_review_frequency }}.

Objective

Ensure production can only be changed through the controlled, reviewable delivery path.

Implementation guidance

Grant production write access to the pipeline's workload identity (for example GitHub Actions OIDC roles) rather than to humans. Keep human production access read-only by default with just-in-time elevation. Use GitHub environments with required reviewers and restrict who can modify pipeline definitions. Evidence is the IAM policy export and the quarterly review record.

Parameters (2)

  • {{ change_access_review_frequency }} — Production change access review frequency (default: quarterly)
  • {{ deploy_authorized_identities }} — Identities permitted to change production (default: the automated deployment pipeline and a named set of platform engineers)

Reviewed framework crosswalks (3)

  • subset-of → requirement--nist-sp-800-53-r5-cm-5 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc6-1 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc8-1 reviewed
OGRL-CM-06 Emergency Change Procedure cm corrective event-driven 3 crosswalks
control--ogrl-cm-06 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Permit changes that bypass standard pre-deployment approval only when authorized by {{ emergency_authorizer }} to resolve an active incident or critical vulnerability, record each emergency change with its justification and linked incident or ticket, and complete retrospective peer review and approval of the change within {{ retro_review_window }}.

Objective

Allow rapid remediation without creating an unreviewed path into production.

Implementation guidance

Use a dedicated emergency label or break-glass deployment workflow that records who invoked it and requires an incident ID. A weekly query for merges that bypassed branch protection or deployments without an approved review gives auditors a complete population to sample.

Parameters (2)

  • {{ emergency_authorizer }} — Emergency change authorizer (default: the incident commander or on-call engineering lead)
  • {{ retro_review_window }} — Retrospective review deadline (default: 2 business days)

Reviewed framework crosswalks (3)

  • intersects-with → requirement--nist-sp-800-53-r5-cm-3#b reviewed
  • subset-of → requirement--nist-sp-800-53-r5-cm-3#c reviewed
  • subset-of → requirement--soc2-tsc-2017-cc8-1 reviewed
OGRL-CM-07 Change Testing and Environment Separation cm preventive event-driven 3 crosswalks
control--ogrl-cm-07 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Test and validate each change in {{ test_environment }} that is logically separated from production before deployment, require automated test suites to pass as a merge or deployment gate, retain test results with the change record, and prohibit unmasked production customer data in non-production environments unless approved by {{ prod_data_exception_approver }}.

Objective

Catch defects and unintended effects before they reach production without exposing customer data in lower environments.

Implementation guidance

Run staging in a separate cloud account or project with distinct credentials. Configure required status checks in branch protection so merges are blocked on failing tests, and keep CI run links on the pull request. Use synthetic or masked data sets for testing.

Parameters (2)

  • {{ prod_data_exception_approver }} — Production data in test exception approver (default: the security lead)
  • {{ test_environment }} — Pre-production test environment (default: a staging environment in a separate cloud account or project)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-cm-3-2 reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-cm-4-1 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc8-1 reviewed
OGRL-CM-08 Least Functionality and Software Restriction cm preventive continuous 5 crosswalks
control--ogrl-cm-08 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Configure production hosts and container images to run only the services, ports, and protocols required for their function with all others disabled or blocked by default, restrict software installation on production systems and workforce endpoints to {{ approved_software_sources }} enforced through {{ software_enforcement_methods }}, and review compliance {{ software_compliance_review_frequency }}.

Objective

Reduce attack surface and prevent unauthorized or malicious software from being introduced.

Implementation guidance

Use minimal or distroless base images, default-deny security groups, and read-only root filesystems. On endpoints, remove local administrator rights and use MDM-managed application catalogs or allow-listing. A quarterly export of listening ports, image package lists, and MDM installed-software reports provides evidence.

Parameters (3)

  • {{ approved_software_sources }} — Approved software sources (default: approved package repositories, the internal container registry, and the MDM-managed software catalog )
  • {{ software_compliance_review_frequency }} — Software compliance review frequency (default: quarterly)
  • {{ software_enforcement_methods }} — Software restriction enforcement methods (default: immutable container images, removal of local administrator rights, and MDM application allow-listing )

Reviewed framework crosswalks (5)

  • equivalent-to → requirement--nist-sp-800-53-r5-cm-11#b reviewed (maps cm_11_odp_02←software_enforcement_methods)
  • equivalent-to → requirement--nist-sp-800-53-r5-cm-11#c reviewed (maps cm_11_odp_03←software_compliance_review_frequency)
  • equivalent-to → requirement--nist-sp-800-53-r5-cm-7#a reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-cm-7#b reviewed
  • subset-of → requirement--soc2-tsc-2017-cc6-8 reviewed
OGRL-CM-09 Software and Data Integrity Verification cm detective continuous 3 crosswalks
control--ogrl-cm-09 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Verify the integrity of {{ integrity_protected_assets }} using {{ integrity_mechanisms }} before deployment and while running, and when verification fails or an unauthorized change is detected, {{ integrity_response_actions }}.

Objective

Detect and stop tampered or unauthorized software and configuration before it can affect production.

Implementation guidance

Sign build artifacts and container images in CI (for example Sigstore cosign), pin deployments to image digests, and enforce signature verification with an admission controller or deployment policy. Use file integrity monitoring or immutable infrastructure for hosts. Integrity of customer data stores is addressed by the data integrity control in the cryptography family.

Parameters (3)

  • {{ integrity_mechanisms }} — Integrity verification mechanisms (default: cryptographic signing and digest pinning of artifacts and images, plus file integrity monitoring on hosts )
  • {{ integrity_protected_assets }} — Assets subject to integrity verification (default: build artifacts, container images, infrastructure-as-code templates, and critical system binaries and configuration files )
  • {{ integrity_response_actions }} — Actions on integrity failure (default: block the deployment or isolate the affected host, alert the security on-call team, and open a security incident )

Reviewed framework crosswalks (3)

  • subset-of → requirement--nist-sp-800-53-r5-si-7#a reviewed (maps si_7_prm_1←integrity_protected_assets)
  • equivalent-to → requirement--nist-sp-800-53-r5-si-7#b reviewed (maps si_7_prm_2←integrity_response_actions)
  • subset-of → requirement--soc2-tsc-2017-cc6-8 reviewed
OGRL-CR-01 Encryption in Transit and at Rest cr preventive continuous 6 crosswalks
control--ogrl-cr-01 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Protect {{ protected_data_scope }} in transit using {{ transit_cipher_suite }} and at rest using {{ rest_cipher_suite }} with centrally managed keys.

Objective

Preserve confidentiality and integrity of sensitive data across networks and storage media.

Implementation guidance

Disable TLS versions below 1.2, enforce HSTS on public web endpoints, and enable cloud KMS encryption on all databases, object stores, and block volumes.

Parameters (3)

  • {{ protected_data_scope }} — Protected data scope (default: all customer, authentication, and confidential organizational data)
  • {{ rest_cipher_suite }} — Minimum storage encryption (default: AES-256)
  • {{ transit_cipher_suite }} — Minimum transport encryption (default: TLS 1.2 or higher)

Library tests (1)

  • automated · daily · required — Verify TLS in Transit and Storage Encryption at Rest: Verify public endpoints enforce TLS 1.2+ and all production databases, object buckets, and volumes have encryption at rest enabled.

Reviewed framework crosswalks (6)

  • equivalent-to → requirement--iso-iec-27001-2022-a-8-24 reviewed
  • equivalent-to → requirement--nist-sp-800-171-r3-03-13-08 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-sc-28 reviewed (maps sc_28_odp_02←protected_data_scope)
  • equivalent-to → requirement--nist-sp-800-53-r5-sc-8 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-1 reviewed
  • equivalent-to → requirement--soc2-tsc-2017-cc6-7 reviewed
OGRL-CR-02 Cryptographic Key Management cr preventive continuous 2 crosswalks
control--ogrl-cr-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Generate, store, and use cryptographic keys protecting {{ key_scope }} within {{ key_management_system }}, restrict key administration and key use to authorized roles through least-privilege policies, rotate keys {{ key_rotation_period }} and upon suspected compromise, and log all key administration actions.

Objective

Keep cryptographic keys confidential, available, and under authorized control throughout their lifecycle so that encryption remains effective.

Implementation guidance

Use a cloud KMS (AWS KMS, Google Cloud KMS, Azure Key Vault) with HSM-backed keys and enable automatic rotation for customer-managed keys. Separate key administrators from key users in IAM policy, require a waiting period before key deletion, and send KMS audit events to the central log store. Manage TLS certificates through a managed certificate service with automated renewal. Keep a key inventory recording owner and purpose, and never embed key material in source code or images (see OGRL-AC-06).

Parameters (3)

  • {{ key_management_system }} — Key management system (default: a FIPS 140-validated cloud key management service or HSM)
  • {{ key_rotation_period }} — Key rotation frequency (default: at least annually)
  • {{ key_scope }} — Data and services protected by managed keys (default: production data stores, backups, and TLS endpoints)

Reviewed framework crosswalks (2)

  • equivalent-to → requirement--nist-sp-800-53-r5-sc-12 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc6-1 reviewed
OGRL-CR-03 Data Retention and Disposal cr preventive quarterly 4 crosswalks
control--ogrl-cr-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Define retention periods for each category of customer, personal, and confidential data in a documented retention schedule; enforce them through automated deletion or lifecycle rules where technically feasible; delete customer data within {{ customer_deletion_window }} of contract termination or a verified deletion request; and verify {{ retention_review_cadence }} that data past its retention period has been disposed of.

Objective

Retain information only as long as required for business, legal, and contractual purposes and dispose of it securely afterward.

Implementation guidance

Implement retention with object storage lifecycle policies, database TTL or scheduled purge jobs, and log-group retention settings. Document that deleted data persists in backups until they age out under OGRL-BC-03. Provide a legal-hold process that suspends deletion when required. Per-tenant encryption keys enable cryptographic erasure of a customer's data at offboarding. Keep deletion job output or tickets as evidence and provide deletion confirmations to customers on request.

Parameters (2)

  • {{ customer_deletion_window }} — Customer data deletion deadline (default: 30 days)
  • {{ retention_review_cadence }} — Retention enforcement review frequency (default: quarterly)

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-53-r5-si-12 reviewed
  • intersects-with → requirement--soc2-tsc-2017-c1-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-5 reviewed
  • intersects-with → requirement--soc2-tsc-2017-p4-2 reviewed
OGRL-CR-04 Media Sanitization and Secure Disposal cr preventive event-driven 5 crosswalks
control--ogrl-cr-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Sanitize {{ media_scope }} prior to disposal, reuse, or release outside organizational control using {{ sanitization_methods }}, and retain a record of each sanitized asset including its identifier, method used, date, and the person or vendor performing the sanitization.

Objective

Prevent recovery of confidential and personal information from retired, reassigned, or returned storage media.

Implementation guidance

For laptops, rely on full-disk encryption plus an MDM-initiated wipe or cryptographic erase before reassignment, and use a certified IT asset disposition vendor that issues certificates of destruction for retired hardware. Data center media is usually sanitized by the cloud provider; treat it as a subservice organization responsibility and confirm it in their SOC 2 report. For cloud volumes and tenant data, deleting the encryption key renders data unrecoverable. Reconcile disposal records against the asset inventory (OGRL-AM-01).

Parameters (2)

  • {{ media_scope }} — Media requiring sanitization (default: laptops, workstations, removable media, and other devices that store organizational data )
  • {{ sanitization_methods }} — Sanitization techniques (default: NIST SP 800-88 purge or destroy techniques, including cryptographic erase of encrypted devices )

Reviewed framework crosswalks (5)

  • equivalent-to → requirement--nist-sp-800-53-r5-mp-6#a reviewed (maps mp_6_prm_1←media_scope, mp_6_prm_2←sanitization_methods)
  • intersects-with → requirement--nist-sp-800-53-r5-mp-6#b reviewed
  • subset-of → requirement--soc2-tsc-2017-c1-2 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc6-5 reviewed
  • subset-of → requirement--soc2-tsc-2017-p4-3 reviewed
OGRL-CR-05 Data Store Integrity and Replication cr detective continuous 4 crosswalks
control--ogrl-cr-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Configure production data stores holding {{ integrity_scope }} with storage-level integrity verification and replication across at least {{ replica_zone_count }} availability zones, and alert {{ integrity_alert_recipients }} when integrity errors, replication failures, or replication lag exceeding {{ replication_lag_threshold }} are detected.

Objective

Ensure stored data remains complete and accurate and survives the loss of a single storage component or zone without corruption or loss.

Implementation guidance

Prefer managed data stores with built-in checksumming and synchronous replication (for example multi-AZ relational databases and object storage with checksums and versioning), enable page checksums where the engine supports them, and alert on replica lag and storage error metrics. Replication propagates logical corruption and accidental deletes, so it complements rather than replaces backups (OGRL-BC-03). Run periodic consistency checks or reconciliations on critical tables. Software and artifact integrity verification is covered by OGRL-CM-09.

Parameters (4)

  • {{ integrity_alert_recipients }} — Integrity and replication alert recipients (default: the on-call engineering team)
  • {{ integrity_scope }} — Data covered by integrity verification (default: customer data and system-of-record data)
  • {{ replica_zone_count }} — Minimum replication zones (default: two)
  • {{ replication_lag_threshold }} — Replication lag alert threshold (default: 5 minutes)

Reviewed framework crosswalks (4)

  • intersects-with → requirement--nist-sp-800-53-r5-cp-9 reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-si-7#a reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-si-7#b reviewed
  • intersects-with → requirement--soc2-tsc-2017-pi1-5 reviewed
OGRL-GV-01 Information Security Program and Policy Framework gv preventive annual 6 crosswalks
control--ogrl-gv-01 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain a documented information security policy set that defines the security program's scope, policy owners, and roles and responsibilities. The policy set is approved by {{ policy_approver }}, published to all workforce members, stored in a repository where only policy owners can modify it, and reviewed and updated {{ policy_review_frequency }} and following {{ policy_review_triggers }}.

Objective

Security expectations are formally defined, approved by accountable leadership, available to everyone they apply to, and kept current.

Implementation guidance

A startup can start with a top-level information security policy plus topic policies (access control, change management, incident response, vendor management, data handling) kept in a wiki or Git repository with change history. Record each review and approval with a dated sign-off or merge approval; auditors typically sample the approval record, the publication location, and the version history. Map each policy to the controls that implement it so gaps are visible.

Parameters (3)

  • {{ policy_approver }} — Policy approval authority (default: executive leadership (CEO or designated executive))
  • {{ policy_review_frequency }} — Policy review frequency (default: at least annually)
  • {{ policy_review_triggers }} — Events triggering out-of-cycle policy review (default: significant organizational, regulatory, contractual, or system changes)

Reviewed framework crosswalks (6)

  • subset-of → requirement--nist-sp-800-53-r5-pm-1#a reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-pm-1#b reviewed (maps pm_01_odp_01←policy_review_frequency, pm_01_odp_02←policy_review_triggers)
  • equivalent-to → requirement--nist-sp-800-53-r5-pm-1#c reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc2-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc5-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc5-3 reviewed
OGRL-GV-02 Security Leadership and Organizational Structure gv preventive annual 3 crosswalks
control--ogrl-gv-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Designate in writing a {{ security_leader_role }} who is accountable for the information security program and has the authority and resources to run it. Maintain an organizational chart showing reporting lines and a document of security roles and responsibilities, and review both {{ org_review_frequency }} and when leadership or structure changes.

Objective

Accountability for security is assigned to a named individual, and reporting lines and responsibilities are clear and current.

Implementation guidance

In small companies the role is often held by the CTO or a head of security as a part-time responsibility; that is acceptable if the designation is written and the person has the authority to act. Keep the org chart in the HRIS so it stays current, and keep a RACI for security activities (policy ownership, access reviews, incident command, vendor reviews). Evidence: the designation memo or board resolution, the dated org chart, and the reviewed RACI.

Parameters (2)

  • {{ org_review_frequency }} — Org chart and responsibilities review frequency (default: at least annually)
  • {{ security_leader_role }} — Accountable security leader role (default: security officer (for example CISO, head of security, or CTO))

Reviewed framework crosswalks (3)

  • superset-of → requirement--nist-sp-800-53-r5-pm-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc1-3 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc1-5 reviewed
OGRL-GV-03 Board Oversight of Security and Risk gv detective annual 2 crosswalks
control--ogrl-gv-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Security leadership briefs {{ oversight_body }} on the state of the security program {{ briefing_frequency }}, covering top risks and their treatment status, significant incidents, control assessment and audit results, and open deficiencies. The oversight body's review, questions, and decisions are recorded in meeting minutes.

Objective

Those charged with governance exercise informed, documented oversight of security and risk independently of the management that operates the controls.

Implementation guidance

Pre-revenue companies with an informal board can use a board meeting agenda item with a short security deck; record attendance and decisions in minutes. Where the board includes outside or independent directors, note their participation. Auditors usually sample the deck and minutes for each briefing in the period.

Parameters (2)

  • {{ briefing_frequency }} — Security briefing frequency (default: at least annually)
  • {{ oversight_body }} — Governance body exercising oversight (default: the board of directors or a designated board committee)

Reviewed framework crosswalks (2)

  • subset-of → requirement--soc2-tsc-2017-cc1-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc2-2 reviewed
OGRL-GV-04 Code of Conduct gv preventive annual 2 crosswalks
control--ogrl-gv-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain a code of conduct, approved by {{ conduct_approver }}, that sets expectations for integrity, ethical behavior, conflicts of interest, and protection of company and customer information, and states disciplinary consequences for violations. Require every employee and contractor to acknowledge the code within {{ acknowledgment_window }} of starting and {{ reacknowledgment_frequency }} thereafter.

Objective

Every workforce member has been informed of, and has agreed to, the organization's standards of conduct and the consequences of violating them.

Implementation guidance

Collect acknowledgments through the HRIS or compliance platform during onboarding and annual policy attestations, and keep the signed record per person. Reference the whistleblower channel (OGRL-GV-05) in the code. Auditors typically sample new hires and existing staff for timely acknowledgment.

Parameters (3)

  • {{ acknowledgment_window }} — Deadline for new-hire acknowledgment (default: 30 days)
  • {{ conduct_approver }} — Code of conduct approval authority (default: executive leadership)
  • {{ reacknowledgment_frequency }} — Re-acknowledgment frequency (default: annually)

Reviewed framework crosswalks (2)

  • subset-of → requirement--soc2-tsc-2017-cc1-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc1-5 reviewed
OGRL-GV-05 Whistleblower and Anonymous Reporting Channel gv detective event-driven 2 crosswalks
control--ogrl-gv-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Provide a confidential reporting channel, with an anonymous option, through which workforce members and {{ external_reporters }} can report suspected misconduct, fraud, or security concerns. Route reports to {{ report_recipient }}, independent of the party reported on, triage each report within {{ triage_sla }}, record its disposition, and prohibit retaliation against good-faith reporters.

Objective

Concerns about misconduct or security can be raised safely and reach someone with authority to act, and every report is resolved.

Implementation guidance

A third-party hotline or a web form that does not record identity satisfies the anonymous option; a shared inbox read only by the CEO does not provide independence if the CEO is the subject. Publish the channel in the code of conduct and employee handbook. Keep a case log (date, category, owner, outcome) as evidence; an empty log is acceptable if the channel's existence and communication are shown.

Parameters (3)

  • {{ external_reporters }} — External parties who may report (default: contractors, customers, and vendors)
  • {{ report_recipient }} — Report recipient (default: a designated board member or the head of legal or people operations)
  • {{ triage_sla }} — Report triage deadline (default: 5 business days)

Reviewed framework crosswalks (2)

  • intersects-with → requirement--soc2-tsc-2017-cc1-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc2-2 reviewed
OGRL-GV-06 Security Objectives and Performance Measures gv detective quarterly 3 crosswalks
control--ogrl-gv-06 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Define security objectives for in-scope systems, each with at least one measurable performance metric and target, approved by {{ metrics_owner }}. Collect the metrics {{ metrics_collection_frequency }} and report results, trends, and missed targets to {{ metrics_audience }} {{ metrics_reporting_frequency }}.

Objective

Security objectives are specific enough to assess risk and performance against, and leadership sees measured results over time.

Implementation guidance

Pick a small set of metrics tied to commitments: vulnerability SLA adherence, access review completion, training completion, MFA coverage, mean time to detect and resolve incidents, availability against SLA. Most can be pulled automatically from the compliance platform, ticketing, and monitoring. Evidence: the objectives document and dated metric reports.

Parameters (4)

  • {{ metrics_audience }} — Metric report audience (default: executive leadership)
  • {{ metrics_collection_frequency }} — Metric collection frequency (default: monthly)
  • {{ metrics_owner }} — Approver of objectives and metrics (default: the security leader)
  • {{ metrics_reporting_frequency }} — Metric reporting frequency (default: quarterly)

Reviewed framework crosswalks (3)

  • subset-of → requirement--nist-sp-800-53-r5-pm-6 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc3-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc4-1 reviewed
OGRL-GV-07 External Commitments and Customer Communication gv preventive annual 1 crosswalks
control--ogrl-gv-07 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain a register of the security, availability, and confidentiality commitments made to customers and users (for example in terms of service, data processing agreements, SLAs, and the trust center). Make current commitments and instructions for reporting security issues available through {{ customer_channel }}, notify affected customers at least {{ change_notice_period }} before a material reduction in commitments takes effect, and review the register {{ commitment_review_frequency }}.

Objective

Customers know what the organization has committed to and how to raise security concerns, and commitments do not change without notice.

Implementation guidance

Legal or the commercial owner usually maintains the register; security confirms each commitment is backed by a control. A public trust center or security page with a security contact (for example security.txt) covers the publication channel. Evidence: the register, the published page, and notices sent for changes.

Parameters (3)

  • {{ change_notice_period }} — Advance notice for material commitment changes (default: 30 days)
  • {{ commitment_review_frequency }} — Commitment register review frequency (default: at least annually)
  • {{ customer_channel }} — Customer communication channel (default: the public trust center and customer contracts)

Reviewed framework crosswalks (1)

  • subset-of → requirement--soc2-tsc-2017-cc2-3 reviewed
OGRL-GV-08 System Description and Security Plan gv preventive annual 7 crosswalks
control--ogrl-gv-08 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain a system description for each in-scope system that documents its boundary, infrastructure and software components, subservice organizations and other dependencies, data flows, information types handled, user roles, and the controls in place. The description is approved by {{ plan_approver }}, distributed to {{ plan_distribution }}, stored where only its owners can modify it, reviewed {{ plan_review_frequency }}, and updated when the system or its environment changes significantly or assessments identify problems.

Objective

An accurate, approved account of each system's scope and controls exists and is available to those who rely on it.

Implementation guidance

This is the document a SOC 2 report's system description is drawn from. Keep the architecture and data-flow diagrams generated from or reconciled with the component inventory (OGRL-AM-01). Link controls to the OGRL control set rather than restating them. Evidence: the current version, its approval, and change history.

Parameters (3)

  • {{ plan_approver }} — System description approver (default: the security leader and the system owner)
  • {{ plan_distribution }} — Recipients of the system description and changes (default: engineering leadership, the compliance team, and auditors)
  • {{ plan_review_frequency }} — System description review frequency (default: at least annually)

Reviewed framework crosswalks (7)

  • subset-of → requirement--nist-sp-800-53-r5-pl-2#a reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-pl-2#b reviewed (maps pl_02_odp_02←plan_distribution)
  • equivalent-to → requirement--nist-sp-800-53-r5-pl-2#c reviewed (maps pl_02_odp_03←plan_review_frequency)
  • equivalent-to → requirement--nist-sp-800-53-r5-pl-2#d reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-pl-2#e reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc2-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc2-3 reviewed
OGRL-GV-09 Acceptable Use and Rules of Behavior gv preventive annual 4 crosswalks
control--ogrl-gv-09 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain an acceptable use policy that sets out workforce responsibilities and expected behavior when using company systems, devices, and data. Require each workforce member to acknowledge the policy before access to company systems is granted, and to re-acknowledge it {{ reacknowledgment_frequency }} and after material revisions. Review and update the policy {{ aup_review_frequency }}.

Objective

Everyone with system access has agreed to defined rules for using systems and data before receiving access, and the rules stay current.

Implementation guidance

Cover device security, approved software and SaaS, handling of customer data, use of AI tools, personal use, and reporting of suspected incidents. Gate account provisioning (OGRL-AC-01) on a recorded acknowledgment in the HRIS or compliance platform. Evidence: the policy, its review history, and per-person acknowledgment timestamps compared with access grant dates.

Parameters (2)

  • {{ aup_review_frequency }} — Acceptable use policy review frequency (default: at least annually)
  • {{ reacknowledgment_frequency }} — Re-acknowledgment frequency (default: annually)

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-53-r5-pl-4 reviewed (maps pl_04_odp_01←aup_review_frequency, pl_04_odp_03←reacknowledgment_frequency)
  • intersects-with → requirement--soc2-tsc-2017-cc1-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc2-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc5-3 reviewed
OGRL-GV-10 Periodic Control Assessment gv detective annual 3 crosswalks
control--ogrl-gv-10 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Assess the design and operating effectiveness of in-scope controls {{ assessment_frequency }} using {{ assessor }} independent of the people who operate the controls. Each assessment follows a written plan defining scope, controls, test procedures, and roles that {{ plan_approver }} approves before testing begins, produces a written report, and delivers results to {{ results_recipients }}.

Objective

Leadership has periodic, independent evidence of whether controls are implemented correctly and achieving their intended outcome.

Implementation guidance

An external SOC 2 audit can serve as the assessment for the controls it covers; a readiness assessment or internal audit fills gaps in years without one. Retain the approved plan, workpapers or sample lists, and the final report. Findings flow to deficiency tracking (OGRL-GV-12).

Parameters (4)

  • {{ assessment_frequency }} — Control assessment frequency (default: at least annually)
  • {{ assessor }} — Assessor (default: an internal audit function or a qualified third-party assessor)
  • {{ plan_approver }} — Assessment plan approver (default: the security leader)
  • {{ results_recipients }} — Recipients of assessment results (default: executive leadership and the board or its designated committee)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-ca-2 reviewed (maps ca_02_odp_01←assessment_frequency, ca_02_odp_02←results_recipients)
  • subset-of → requirement--soc2-tsc-2017-cc4-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc5-1 reviewed
OGRL-GV-11 Continuous Control Monitoring gv detective continuous 6 crosswalks
control--ogrl-gv-11 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Continuously monitor in-scope controls using automated checks that track {{ monitored_metrics }}, executed {{ monitoring_frequency }}. Assign an owner and a remediation ticket to each failing check within {{ triage_sla }}, and report control health and trends to {{ status_audience }} {{ status_reporting_frequency }}.

Objective

Control failures between periodic assessments are detected quickly, assigned, and resolved, and leadership sees current control health.

Implementation guidance

Compliance automation platforms and cloud security posture tools provide most checks out of the box (MFA enforcement, encryption at rest, logging enabled, offboarding completed, background checks on file). Tune checks to the controls in scope, route failures to the owning team's queue, and retain the dashboard history. Persistent failures become deficiencies under OGRL-GV-12.

Parameters (5)

  • {{ monitored_metrics }} — Monitored control metrics (default: pass or fail status of automated control tests and open failures by age and severity )
  • {{ monitoring_frequency }} — Automated check frequency (default: at least daily)
  • {{ status_audience }} — Control health report audience (default: the security leader and executive leadership)
  • {{ status_reporting_frequency }} — Control health reporting frequency (default: monthly)
  • {{ triage_sla }} — Failing check triage deadline (default: 2 business days)

Reviewed framework crosswalks (6)

  • equivalent-to → requirement--nist-sp-800-53-r5-ca-7#a reviewed (maps ca_07_odp_01←monitored_metrics)
  • equivalent-to → requirement--nist-sp-800-53-r5-ca-7#d reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ca-7#f reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ca-7#g reviewed (maps ca_7_prm_4←status_audience, ca_7_prm_5←status_reporting_frequency)
  • subset-of → requirement--soc2-tsc-2017-cc4-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-1 reviewed
OGRL-GV-12 Deficiency Tracking and Remediation gv corrective monthly 2 crosswalks
control--ogrl-gv-12 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Record every control deficiency identified by assessments, audits, continuous monitoring, penetration tests, or incidents in a deficiency register with an owner, severity, remediation plan, and due date. Remediate deficiencies within {{ remediation_sla }}, review open and overdue items with {{ review_audience }} {{ review_frequency }}, and escalate items past due to executive leadership.

Objective

Identified control weaknesses are communicated to those who can fix them and are corrected in a timely, tracked way.

Implementation guidance

A dedicated project in the ticketing system or the compliance platform's findings module works as the register. Close items only with evidence of the fix and, for significant deficiencies, a retest. Evidence: the register with timestamps and the review meeting notes.

Parameters (3)

  • {{ remediation_sla }} — Deficiency remediation deadline (default: 30 days for high severity and 90 days for others, unless a documented risk acceptance applies )
  • {{ review_audience }} — Deficiency review audience (default: the security leader and responsible control owners)
  • {{ review_frequency }} — Deficiency review frequency (default: monthly)

Reviewed framework crosswalks (2)

  • equivalent-to → requirement--nist-sp-800-53-r5-ca-5 reviewed (maps ca_05_odp←review_frequency)
  • intersects-with → requirement--soc2-tsc-2017-cc4-2 reviewed
OGRL-HR-01 Background Screening hr preventive event-driven 3 crosswalks
control--ogrl-hr-01 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Complete {{ screening_scope }} for every employee and contractor, to the extent permitted by applicable law, before granting access to production systems or customer data, and rescreen personnel {{ rescreening_conditions }}.

Objective

Reduce insider risk by confirming that individuals entrusted with systems and data have been vetted before access is granted.

Implementation guidance

Use a background-check provider integrated with the HRIS or applicant tracking system so the check status gates the access-provisioning ticket. Calibrate check depth to the role and jurisdiction, document local-law exceptions, and retain completion records (not report contents) as audit evidence. Contractors supplied through an agency may be covered by the agency's screening if the contract requires it.

Parameters (2)

  • {{ rescreening_conditions }} — Conditions that trigger rescreening (default: upon transfer into a privileged or high-risk role)
  • {{ screening_scope }} — Required screening checks (default: identity verification, criminal history, and employment history checks)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-ps-3 reviewed (maps ps_03_odp_01←rescreening_conditions)
  • intersects-with → requirement--soc2-tsc-2017-cc1-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc1-4 reviewed
OGRL-HR-02 Personnel Offboarding hr preventive event-driven 5 crosswalks
control--ogrl-hr-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

For every departing employee or contractor, complete a documented offboarding checklist that disables system access within {{ access_disable_sla }} of separation, revokes associated credentials, keys, and tokens, recovers company-issued devices and sanitizes them before reassignment, briefs the individual on {{ exit_briefing_topics }}, and transfers ownership of the individual's data and systems to a designated owner; when an individual transfers roles, review and adjust existing access to match the new role within {{ transfer_review_sla }}.

Objective

Ensure departing and transferring personnel retain no access, credentials, or company assets beyond what their current status requires.

Implementation guidance

Trigger the checklist automatically from the HRIS termination or job-change event into the ticketing system. Use the identity provider to suspend SSO and revoke sessions, then sweep systems outside SSO (cloud root or break-glass credentials, SSH keys, personal access tokens, API keys). Track device return through the MDM inventory and remote-wipe unreturned devices. Account disablement itself is also governed by OGRL-AC-01; this control evidences the full offboarding workflow.

Parameters (3)

  • {{ access_disable_sla }} — Maximum time to disable access after separation (default: 24 hours)
  • {{ exit_briefing_topics }} — Topics covered in the exit briefing (default: continuing confidentiality obligations and return of company property)
  • {{ transfer_review_sla }} — Time to review access after an internal transfer (default: 5 business days)

Reviewed framework crosswalks (5)

  • equivalent-to → requirement--nist-sp-800-53-r5-ps-4 reviewed (maps ps_04_odp_01←access_disable_sla, ps_04_odp_02←exit_briefing_topics)
  • equivalent-to → requirement--nist-sp-800-53-r5-ps-5#a reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ps-5#c reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-5 reviewed
OGRL-HR-03 Confidentiality and Access Agreements hr preventive event-driven 3 crosswalks
control--ogrl-hr-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Require every employee and contractor to sign a confidentiality agreement and acknowledge the acceptable use and information security policies before receiving access to systems or confidential information; review the agreement templates {{ agreement_review_frequency }} and obtain renewed acknowledgement {{ reacknowledgement_frequency }} and whenever the agreements materially change.

Objective

Establish enforceable, documented obligations for protecting organizational and customer information before anyone is given access to it.

Implementation guidance

Collect signatures through the HRIS or e-signature tool during onboarding and gate access provisioning on completion. Track annual re-acknowledgement alongside awareness training to reduce friction. Legal should own the templates; security should own the policy content they reference.

Parameters (2)

  • {{ agreement_review_frequency }} — Agreement template review frequency (default: annually)
  • {{ reacknowledgement_frequency }} — Re-acknowledgement frequency (default: annually)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-ps-6 reviewed (maps ps_06_odp_01←agreement_review_frequency, ps_06_odp_02←reacknowledgement_frequency)
  • intersects-with → requirement--soc2-tsc-2017-c1-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc1-1 reviewed
OGRL-HR-04 Contractor and Third-Party Personnel Security hr preventive event-driven 3 crosswalks
control--ogrl-hr-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Require providers whose personnel access organizational systems or confidential data to apply the organization's personnel security requirements, including screening, confidentiality agreements, and security training, with roles and responsibilities documented in the contract; require the provider to notify {{ notification_recipient }} of any transfer or termination of such personnel within {{ notification_window }}; and verify provider compliance {{ compliance_verification_frequency }}.

Objective

Ensure external personnel with access meet the same security expectations as employees and lose access promptly when their engagement ends.

Implementation guidance

Sponsor every contractor account through an internal owner and give it an end date in the identity provider. Include personnel security clauses in staffing agreements and request attestation of screening and training completion. Reconcile active contractor accounts against the provider's roster as part of verification.

Parameters (3)

  • {{ compliance_verification_frequency }} — Provider compliance verification frequency (default: annually)
  • {{ notification_recipient }} — Recipient of provider personnel change notices (default: the internal sponsor and the security team)
  • {{ notification_window }} — Provider notification deadline (default: 1 business day)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-ps-7 reviewed (maps ps_07_odp_01←notification_recipient, ps_07_odp_02←notification_window)
  • intersects-with → requirement--soc2-tsc-2017-cc1-4 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc9-2 reviewed
OGRL-HR-05 Personnel Sanctions hr corrective event-driven 3 crosswalks
control--ogrl-hr-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Apply the documented disciplinary process to any employee or contractor who violates information security or privacy policies, record each case and its outcome, and notify {{ sanction_notification_recipient }} within {{ sanction_notification_window }} when a formal sanction is initiated, identifying the individual and the reason.

Objective

Hold personnel accountable for policy violations consistently and ensure security leadership is aware of sanctioned individuals.

Implementation guidance

Reference the sanctions process in the code of conduct and acceptable use policy. HR owns case records; security receives notification so it can review the individual's access. Keep a log of cases (even if empty for the period) to evidence operation.

Parameters (2)

  • {{ sanction_notification_recipient }} — Roles notified when a sanction is initiated (default: the security lead and the individual's manager)
  • {{ sanction_notification_window }} — Sanction notification deadline (default: 2 business days)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-ps-8 reviewed (maps ps_08_odp_01←sanction_notification_recipient, ps_08_odp_02←sanction_notification_window)
  • intersects-with → requirement--soc2-tsc-2017-cc1-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc1-5 reviewed
OGRL-HR-06 Position Descriptions and Security Responsibilities hr preventive annual 3 crosswalks
control--ogrl-hr-06 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Include security and privacy responsibilities in the documented description of every position, with role-specific duties for {{ elevated_roles }}, and review position descriptions {{ description_review_frequency }} and when roles materially change.

Objective

Make each individual's security and privacy obligations explicit so they can be communicated, trained, and enforced.

Implementation guidance

Add a standard security-responsibilities clause to all job descriptions and role-specific clauses for engineering, operations, and leadership roles. Store current descriptions in the HRIS or a controlled document repository and record review dates.

Parameters (2)

  • {{ description_review_frequency }} — Position description review frequency (default: annually)
  • {{ elevated_roles }} — Roles requiring role-specific security duties (default: engineers, administrators, and security and privacy personnel)

Reviewed framework crosswalks (3)

  • superset-of → requirement--nist-sp-800-53-r5-ps-9 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc1-3 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc1-4 reviewed
OGRL-HR-07 Security and Privacy Awareness Training hr preventive annual 7 crosswalks
control--ogrl-hr-07 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Require every employee and contractor to complete security and privacy awareness training within {{ onboarding_training_window }} of starting and {{ training_frequency }} thereafter; conduct simulated phishing exercises {{ phishing_simulation_frequency }}; and update training content {{ content_review_frequency }} and after {{ content_update_events }}, incorporating lessons learned from security incidents.

Objective

Equip all personnel to recognize and report threats and to handle information in line with security and privacy policies.

Implementation guidance

Use a training platform integrated with the HRIS so new hires are enrolled automatically and completion is tracked; escalate overdue training to managers and consider suspending access after a grace period. Cover phishing, credential hygiene, data handling, incident reporting, and privacy basics. Feed internal incidents and phishing simulation results into content updates.

Parameters (5)

  • {{ content_review_frequency }} — Training content review frequency (default: annually)
  • {{ content_update_events }} — Events that trigger content updates (default: significant security incidents, policy changes, or emerging threats)
  • {{ onboarding_training_window }} — Deadline for initial training after start date (default: 30 days)
  • {{ phishing_simulation_frequency }} — Phishing simulation frequency (default: at least quarterly)
  • {{ training_frequency }} — Recurring training frequency (default: annually)

Reviewed framework crosswalks (7)

  • equivalent-to → requirement--nist-sp-800-53-r5-at-2-1 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-at-2#a.1 reviewed (maps at_02_odp_01←training_frequency, at_02_odp_02←training_frequency)
  • equivalent-to → requirement--nist-sp-800-53-r5-at-2#b reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-at-2#c reviewed (maps at_02_odp_06←content_review_frequency, at_02_odp_07←content_update_events)
  • equivalent-to → requirement--nist-sp-800-53-r5-at-2#d reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc1-4 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc2-2 reviewed
OGRL-HR-08 Role-Based Security Training hr preventive annual 3 crosswalks
control--ogrl-hr-08 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Provide role-specific security training to {{ trained_roles }} before they are granted access to perform those duties, {{ role_training_frequency }} thereafter, and when significant system changes alter their responsibilities; update the content {{ role_content_review_frequency }} and after {{ role_content_update_events }}, incorporating lessons learned from security incidents.

Objective

Ensure personnel with elevated access or security duties have the specific knowledge needed to perform them securely.

Implementation guidance

Typical modules include secure coding and OWASP topics for engineers, cloud and IAM hygiene for infrastructure administrators, incident handling for on-call responders, and privacy obligations for staff handling personal data. Track completion per role in the training platform and gate production access requests on completion.

Parameters (4)

  • {{ role_content_review_frequency }} — Role-based content review frequency (default: annually)
  • {{ role_content_update_events }} — Events that trigger role-based content updates (default: significant security incidents or major technology changes)
  • {{ role_training_frequency }} — Recurring role-based training frequency (default: annually)
  • {{ trained_roles }} — Roles requiring role-based training (default: engineers with production or source code access, on-call incident responders, and administrators of in-scope systems )

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-at-3 reviewed (maps at_03_odp_01←trained_roles, at_03_odp_02←trained_roles, at_03_odp_03←role_training_frequency, at_03_odp_04←role_content_review_frequency, at_03_odp_05←role_content_update_events)
  • intersects-with → requirement--soc2-tsc-2017-cc1-4 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc2-2 reviewed
OGRL-IR-01 Incident Response Plan and Tabletop Testing ir corrective annual 4 crosswalks
control--ogrl-ir-01 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Maintain a documented security incident response plan with defined roles and escalation paths, and test response effectiveness {{ ir_test_cadence }} using {{ ir_test_method }}.

Objective

Ensure personnel can rapidly detect, contain, eradicate, recover from, and report security incidents.

Implementation guidance

Document post-incident lessons learned, track corrective action items to closure, and update contact trees whenever on-call rotations or regulatory notification obligations change.

Parameters (2)

  • {{ ir_test_cadence }} — Incident response test frequency (default: at least annually)
  • {{ ir_test_method }} — Incident response test method (default: structured tabletop exercises and simulated incident drills)

Library tests (1)

  • manual · annual · required — Verify Annual Incident Response Tabletop Exercise: Examine the current incident response plan, after-action report from the most recent tabletop exercise, and closure evidence for identified follow-up tasks.

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-171-r3-03-06-03 reviewed (maps a_03_06_03_odp_01←ir_test_cadence)
  • equivalent-to → requirement--nist-sp-800-53-r5-ir-3 reviewed (maps ir_03_odp_01←ir_test_cadence, ir_03_odp_02←ir_test_method)
  • equivalent-to → requirement--soc2-tsc-2017-cc7-3 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-4 reviewed
OGRL-IR-02 Incident Handling and Triage ir corrective event-driven 4 crosswalks
control--ogrl-ir-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Triage each suspected security incident within {{ triage_sla }} of it being reported or detected, classify it using {{ severity_scale }}, assign an incident commander, and handle confirmed incidents through containment, eradication, and recovery as defined in the incident response plan, escalating high-severity incidents to {{ escalation_contacts }}.

Objective

Ensure suspected incidents are evaluated quickly and consistently and that confirmed incidents are contained and resolved before they cause further harm.

Implementation guidance

Route monitoring alerts and employee or customer reports into a single on-call intake such as a paging tool or dedicated incident channel. Define a severity matrix (for example SEV1-SEV4) keyed on data exposure, customer impact, and blast radius. Keep runbooks for common cloud SaaS scenarios such as compromised credentials, leaked secrets, malicious dependencies, and cloud account takeover: revoke sessions and keys, isolate workloads with security groups or by scaling to zero, and snapshot volumes and preserve logs for forensics before rebuilding. Coordinate with the disaster recovery plan when recovery requires restoration from backup. Evidence is the incident ticket showing triage time, severity, commander, and response actions.

Parameters (3)

  • {{ escalation_contacts }} — High-severity escalation contacts (default: the security lead and executive leadership)
  • {{ severity_scale }} — Incident severity classification scheme (default: the documented incident severity matrix)
  • {{ triage_sla }} — Incident triage time limit (default: 1 hour)

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-53-r5-ir-4#a reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-ir-4#d reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-3 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-4 reviewed
OGRL-IR-03 Incident Tracking and Documentation ir detective event-driven 3 crosswalks
control--ogrl-ir-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Record every security incident in {{ incident_tracking_system }} from detection through closure, capturing at minimum the detection source, timeline, severity, affected systems and data, actions taken, responsible owner, and resolution, and retain incident records for {{ incident_record_retention }}.

Objective

Maintain a complete and reliable history of incidents that supports coordinated response, trend analysis, and audit evidence.

Implementation guidance

Use a dedicated ticket type or project with mandatory fields rather than free-form chat threads, and link alerts, incident channel exports, and post-incident reviews to the record. Restrict who can delete incident records. Report incident counts, time to detect, and time to resolve to leadership periodically. Auditors typically sample incidents for completeness, so keep the register even in periods with no incidents and document that none occurred.

Parameters (2)

  • {{ incident_record_retention }} — Incident record retention period (default: at least 3 years)
  • {{ incident_tracking_system }} — Incident tracking system (default: a dedicated incident ticket queue with mandatory fields)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-ir-5 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-3 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-4 reviewed
OGRL-IR-04 Incident Reporting and Customer Notification ir corrective event-driven 4 crosswalks
control--ogrl-ir-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Require personnel to report suspected security incidents to the security team through a published reporting channel within {{ internal_report_window }} of discovery, and report confirmed incidents affecting customer data or services to {{ external_notification_recipients }} within {{ external_notification_deadline }} of confirmation, or sooner where contract or law requires.

Objective

Ensure incidents reach the response team quickly and that external parties who rely on the system learn of incidents affecting them in time to protect themselves.

Implementation guidance

Publish a reporting channel such as a security@ alias or chat channel and cover it in onboarding and awareness training. Maintain a notification matrix of contractual (MSA, DPA) and regulatory deadlines, such as GDPR supervisory-authority notice within 72 hours or public-company disclosure rules, and have legal review external notices. Keep pre-approved notification templates and use the status page for availability incidents. Retain copies of sent notifications as evidence.

Parameters (3)

  • {{ external_notification_deadline }} — External notification deadline (default: 72 hours)
  • {{ external_notification_recipients }} — External incident notification recipients (default: affected customers, regulators, law enforcement, and other parties as required by contract or law )
  • {{ internal_report_window }} — Internal reporting time limit (default: 24 hours)

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-53-r5-ir-6#a reviewed (maps ir_06_odp_01←internal_report_window)
  • equivalent-to → requirement--nist-sp-800-53-r5-ir-6#b reviewed (maps ir_06_odp_02←external_notification_recipients)
  • intersects-with → requirement--soc2-tsc-2017-cc2-3 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-4 reviewed
OGRL-IR-05 Post-Incident Review ir corrective event-driven 2 crosswalks
control--ogrl-ir-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Complete a documented post-incident review within {{ review_deadline }} of resolving each incident rated {{ review_severity_threshold }}, identifying root cause and contributing factors, and track the resulting corrective actions to closure, including updates to incident response procedures, training, and testing.

Objective

Prevent recurrence of incidents and continuously improve detection, response, and recovery capability.

Implementation guidance

Use a blameless postmortem template covering timeline, impact, root cause, detection gaps, and what went well. File corrective actions in the engineering backlog with owners and due dates and review open items in a recurring security meeting. Feed real incident scenarios into the next tabletop exercise (OGRL-IR-01) and update runbooks and detection rules. Evidence is the completed review linked to the incident record and the closed corrective-action tickets.

Parameters (2)

  • {{ review_deadline }} — Post-incident review deadline (default: 10 business days)
  • {{ review_severity_threshold }} — Severity requiring a post-incident review (default: high or critical severity)

Reviewed framework crosswalks (2)

  • equivalent-to → requirement--nist-sp-800-53-r5-ir-4#c reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-5 reviewed
OGRL-IR-06 Privacy Breach Handling and Notification ir corrective event-driven 3 crosswalks
control--ogrl-ir-06 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

For each incident involving personal information, follow the breach-response procedure in the incident response plan to assess the data and individuals affected, the likely harm to them, and available mitigations; determine notification obligations under {{ applicable_privacy_requirements }}; notify affected individuals and regulators within {{ breach_notification_deadline }} when required; and record the breach, harm assessment, and notification decision in {{ breach_register }}.

Objective

Ensure breaches of personal information are evaluated for harm, mitigated, and reported to affected individuals and authorities as legally and contractually required.

Implementation guidance

Maintain a jurisdiction matrix of breach notification rules (for example GDPR 72-hour supervisory-authority notice, US state breach laws, HIPAA, and customer DPAs) and involve privacy counsel in every assessment. Consider data sensitivity, encryption status, and likelihood of misuse when assessing harm, and offer mitigations such as forced credential resets or credit monitoring where appropriate. Record decisions not to notify with their rationale. Where the organization acts as a processor, notify the controlling customer rather than individuals directly.

Parameters (3)

  • {{ applicable_privacy_requirements }} — Applicable privacy and breach notification requirements (default: applicable privacy and breach notification laws, regulations, and customer contracts )
  • {{ breach_notification_deadline }} — Breach notification deadline (default: the shortest applicable legal or contractual deadline)
  • {{ breach_register }} — Breach record location (default: the privacy breach register)

Reviewed framework crosswalks (3)

  • superset-of → requirement--nist-sp-800-53-r5-ir-8-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-p6-3 reviewed
  • intersects-with → requirement--soc2-tsc-2017-p6-6 reviewed
OGRL-LM-01 Centralized Security Audit Logging and Retention lm detective continuous 6 crosswalks
control--ogrl-lm-01 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Log {{ logged_events }} across all in-scope systems to a centralized, access-controlled log store, review logging coverage {{ logging_review_cadence }}, and retain audit records for at least {{ retention_period }}.

Objective

Maintain reliable, tamper-resistant audit trails sufficient for forensic investigation and accountability.

Implementation guidance

Synchronize system clocks via NTP, enforce append-only or write-once storage policies on log buckets, and ensure log shippers alert on ingestion drops.

Parameters (3)

  • {{ logged_events }} — Auditable security event types (default: authentication attempts, privilege changes, configuration mutations, and sensitive data access )
  • {{ logging_review_cadence }} — Logging scope review cadence (default: annually)
  • {{ retention_period }} — Minimum audit log retention period (default: 365 days)

Library tests (1)

  • automated · daily · required — Verify Centralized Audit Logging Ingestion and Retention: Confirm audit logging is enabled across all production accounts, logs flow into the central store, and bucket retention policies meet or exceed the configured minimum.

Reviewed framework crosswalks (6)

  • equivalent-to → requirement--iso-iec-27001-2022-a-8-15 reviewed
  • equivalent-to → requirement--nist-sp-800-171-r3-03-03-01 reviewed (maps a_03_03_01_odp_01←logged_events, a_03_03_01_odp_02←logging_review_cadence)
  • equivalent-to → requirement--nist-sp-800-53-r5-au-11 reviewed (maps au_11_odp←retention_period)
  • equivalent-to → requirement--nist-sp-800-53-r5-au-2#a reviewed (maps au_02_odp_01←logged_events)
  • equivalent-to → requirement--nist-sp-800-53-r5-au-2#e reviewed (maps au_02_odp_04←logging_review_cadence)
  • subset-of → requirement--soc2-tsc-2017-cc7-2 reviewed
OGRL-LM-02 Continuous Security Monitoring and Alert Triage lm detective continuous 4 crosswalks
control--ogrl-lm-02 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Continuously monitor system and security telemetry using {{ monitoring_methods }} to detect {{ monitoring_objectives }}, routing actionable alerts to {{ alert_recipients }} for triage within {{ triage_sla }}.

Objective

Detect unauthorized activity, intrusion attempts, and security anomalies quickly enough to contain impact.

Implementation guidance

Tune SIEM/EDR rules to minimize alert fatigue, document escalation runbooks, and test alerting pipelines periodically.

Parameters (4)

  • {{ alert_recipients }} — Alert response recipients (default: the on-call security operations team)
  • {{ monitoring_methods }} — Detection techniques and tools (default: automated SIEM correlation rules and cloud threat detection)
  • {{ monitoring_objectives }} — Security monitoring objectives (default: unauthorized access, privilege escalation, malware execution, and anomalous data egress )
  • {{ triage_sla }} — High-severity alert triage SLA (default: 4 hours)

Library tests (1)

  • automated · daily · required — Verify Active Threat Detection and Alert Routing: Confirm threat detection rules are active, alert delivery channels are healthy, and open high-severity alerts are triaged within SLA.

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-53-r5-si-4#a.1 reviewed (maps si_04_odp_01←monitoring_objectives)
  • equivalent-to → requirement--nist-sp-800-53-r5-si-4#b reviewed (maps si_04_odp_02←monitoring_methods)
  • equivalent-to → requirement--nist-sp-800-53-r5-si-4#g reviewed (maps si_04_odp_04←alert_recipients)
  • equivalent-to → requirement--soc2-tsc-2017-cc7-2 reviewed
OGRL-LM-03 Audit Log Protection lm preventive continuous 4 crosswalks
control--ogrl-lm-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Store audit logs in {{ log_store }} with immutable or write-once retention, restrict read access to {{ log_reader_roles }}, prevent modification or deletion by any user including administrators of the logged systems, and alert {{ log_tamper_alert_recipients }} on attempts to disable logging, change log configuration, or delete log data.

Objective

Preserve the integrity and confidentiality of audit trails so they remain trustworthy for investigations.

Implementation guidance

Ship logs to a separate logging account or project with S3 Object Lock, GCS bucket lock, or equivalent retention locks. Deny log deletion and trail modification with organization policies. Alert on events such as StopLogging, DeleteTrail, or sink deletion. Log generation and retention periods are covered by OGRL-LM-01.

Parameters (3)

  • {{ log_reader_roles }} — Roles permitted to read audit logs (default: security and designated on-call engineering roles)
  • {{ log_store }} — Protected log storage location (default: a dedicated logging account or project separate from production workloads)
  • {{ log_tamper_alert_recipients }} — Log tampering alert recipients (default: the security on-call team)

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-53-r5-au-9#a reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-au-9#b reviewed (maps au_09_odp←log_tamper_alert_recipients)
  • subset-of → requirement--soc2-tsc-2017-cc6-1 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc7-2 reviewed
OGRL-LM-04 Audit Log Review and Analysis lm detective weekly 6 crosswalks
control--ogrl-lm-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Review and analyze {{ reviewed_log_sources }} {{ log_review_frequency }} for indications of {{ reviewed_activity }}, document each review with reviewer, date, and findings, report findings to {{ log_review_report_recipients }}, and increase review scope or frequency when incidents, threat intelligence, or significant system changes indicate elevated risk.

Objective

Identify inappropriate or unusual activity that automated alerting may not catch, and leave evidence that review occurred.

Implementation guidance

Use saved SIEM queries or dashboards for each review so it is repeatable, and record the review as a ticket with the query output attached. Focus on privileged and administrative actions, break-glass usage, and changes to security tooling. Real-time automated alerting is covered by OGRL-LM-02.

Parameters (4)

  • {{ log_review_frequency }} — Log review frequency (default: weekly)
  • {{ log_review_report_recipients }} — Log review finding recipients (default: the security lead and affected system owners)
  • {{ reviewed_activity }} — Activity sought in log review (default: unauthorized privileged actions, anomalous authentication patterns, and disabled or modified security controls )
  • {{ reviewed_log_sources }} — Logs subject to periodic review (default: privileged and administrative activity logs, authentication logs, and security tooling configuration changes )

Reviewed framework crosswalks (6)

  • equivalent-to → requirement--nist-sp-800-53-r5-au-6#a reviewed (maps au_06_odp_01←log_review_frequency, au_06_odp_02←reviewed_activity)
  • equivalent-to → requirement--nist-sp-800-53-r5-au-6#b reviewed (maps au_06_odp_03←log_review_report_recipients)
  • equivalent-to → requirement--nist-sp-800-53-r5-au-6#c reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc4-1 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc7-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-3 reviewed
OGRL-LM-05 Processing Monitoring and Reconciliation lm detective daily 1 crosswalks
control--ogrl-lm-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Monitor {{ monitored_processing_jobs }} for failures, delays, and incomplete runs, reconcile record counts or control totals between inputs and outputs {{ reconciliation_frequency }}, and route discrepancies to {{ processing_owner }} for investigation and correction within {{ discrepancy_resolution_sla }}.

Objective

Detect and correct incomplete or inaccurate processing before it affects customers or downstream systems.

Implementation guidance

Emit job success, duration, and record-count metrics and alert on failures, missed schedules, and dead-letter queue depth. Automate reconciliation queries that compare source and destination counts or sums and open a ticket on mismatch. Evidence is the alert configuration plus a sample of reconciliation results and resolved discrepancy tickets.

Parameters (4)

  • {{ discrepancy_resolution_sla }} — Discrepancy resolution SLA (default: 2 business days)
  • {{ monitored_processing_jobs }} — Processing monitored for completeness (default: scheduled jobs, data pipelines, and queue consumers that process customer data)
  • {{ processing_owner }} — Discrepancy owner (default: the owning engineering team)
  • {{ reconciliation_frequency }} — Reconciliation frequency (default: daily)

Reviewed framework crosswalks (1)

  • subset-of → requirement--soc2-tsc-2017-pi1-3 reviewed
OGRL-PR-01 Privacy Notice pr preventive annual 2 crosswalks
control--ogrl-pr-01 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Publish a plain-language privacy notice at {{ notice_locations }} that is available before or at first collection of personal information and that states the purposes and legal basis for processing and includes {{ notice_contents }}; review the notice {{ notice_review_cadence }} and before any material change in processing, and inform affected individuals of material changes {{ notice_change_lead_time }}.

Objective

Ensure individuals are informed about how their personal information is processed before and while it is processed.

Implementation guidance

Link the notice from sign-up flows, the website footer, and mobile app settings; keep a version history with effective dates. Have legal or the privacy lead confirm the notice still matches the PII inventory at each review.

Parameters (4)

  • {{ notice_change_lead_time }} — Advance notice of material changes (default: at least 30 days before they take effect)
  • {{ notice_contents }} — Required privacy notice contents (default: data categories, sources, recipients, retention, individual rights, and contacts)
  • {{ notice_locations }} — Privacy notice locations (default: the public website and every point where personal information is collected)
  • {{ notice_review_cadence }} — Privacy notice review frequency (default: annually)

Reviewed framework crosswalks (2)

  • equivalent-to → requirement--nist-sp-800-53-r5-pt-5 reviewed (maps pt_05_odp_02←notice_contents)
  • subset-of → requirement--soc2-tsc-2017-p1-1 reviewed
OGRL-PR-02 Consent Management pr preventive event-driven 3 crosswalks
control--ogrl-pr-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Where consent is the basis for processing, obtain informed, affirmative consent through {{ consent_mechanism }} before collecting personal information, obtain separate explicit consent before collecting {{ sensitive_pii_categories }}, record each consent with the individual, scope, timestamp, and notice version, and give effect to consent withdrawals within {{ consent_withdrawal_sla }}.

Objective

Ensure personal information processed on the basis of consent is backed by a valid, provable, and revocable consent.

Implementation guidance

Use unchecked opt-in boxes or a consent management platform; store consent records in a system queryable by user ID. Withdrawal should be as easy as giving consent and must propagate to downstream processors such as marketing tools.

Parameters (3)

  • {{ consent_mechanism }} — Consent collection mechanism (default: unbundled opt-in controls presented with a link to the privacy notice)
  • {{ consent_withdrawal_sla }} — Consent withdrawal processing SLA (default: 10 business days)
  • {{ sensitive_pii_categories }} — Sensitive personal information categories (default: health, biometric, financial, precise location, or government ID data)

Reviewed framework crosswalks (3)

  • superset-of → requirement--nist-sp-800-53-r5-pt-4 reviewed (maps pt_04_odp←consent_mechanism)
  • subset-of → requirement--soc2-tsc-2017-p2-1 reviewed
  • subset-of → requirement--soc2-tsc-2017-p3-2 reviewed
OGRL-PR-03 Purpose Specification and Use Limitation pr preventive event-driven 4 crosswalks
control--ogrl-pr-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Document the purposes and legal authority for each personal information processing activity, reflect those purposes in the privacy notice, restrict collection and use of personal information to the documented purposes, and require {{ purpose_change_review }} before personal information is processed for a new or changed purpose.

Objective

Prevent personal information from being used for purposes individuals were not told about or that lack a legal basis.

Implementation guidance

Record purposes and legal basis per processing activity in the PII inventory (pr-05). Add a privacy checkbox to product and data-pipeline design reviews so new uses (analytics, ML training, marketing) trigger review before launch.

Parameters (1)

  • {{ purpose_change_review }} — Review required for new or changed purposes (default: a documented privacy review approved by the privacy lead)

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-53-r5-pt-2 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-pt-3 reviewed (maps pt_03_odp_03←purpose_change_review)
  • intersects-with → requirement--soc2-tsc-2017-p3-1 reviewed
  • subset-of → requirement--soc2-tsc-2017-p4-1 reviewed
OGRL-PR-04 PII Minimization pr preventive annual 3 crosswalks
control--ogrl-pr-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Limit personal information collected and processed to {{ permitted_pii_elements }}, require {{ pii_element_approver }} to approve any new personal information element before collection begins, and review collection points and data stores {{ minimization_review_cadence }} to remove elements no longer needed.

Objective

Reduce privacy risk and breach impact by holding no more personal information than each purpose requires.

Implementation guidance

Enforce minimization in form and API schemas, and use data discovery or schema diffs to spot unapproved fields. Prefer pseudonymized or aggregated data for analytics and testing.

Parameters (3)

  • {{ minimization_review_cadence }} — Minimization review frequency (default: annually)
  • {{ permitted_pii_elements }} — Permitted personal information elements (default: the elements approved for each processing activity in the PII inventory)
  • {{ pii_element_approver }} — Approver for new personal information elements (default: the privacy lead)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-si-12-1 reviewed (maps si_12_01_odp←permitted_pii_elements)
  • subset-of → requirement--soc2-tsc-2017-p3-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-p4-1 reviewed
OGRL-PR-05 PII Inventory and Processing Records pr detective annual 3 crosswalks
control--ogrl-pr-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain an inventory of systems, applications, vendors, and projects that process personal information, recording for each the personal information categories, data subjects, purposes, legal basis, storage locations, recipients, and retention period; update it when processing changes and review it in full {{ pii_inventory_review_cadence }}.

Objective

Provide an accurate record of where personal information lives and how it flows, enabling notice, rights requests, and risk management.

Implementation guidance

A spreadsheet or data-map tool is sufficient; seed it from the system and vendor inventories and data-discovery scans. Make updates part of the change and vendor-onboarding workflows.

Parameters (1)

  • {{ pii_inventory_review_cadence }} — PII inventory review frequency (default: annually)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-pm-5-1 reviewed (maps pm_05_01_odp←pii_inventory_review_cadence)
  • intersects-with → requirement--soc2-tsc-2017-p4-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-p6-7 reviewed
OGRL-PR-06 Data Subject Access Requests pr corrective event-driven 2 crosswalks
control--ogrl-pr-06 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Provide {{ access_request_channels }} through which individuals can request access to their personal information, verify the requester's identity using {{ requester_verification_method }}, provide {{ access_request_elements }} within {{ access_request_sla }}, and log each request, its outcome, and the reason for any denial.

Objective

Enable individuals to learn what personal information the organization holds about them in a timely and secure manner.

Implementation guidance

Track requests in a ticketing queue with due dates; use the PII inventory (pr-05) to locate data across systems and processors. Avoid over-collecting identity documents for verification; matching account login or a verified email is usually enough.

Parameters (4)

  • {{ access_request_channels }} — Access request channels (default: a web form and a published privacy email address)
  • {{ access_request_elements }} — Personal information disclosed in response (default: a copy of their personal information and its categories, sources, and recipients)
  • {{ access_request_sla }} — Access request response SLA (default: 30 days)
  • {{ requester_verification_method }} — Requester identity verification method (default: account authentication or confirmation via the email address on file)

Reviewed framework crosswalks (2)

  • equivalent-to → requirement--nist-sp-800-53-r5-ac-3-14 reviewed (maps ac_03_14_odp_01←access_request_channels, ac_03_14_odp_02←access_request_elements)
  • subset-of → requirement--soc2-tsc-2017-p5-1 reviewed
OGRL-PR-07 Data Subject Correction Requests pr corrective event-driven 2 crosswalks
control--ogrl-pr-07 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Accept requests from individuals or their authorized representatives to correct or delete their personal information, verify the requester's identity, complete the correction or deletion within {{ correction_request_sla }} across all systems in the PII inventory, notify third parties that received the information, and record the reason when a request is denied and communicate it to the requester.

Objective

Ensure individuals can have inaccurate or unwanted personal information fixed or removed and that changes reach downstream recipients.

Implementation guidance

Reuse the access-request intake and ticket queue (pr-06). Automate deletion through account-deletion workflows where possible and keep evidence of processor notifications. Legal holds and retention obligations are valid denial reasons when documented.

Parameters (1)

  • {{ correction_request_sla }} — Correction or deletion request SLA (default: 30 days)

Reviewed framework crosswalks (2)

  • equivalent-to → requirement--nist-sp-800-53-r5-si-18-4 reviewed
  • subset-of → requirement--soc2-tsc-2017-p5-2 reviewed
OGRL-PR-08 Third-Party Disclosure Authorization pr preventive event-driven 2 crosswalks
control--ogrl-pr-08 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Before disclosing personal information to a new third party or for a new purpose in {{ disclosure_circumstances }}, require {{ disclosure_approver }} to confirm that the disclosure is consistent with the privacy notice and any consent obtained and that a written agreement binds the recipient to equivalent privacy and confidentiality obligations.

Objective

Ensure personal information is shared only with recipients and for uses that individuals were informed of and that contracts restrict.

Implementation guidance

Embed the privacy check in vendor onboarding and in data-sharing requests; maintain the approved recipient list as the public subprocessor list where applicable. A data processing agreement with standard privacy terms meets the written-agreement requirement.

Parameters (2)

  • {{ disclosure_approver }} — Disclosure approval authority (default: the privacy lead)
  • {{ disclosure_circumstances }} — Disclosure circumstances requiring authorization (default: any sharing of personal information with a party outside the organization)

Reviewed framework crosswalks (2)

  • intersects-with → requirement--nist-sp-800-53-r5-ac-21#a reviewed (maps ac_21_odp_01←disclosure_circumstances)
  • subset-of → requirement--soc2-tsc-2017-p6-1 reviewed
OGRL-PR-09 Accounting of Disclosures pr detective event-driven 3 crosswalks
control--ogrl-pr-09 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Record each disclosure of personal information to a third party with the date, nature and purpose of the disclosure, and the recipient's name and contact information, retain each record for {{ disclosure_record_retention }}, and provide individuals with the record of disclosures of their personal information within {{ disclosure_accounting_sla }} of request.

Objective

Maintain a reliable history of who received personal information and why, supporting individual rights and investigations.

Implementation guidance

Routine sharing with contracted processors can be recorded at category level via the subprocessor list and PII inventory; ad hoc disclosures (law enforcement requests, data transfers to partners, unauthorized disclosures found during incidents) should be logged individually in a ticket or register.

Parameters (2)

  • {{ disclosure_accounting_sla }} — Disclosure accounting response SLA (default: 30 days)
  • {{ disclosure_record_retention }} — Disclosure record retention period (default: the longer of the life of the information or five years after disclosure)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-pm-21 reviewed
  • subset-of → requirement--soc2-tsc-2017-p6-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-p6-7 reviewed
OGRL-PR-10 PII Data Quality pr corrective annual 3 crosswalks
control--ogrl-pr-10 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Validate personal information at collection, check the accuracy, completeness, relevance, and timeliness of stored personal information {{ pii_quality_check_cadence }}, and correct or delete inaccurate or outdated personal information within {{ pii_quality_remediation_sla }} of detection.

Objective

Ensure decisions and communications that rely on personal information are based on accurate and current data.

Implementation guidance

Input validation, self-service profile editing, and bounce or undeliverable handling cover most needs. Periodic checks can be automated data-quality queries or stale-record reports reviewed by the data owner.

Parameters (2)

  • {{ pii_quality_check_cadence }} — PII quality check frequency (default: annually)
  • {{ pii_quality_remediation_sla }} — PII quality remediation SLA (default: 30 days)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-si-18#a reviewed (maps si_18_prm_1←pii_quality_check_cadence)
  • equivalent-to → requirement--nist-sp-800-53-r5-si-18#b reviewed
  • subset-of → requirement--soc2-tsc-2017-p7-1 reviewed
OGRL-PR-11 Privacy Inquiry and Complaint Management pr corrective event-driven 3 crosswalks
control--ogrl-pr-11 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Designate {{ privacy_lead_role }} as accountable for privacy inquiries and complaints, publish {{ complaint_channels }} together with the information needed to file a complaint, track each inquiry or complaint to closure, acknowledge it within {{ complaint_acknowledgement_sla }}, respond within {{ complaint_response_sla }}, and resolve or escalate it within {{ complaint_resolution_sla }}.

Objective

Ensure individuals' privacy concerns are heard, addressed in a timely way, and used to improve privacy practices.

Implementation guidance

A shared privacy mailbox feeding a ticket queue with SLA timers is usually enough. Report complaint volume and themes to leadership periodically and feed recurring issues into the privacy risk assessment.

Parameters (5)

  • {{ complaint_acknowledgement_sla }} — Complaint acknowledgement SLA (default: 5 business days)
  • {{ complaint_channels }} — Privacy complaint channels (default: a privacy email address and web form linked from the privacy notice)
  • {{ complaint_resolution_sla }} — Complaint resolution SLA (default: 60 days)
  • {{ complaint_response_sla }} — Complaint response SLA (default: 30 days)
  • {{ privacy_lead_role }} — Accountable privacy role (default: the privacy lead)

Reviewed framework crosswalks (3)

  • subset-of → requirement--nist-sp-800-53-r5-pm-19 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-pm-26 reviewed (maps pm_26_odp_03←complaint_acknowledgement_sla, pm_26_odp_04←complaint_response_sla, pm_26_prm_1←complaint_resolution_sla)
  • subset-of → requirement--soc2-tsc-2017-p8-1 reviewed
OGRL-PS-01 Physical Access Authorization and Review ps preventive quarterly 2 crosswalks
control--ogrl-ps-01 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain a list of individuals authorized to enter {{ controlled_facilities }}, issue badges, keys, or other access credentials only after approval by {{ access_approver }}, review the list {{ access_review_cadence }}, and remove an individual's physical access within {{ access_removal_sla }} of termination or when access is no longer required.

Objective

Ensure only currently authorized individuals hold credentials that grant entry to facilities housing personnel or system components.

Implementation guidance

Use the badge or door-access system as the source of truth and reconcile it against the HR roster during each review; tie offboarding tickets to badge deactivation so removal evidence is automatic. Coworking or shared offices can rely on the landlord's badge system if the organization can obtain the list of its credential holders. Where production runs on a cloud provider, data-center physical controls are inherited from the provider and validated by reviewing its SOC 2 report; offices and any organization-operated server, network, or storage rooms remain in scope.

Parameters (4)

  • {{ access_approver }} — Physical access approval authority (default: the facilities owner or the requester's manager)
  • {{ access_removal_sla }} — Physical access removal SLA (default: 1 business day)
  • {{ access_review_cadence }} — Physical access list review frequency (default: quarterly)
  • {{ controlled_facilities }} — Controlled facilities (default: company offices and any organization-operated server, network, or storage rooms)

Reviewed framework crosswalks (2)

  • equivalent-to → requirement--nist-sp-800-53-r5-pe-2 reviewed (maps pe_02_odp←access_review_cadence)
  • subset-of → requirement--soc2-tsc-2017-cc6-4 reviewed
OGRL-PS-02 Physical Access Control ps preventive continuous 6 crosswalks
control--ogrl-ps-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Enforce physical access authorizations at every entry and exit point of {{ controlled_facilities }} using {{ entry_control_mechanism }}, retain electronic entry logs for {{ entry_log_retention }}, secure unissued keys, badges, and combinations, inventory physical access devices {{ access_device_inventory_cadence }}, and change combinations or rekey locks when a key or code is lost or compromised or its holder leaves.

Objective

Prevent unauthorized individuals from entering facilities that house personnel or system components, and keep a record of who entered.

Implementation guidance

Badge readers that log each entry satisfy both enforcement and logging; areas that rely on physical keys need a key register. Inventory issued badges against ps-01's authorized list to catch orphaned credentials. Where production runs on a cloud provider, data-center physical controls are inherited from the provider and validated by reviewing its SOC 2 report; offices and any organization-operated server, network, or storage rooms remain in scope.

Parameters (4)

  • {{ access_device_inventory_cadence }} — Physical access device inventory frequency (default: annually)
  • {{ controlled_facilities }} — Controlled facilities (default: company offices and any organization-operated server, network, or storage rooms)
  • {{ entry_control_mechanism }} — Entry control mechanism (default: electronic badge readers or keyed locks)
  • {{ entry_log_retention }} — Physical entry log retention (default: 90 days)

Reviewed framework crosswalks (6)

  • equivalent-to → requirement--nist-sp-800-53-r5-pe-3#a reviewed (maps pe_03_odp_02←entry_control_mechanism)
  • equivalent-to → requirement--nist-sp-800-53-r5-pe-3#b reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-pe-3#e reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-pe-3#f reviewed (maps pe_03_odp_08←access_device_inventory_cadence)
  • subset-of → requirement--nist-sp-800-53-r5-pe-3#g reviewed
  • subset-of → requirement--soc2-tsc-2017-cc6-4 reviewed
OGRL-PS-03 Visitor Access Records ps detective monthly 3 crosswalks
control--ogrl-ps-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Record each visitor to {{ controlled_facilities }} with name, organization, host, and times of arrival and departure, escort visitors in non-public areas, retain visitor records for {{ visitor_record_retention }}, review the records {{ visitor_review_cadence }}, and report anomalies to {{ visitor_anomaly_recipient }}.

Objective

Maintain accountability for non-workforce individuals who enter facilities and detect unusual visitor activity.

Implementation guidance

A tablet-based visitor management system or front-desk sign-in sheet both work; capture host and badge-return evidence. Anomalies include unescorted visitors, missing sign-outs, and unreturned visitor badges. In shared buildings, building-reception logs may be used if the organization can retrieve entries for its own visitors. Where production runs on a cloud provider, data-center physical controls are inherited from the provider and validated by reviewing its SOC 2 report; offices and any organization-operated server, network, or storage rooms remain in scope.

Parameters (4)

  • {{ controlled_facilities }} — Controlled facilities (default: company offices and any organization-operated server, network, or storage rooms)
  • {{ visitor_anomaly_recipient }} — Recipient of visitor anomaly reports (default: the security team)
  • {{ visitor_record_retention }} — Visitor record retention period (default: 1 year)
  • {{ visitor_review_cadence }} — Visitor record review frequency (default: monthly)

Reviewed framework crosswalks (3)

  • subset-of → requirement--nist-sp-800-53-r5-pe-3#d reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-pe-8 reviewed (maps pe_08_odp_01←visitor_record_retention, pe_08_odp_02←visitor_review_cadence, pe_08_odp_03←visitor_anomaly_recipient)
  • subset-of → requirement--soc2-tsc-2017-cc6-4 reviewed
OGRL-PS-04 Physical Access Monitoring ps detective monthly 3 crosswalks
control--ogrl-ps-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Monitor entry points of {{ controlled_facilities }} using {{ physical_monitoring_mechanisms }}, review physical access logs {{ access_log_review_cadence }} and upon {{ access_log_review_triggers }}, and escalate suspected physical security incidents to the incident response process.

Objective

Detect unauthorized or suspicious physical access in time to respond and feed findings into incident response.

Implementation guidance

Configure badge-system alerts for forced or held-open doors and after-hours entry, and keep camera footage long enough to support investigations. Record each review (date, reviewer, exceptions) as evidence. Where production runs on a cloud provider, data-center physical controls are inherited from the provider and validated by reviewing its SOC 2 report; offices and any organization-operated server, network, or storage rooms remain in scope.

Parameters (4)

  • {{ access_log_review_cadence }} — Physical access log review frequency (default: monthly)
  • {{ access_log_review_triggers }} — Events triggering an ad hoc log review (default: door alarms, forced-entry alerts, or reported physical security incidents)
  • {{ controlled_facilities }} — Controlled facilities (default: company offices and any organization-operated server, network, or storage rooms)
  • {{ physical_monitoring_mechanisms }} — Physical monitoring mechanisms (default: video surveillance and door alarms or badge-system alerts)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-pe-6 reviewed (maps pe_06_odp_01←access_log_review_cadence, pe_06_odp_02←access_log_review_triggers)
  • subset-of → requirement--soc2-tsc-2017-cc6-4 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-2 reviewed
OGRL-PS-05 Environmental Safeguards ps preventive continuous 5 crosswalks
control--ogrl-ps-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

In each organization-operated facility that houses in-scope system components, maintain {{ environmental_factors }} within {{ environmental_ranges }} and monitor them {{ environmental_monitoring_cadence }} with alerting; provide an uninterruptible power supply sufficient to allow {{ ups_capability }}; employ fire detection and suppression systems with an independent power source; and keep master water shutoff or isolation valves accessible, working, and known to facilities personnel.

Objective

Prevent loss of availability or equipment damage from environmental hazards in facilities the organization operates.

Implementation guidance

Applies only to server rooms, network closets, or on-premises data centers run by the organization. For cloud-hosted production, these safeguards are inherited from the provider and validated through its SOC 2 report; document the inheritance and review the report each year. Office spaces with only laptops and a network switch typically need only UPS for network gear and landlord-provided fire protection.

Parameters (4)

  • {{ environmental_factors }} — Environmental factors controlled (default: temperature and humidity)
  • {{ environmental_monitoring_cadence }} — Environmental monitoring frequency (default: continuously)
  • {{ environmental_ranges }} — Acceptable environmental ranges (default: the equipment manufacturer's recommended operating ranges)
  • {{ ups_capability }} — Uninterruptible power supply capability (default: an orderly shutdown of in-scope systems)

Reviewed framework crosswalks (5)

  • equivalent-to → requirement--nist-sp-800-53-r5-pe-11 reviewed (maps pe_11_odp←ups_capability)
  • equivalent-to → requirement--nist-sp-800-53-r5-pe-13 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-pe-14 reviewed (maps pe_14_odp_01←environmental_factors, pe_14_odp_03←environmental_ranges, pe_14_odp_04←environmental_monitoring_cadence)
  • equivalent-to → requirement--nist-sp-800-53-r5-pe-15 reviewed
  • subset-of → requirement--soc2-tsc-2017-a1-2 reviewed
OGRL-PS-06 Equipment Delivery and Removal ps preventive event-driven 3 crosswalks
control--ogrl-ps-06 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Authorize and record {{ controlled_component_types }} entering and leaving {{ controlled_facilities }}, require approval from {{ removal_approver }} before such components are removed, and record the asset identifier, date, responsible person, and purpose of each movement in the asset inventory.

Objective

Ensure that system components cannot enter or leave organization facilities without authorization and a traceable record.

Implementation guidance

Track movements in the asset management system or ticketing tool; laptops assigned to employees for routine use need not be logged at each trip, but receipt, reassignment, repair shipment, and disposal should be. Pair with media sanitization controls for components leaving for repair or disposal. Where production runs on a cloud provider, data-center physical controls are inherited from the provider and validated by reviewing its SOC 2 report; offices and any organization-operated server, network, or storage rooms remain in scope.

Parameters (3)

  • {{ controlled_component_types }} — Component types subject to movement control (default: servers, network devices, storage media, and workforce endpoints)
  • {{ controlled_facilities }} — Controlled facilities (default: company offices and any organization-operated server, network, or storage rooms)
  • {{ removal_approver }} — Equipment removal approval authority (default: IT or the asset owner)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-pe-16 reviewed (maps pe_16_prm_1←controlled_component_types)
  • subset-of → requirement--soc2-tsc-2017-cc6-4 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-5 reviewed
OGRL-PS-07 Facility and Infrastructure Maintenance ps preventive quarterly 6 crosswalks
control--ogrl-ps-07 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Schedule maintenance of in-scope system components and supporting facility infrastructure in organization-operated facilities according to manufacturer or vendor specifications, require approval by {{ maintenance_approver }} for maintenance activities and for removing components off-site for service, verify affected safeguards function after maintenance, record {{ maintenance_record_contents }}, and review maintenance records {{ maintenance_review_cadence }}.

Objective

Keep supporting infrastructure reliable and ensure maintenance does not introduce unauthorized changes or degrade safeguards.

Implementation guidance

Supporting infrastructure includes UPS units, HVAC, fire suppression, generators, and on-premises network or server hardware. Keep vendor service reports with the maintenance record. For cloud-hosted production, data-center maintenance is inherited from the provider and validated through its SOC 2 report; this control then covers only office or organization-operated equipment rooms.

Parameters (3)

  • {{ maintenance_approver }} — Maintenance approval authority (default: the facilities or IT owner)
  • {{ maintenance_record_contents }} — Required maintenance record contents (default: date, component, maintenance performed, performer, and approver)
  • {{ maintenance_review_cadence }} — Maintenance record review frequency (default: quarterly)

Reviewed framework crosswalks (6)

  • equivalent-to → requirement--nist-sp-800-53-r5-ma-2#a reviewed
  • subset-of → requirement--nist-sp-800-53-r5-ma-2#b reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ma-2#c reviewed (maps ma_02_odp_01←maintenance_approver)
  • equivalent-to → requirement--nist-sp-800-53-r5-ma-2#e reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ma-2#f reviewed (maps ma_02_odp_03←maintenance_record_contents)
  • intersects-with → requirement--soc2-tsc-2017-a1-2 reviewed
OGRL-RM-01 Risk Management Strategy rm preventive annual 5 crosswalks
control--ogrl-rm-01 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain a documented risk management methodology that defines risk appetite and tolerance thresholds, likelihood and impact scoring criteria, the treatment options available, and that risk acceptance requires approval by {{ risk_acceptance_authority }}. The methodology is approved by {{ strategy_approver }} and reviewed and updated {{ strategy_review_frequency }} or when significant organizational changes occur.

Objective

Risks are identified, rated, and treated consistently against criteria that leadership has approved.

Implementation guidance

A two-page method is enough for a startup: a 5x5 likelihood and impact matrix with defined levels, a tolerance line above which risks must be treated, and named acceptance authority by risk level. The risk assessment (OGRL-RM-02) and treatment tracking (OGRL-RM-04) apply this method.

Parameters (3)

  • {{ risk_acceptance_authority }} — Risk acceptance authority (default: the CEO for high risks and the security leader for others)
  • {{ strategy_approver }} — Methodology approver (default: executive leadership)
  • {{ strategy_review_frequency }} — Methodology review frequency (default: at least annually)

Reviewed framework crosswalks (5)

  • equivalent-to → requirement--nist-sp-800-53-r5-pm-9#a.1 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-pm-9#c reviewed (maps pm_09_odp←strategy_review_frequency)
  • intersects-with → requirement--soc2-tsc-2017-cc3-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc3-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc9-1 reviewed
OGRL-RM-02 Periodic Risk Assessment rm detective annual 7 crosswalks
control--ogrl-rm-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Perform a risk assessment of in-scope systems {{ risk_assessment_frequency }} that identifies threats and vulnerabilities, including those arising from vendors and subservice organizations, and rates the likelihood and impact of each risk using the approved methodology. Record results in {{ risk_register }} and communicate them to {{ results_audience }}.

Objective

Leadership has a current, rated view of the risks to in-scope systems and the data they handle.

Implementation guidance

Run a structured workshop with engineering, product, and operations; seed it with incidents, vulnerability trends, vendor reviews, and audit findings from the period. Each register entry needs a description, affected assets, inherent rating, existing controls, residual rating, and owner. Evidence: the dated register snapshot and its sign-off.

Parameters (3)

  • {{ results_audience }} — Recipients of risk assessment results (default: executive leadership and the board or its designated committee)
  • {{ risk_assessment_frequency }} — Risk assessment frequency (default: at least annually)
  • {{ risk_register }} — Location of documented results (default: the risk register)

Reviewed framework crosswalks (7)

  • equivalent-to → requirement--nist-sp-800-53-r5-ra-3#a.1 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ra-3#a.2 reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ra-3#c reviewed (maps ra_03_odp_02←risk_register)
  • equivalent-to → requirement--nist-sp-800-53-r5-ra-3#e reviewed (maps ra_03_odp_04←results_audience)
  • subset-of → requirement--nist-sp-800-53-r5-ra-3#f reviewed (maps ra_03_odp_05←risk_assessment_frequency)
  • intersects-with → requirement--soc2-tsc-2017-cc3-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc3-2 reviewed
OGRL-RM-03 Fraud Risk Assessment rm detective annual 2 crosswalks
control--ogrl-rm-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Assess fraud risk {{ fraud_assessment_frequency }}, considering motive, opportunity, and rationalization for the workforce and third parties, the potential for management override of controls, and fraud scenarios relevant to the system such as misuse of privileged access or manipulation of customer or billing data. Document each scenario with its rating and mitigating controls, and review the results with {{ fraud_review_audience }}.

Objective

The organization has considered how fraud could compromise its systems and commitments, and each identified scenario has a documented response.

Implementation guidance

Perform it as a dedicated section of the annual risk assessment (OGRL-RM-02) and record scenarios in the same register with a fraud tag. Typical SaaS scenarios: an engineer altering production data, an admin granting themselves access, payment redirection through a vendor change request, and executives bypassing change approval. Evidence: the fraud section of the assessment and its review record.

Parameters (2)

  • {{ fraud_assessment_frequency }} — Fraud risk assessment frequency (default: at least annually)
  • {{ fraud_review_audience }} — Fraud risk review audience (default: executive leadership and the board or its designated committee)

Reviewed framework crosswalks (2)

  • intersects-with → requirement--nist-sp-800-53-r5-ra-3#a.1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc3-3 reviewed
OGRL-RM-04 Risk Treatment Tracking rm corrective quarterly 3 crosswalks
control--ogrl-rm-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

For each risk rated above {{ risk_tolerance_threshold }}, record a treatment decision (mitigate, transfer, avoid, or accept), an owner, and a target date. Risk acceptances require documented approval by {{ risk_acceptance_authority }} and expire after {{ acceptance_duration }}. Review treatment progress and acceptances {{ treatment_review_frequency }}.

Objective

Every risk outside tolerance has an accountable, tracked response consistent with leadership's risk appetite.

Implementation guidance

Track treatment in the risk register or link register entries to tickets. Mitigation plans should reference the controls being added or strengthened; transfer should reference the contract or insurance policy. Evidence: register entries with decisions, approvals, and review dates.

Parameters (4)

  • {{ acceptance_duration }} — Maximum risk acceptance duration (default: 12 months)
  • {{ risk_acceptance_authority }} — Risk acceptance authority (default: the CEO for high risks and the security leader for others)
  • {{ risk_tolerance_threshold }} — Risk tolerance threshold (default: the tolerance level defined in the risk methodology)
  • {{ treatment_review_frequency }} — Treatment review frequency (default: quarterly)

Reviewed framework crosswalks (3)

  • subset-of → requirement--nist-sp-800-53-r5-ra-7 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc3-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc9-1 reviewed
OGRL-RM-05 Significant Change Risk Evaluation rm detective event-driven 2 crosswalks
control--ogrl-rm-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Before a significant change takes effect, including {{ significant_changes }}, evaluate its effect on security risk and on existing controls, document the evaluation, update the risk register, and obtain approval from {{ change_risk_approver }}.

Objective

Risk and control impacts of significant changes are understood and addressed before the changes take effect.

Implementation guidance

Trigger the evaluation from the architecture review or design-doc template, vendor onboarding, and leadership or legal change processes. A short structured note (what changed, new risks, affected controls, decision) linked to the register entry is sufficient. Routine code changes are covered by change management, not this control.

Parameters (2)

  • {{ change_risk_approver }} — Change risk approver (default: the security leader)
  • {{ significant_changes }} — Changes requiring risk evaluation (default: new products or major features, architecture or hosting changes, new critical vendors, acquisitions, leadership changes, and new regulatory obligations )

Reviewed framework crosswalks (2)

  • subset-of → requirement--nist-sp-800-53-r5-ra-3#f reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc3-4 reviewed
OGRL-RM-06 Cyber Insurance rm corrective annual 1 crosswalks
control--ogrl-rm-06 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain cyber liability insurance with limits of at least {{ coverage_minimum }} that covers incident response costs, business interruption, and third-party liability arising from security incidents. Review coverage adequacy against the risk register and customer contractual requirements {{ insurance_review_frequency }}.

Objective

The financial impact of a significant security incident is partially transferred, consistent with risk treatment decisions and customer commitments.

Implementation guidance

Many enterprise customer contracts specify minimum cyber coverage; record those in the commitments register (OGRL-GV-07). Note insurer requirements such as MFA or EDR that become implicit control commitments, and include the carrier's breach hotline in the incident response plan. Evidence: the current certificate of insurance and the renewal review record.

Parameters (2)

  • {{ coverage_minimum }} — Minimum aggregate coverage limit (default: USD 2,000,000 or the highest amount required by customer contracts)
  • {{ insurance_review_frequency }} — Coverage review frequency (default: at least annually at renewal)

Reviewed framework crosswalks (1)

  • intersects-with → requirement--soc2-tsc-2017-cc9-1 reviewed
OGRL-SD-01 Secure Development Lifecycle sd preventive annual 6 crosswalks
control--ogrl-sd-01 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain a documented secure development lifecycle that defines required security activities for design, implementation, testing, release, and maintenance, requires threat modeling for {{ threat_model_triggers }}, applies {{ secure_design_principles }}, assigns security responsibilities to named roles, and is reviewed and approved by {{ sdlc_owner }} {{ sdlc_review_frequency }}.

Objective

Ensure security is designed into systems consistently rather than added after release.

Implementation guidance

Keep the SDLC as a short engineering handbook page that links to the concrete gates: design review template, code review (OGRL-SD-02), automated scanning (OGRL-SD-03), branch protection (OGRL-SD-04), and change testing (OGRL-CM-07). Record approval with a dated sign-off. Reference OWASP SAMM or NIST SSDF if a maturity model is helpful.

Parameters (4)

  • {{ sdlc_owner }} — SDLC approval authority (default: the head of engineering and the security lead)
  • {{ sdlc_review_frequency }} — SDLC review frequency (default: annually)
  • {{ secure_design_principles }} — Secure design principles (default: least privilege, defense in depth, secure defaults, and attack-surface minimization )
  • {{ threat_model_triggers }} — Work requiring threat modeling (default: new services, new external integrations, and major architecture changes)

Reviewed framework crosswalks (6)

  • equivalent-to → requirement--nist-sp-800-53-r5-sa-3#a reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-sa-3#b reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-sa-3#d reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-sa-8 reviewed (maps sa_8_prm_1←secure_design_principles)
  • intersects-with → requirement--soc2-tsc-2017-cc5-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc8-1 reviewed
OGRL-SD-02 Peer Code Review sd preventive event-driven 2 crosswalks
control--ogrl-sd-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Require every pull request that modifies {{ security_sensitive_code }} to be reviewed and approved by {{ security_code_reviewer }} using {{ code_review_techniques }} before merge, enforced through code-owner rules in the source control platform.

Objective

Catch security defects in high-risk code paths that general peer review and automated scanning may miss.

Implementation guidance

Map security-sensitive paths in a CODEOWNERS file to a security reviewer group and enable the require-code-owner-review branch protection setting. General independent peer review of all production changes is covered by OGRL-CM-01; this control adds security-focused review for high-risk code.

Parameters (3)

  • {{ code_review_techniques }} — Security code review technique (default: the organization's secure code review checklist covering OWASP Top 10 weakness classes )
  • {{ security_code_reviewer }} — Security code reviewer (default: a designated security code owner other than the author)
  • {{ security_sensitive_code }} — Security-sensitive code requiring security review (default: authentication, authorization, cryptography, session management, payment, and tenant-isolation code paths )

Reviewed framework crosswalks (2)

  • equivalent-to → requirement--nist-sp-800-53-r5-sa-11-4 reviewed (maps sa_11_04_odp_01←security_sensitive_code, sa_11_04_odp_02←code_review_techniques)
  • subset-of → requirement--soc2-tsc-2017-cc8-1 reviewed
OGRL-SD-03 Static Analysis and Dependency Scanning sd detective event-driven 3 crosswalks
control--ogrl-sd-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Run static application security testing, secret scanning, and software composition analysis on every pull request to {{ scanned_repositories }}, block merge on unresolved findings rated {{ blocking_severity }} or above unless an exception is approved by {{ scan_exception_approver }}, and retain scan results with the change record.

Objective

Prevent common code flaws, leaked secrets, and known-vulnerable dependencies from being merged.

Implementation guidance

Use CI-integrated tools such as CodeQL or Semgrep, GitHub secret scanning with push protection, and Dependabot or Snyk, configured as required status checks. Track approved exceptions with an expiry date. Ongoing scanning of deployed images and dependencies is covered by OGRL-VM-01.

Parameters (3)

  • {{ blocking_severity }} — Minimum blocking severity (default: high)
  • {{ scan_exception_approver }} — Scan exception approver (default: the security lead)
  • {{ scanned_repositories }} — Repositories subject to scanning (default: all repositories that build or deploy production code or infrastructure)

Reviewed framework crosswalks (3)

  • superset-of → requirement--nist-sp-800-53-r5-sa-11-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc7-1 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc8-1 reviewed
OGRL-SD-04 Source Control and Branch Protection sd preventive continuous 3 crosswalks
control--ogrl-sd-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain {{ versioned_assets }} in {{ source_control_platform }}, enforce branch protection on {{ protected_branches }} that blocks direct pushes, force-pushes, and deletion and requires an approved pull request with passing checks to merge, and verify protection settings on all production repositories {{ branch_protection_review_frequency }}.

Objective

Ensure every production change is versioned, attributable, and can only enter protected branches through the approved workflow.

Implementation guidance

Apply organization-level rulesets so new repositories inherit protection, disallow administrator bypass, and require SSO for platform access. Script a quarterly export of branch protection settings across repositories (for example via the GitHub API) as evidence. Review content requirements are covered by OGRL-CM-01 and OGRL-SD-02.

Parameters (4)

  • {{ branch_protection_review_frequency }} — Branch protection verification frequency (default: quarterly)
  • {{ protected_branches }} — Protected branches (default: default and release branches)
  • {{ source_control_platform }} — Source control platform (default: the organization's SSO-enforced source control platform)
  • {{ versioned_assets }} — Assets kept under source control (default: application source code, infrastructure-as-code, CI/CD pipeline definitions, and deployment configuration )

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-sa-10#b reviewed (maps sa_10_odp_02←versioned_assets)
  • subset-of → requirement--nist-sp-800-53-r5-sa-10#c reviewed
  • subset-of → requirement--soc2-tsc-2017-cc8-1 reviewed
OGRL-SD-05 Processing Specifications and Data Definitions sd preventive event-driven 3 crosswalks
control--ogrl-sd-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Document, for each in-scope processing system, the input data definitions, accepted formats and value ranges, processing rules, and expected outputs in version-controlled specifications, update them with every change that alters processing behavior, have them reviewed by {{ spec_owner }} {{ spec_review_frequency }}, and make them available to {{ spec_audience }}.

Objective

Provide a single accurate reference for how each system is expected to process data, so processing can be built, tested, and verified against it.

Implementation guidance

Machine-readable specifications work best: OpenAPI or GraphQL schemas, JSON Schema or protobuf data contracts, and database schema migrations, supplemented by short design notes for business rules. Generate customer-facing API documentation from the same source. Input validation (OGRL-SD-06) and output validation (OGRL-SD-08) should enforce these definitions.

Parameters (3)

  • {{ spec_audience }} — Specification audience (default: engineering, support, and customers through published API documentation)
  • {{ spec_owner }} — Specification owner (default: the product or engineering owner of each system)
  • {{ spec_review_frequency }} — Specification review frequency (default: annually)

Reviewed framework crosswalks (3)

  • intersects-with → requirement--nist-sp-800-53-r5-pl-2#a.5 reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-sa-5#d reviewed (maps sa_05_odp_02←spec_audience)
  • subset-of → requirement--soc2-tsc-2017-pi1-1 reviewed
OGRL-SD-06 Input Validation sd preventive continuous 2 crosswalks
control--ogrl-sd-06 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Validate inputs received through {{ validated_input_channels }} against defined schemas for type, length, format, and range before processing, reject or quarantine invalid inputs and log the reason, and verify validation behavior with automated tests in the CI pipeline.

Objective

Ensure only complete, well-formed, and expected data enters processing, protecting both data accuracy and the application from injection attacks.

Implementation guidance

Enforce validation at the API boundary with schema validators generated from the specification (for example OpenAPI request validation, zod, or pydantic). Use allow-list validation, parameterized queries, and size limits on uploads. Batch imports should report rejected rows back to the submitter.

Parameters (1)

  • {{ validated_input_channels }} — Input channels subject to validation (default: public APIs, user interface forms, file uploads, webhooks, and batch data imports )

Reviewed framework crosswalks (2)

  • equivalent-to → requirement--nist-sp-800-53-r5-si-10 reviewed (maps si_10_odp←validated_input_channels)
  • subset-of → requirement--soc2-tsc-2017-pi1-2 reviewed
OGRL-SD-07 Error Handling sd corrective continuous 3 crosswalks
control--ogrl-sd-07 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Implement application error handling that returns messages giving users enough information to correct the problem without exposing stack traces, internal identifiers, queries, or system details, records detailed error information only in logs accessible to {{ error_detail_roles }}, and rolls back or routes failed transactions to {{ error_queue }} for retry or correction so that no processing failure is silently discarded.

Objective

Ensure processing errors are corrected rather than lost, without leaking information useful to an attacker.

Implementation guidance

Use a global exception handler that maps exceptions to generic responses with a correlation ID. Disable framework debug modes in production. Wrap multi-step writes in transactions and configure dead-letter queues with alerting on depth for asynchronous consumers. Reconciliation of processed volumes is covered by OGRL-LM-05.

Parameters (2)

  • {{ error_detail_roles }} — Roles permitted to view detailed errors (default: authorized engineering and support personnel)
  • {{ error_queue }} — Failed transaction handling destination (default: a monitored dead-letter or error queue)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-si-11#a reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-si-11#b reviewed (maps si_11_odp←error_detail_roles)
  • intersects-with → requirement--soc2-tsc-2017-pi1-3 reviewed
OGRL-SD-08 Output Validation and Distribution sd detective event-driven 2 crosswalks
control--ogrl-sd-08 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Validate outputs from {{ validated_output_sources }} against expected schemas, record counts, or control totals before release, deliver outputs only to authorized recipients through {{ output_delivery_channels }}, and hold, investigate, and correct any output that fails validation before it is redistributed.

Objective

Ensure outputs are complete, accurate, and reach only their intended recipients.

Implementation guidance

Apply response schema validation in API tests, compare export row counts with source query counts, and enforce tenant scoping on download and API endpoints. Failed validations should block publication and page the owning team.

Parameters (2)

  • {{ output_delivery_channels }} — Authorized output delivery channels (default: authenticated APIs, tenant-scoped downloads, and encrypted transfer channels)
  • {{ validated_output_sources }} — Outputs subject to validation (default: customer-facing reports, data exports, outbound data feeds, and API responses with defined schemas )

Reviewed framework crosswalks (2)

  • superset-of → requirement--nist-sp-800-53-r5-si-15 reviewed (maps si_15_odp←validated_output_sources)
  • subset-of → requirement--soc2-tsc-2017-pi1-4 reviewed
OGRL-TP-01 Vendor Inventory and Risk Tiering tp preventive annual 3 crosswalks
control--ogrl-tp-01 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Maintain an inventory of every third party that stores, processes, or accesses customer data or supports in-scope systems, recording for each its internal owner, services provided, data shared, and a risk tier assigned using {{ tiering_criteria }}; add each vendor to the inventory before production use or data sharing, and review the full inventory {{ inventory_review_frequency }}.

Objective

Know which third parties the service depends on and how much risk each one carries, so oversight effort can be proportionate.

Implementation guidance

Seed the inventory from finance and expense data, SSO application catalogs, and infrastructure-as-code provider lists to catch shadow vendors. Flag subservice organizations that will be carved out of the SOC 2 report. The risk tier drives due diligence depth (OGRL-TP-02) and monitoring cadence (OGRL-TP-04).

Parameters (2)

  • {{ inventory_review_frequency }} — Vendor inventory review frequency (default: at least annually)
  • {{ tiering_criteria }} — Risk tiering criteria (default: the sensitivity of data shared, level of system access, and operational criticality of the service )

Reviewed framework crosswalks (3)

  • subset-of → requirement--nist-sp-800-53-r5-sa-9#b reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-sr-2#a reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc9-2 reviewed
OGRL-TP-02 Vendor Security Due Diligence tp preventive event-driven 2 crosswalks
control--ogrl-tp-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Before onboarding any vendor rated {{ diligence_tiers }}, and again when the services or data shared materially change, assess its security and privacy posture using {{ assessment_evidence }}, document findings and any accepted risks, and obtain approval from {{ vendor_risk_approver }} before contract signature or data sharing.

Objective

Avoid taking on vendors whose security posture is inconsistent with the organization's commitments to customers.

Implementation guidance

Scale the assessment to the tier: an independent assurance report review for critical vendors, a standard questionnaire for moderate ones, and a lightweight checklist for low-risk tools. Route approvals through procurement so contracts cannot be signed without security sign-off. Periodic reassessment after onboarding is covered by OGRL-TP-04.

Parameters (3)

  • {{ assessment_evidence }} — Due diligence evidence (default: a current SOC 2 Type II report, ISO/IEC 27001 certificate, or completed security questionnaire )
  • {{ diligence_tiers }} — Vendor tiers requiring due diligence (default: high or moderate risk)
  • {{ vendor_risk_approver }} — Vendor risk approval authority (default: the security team)

Reviewed framework crosswalks (2)

  • subset-of → requirement--nist-sp-800-53-r5-sr-6 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc9-2 reviewed
OGRL-TP-03 Vendor Contract Security and Privacy Requirements tp preventive event-driven 6 crosswalks
control--ogrl-tp-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Execute a written agreement with every vendor that will store, process, or access confidential or personal data before sharing that data, including security and confidentiality obligations, data protection terms that restrict use to the contracted purpose, notification of security incidents or unauthorized disclosures affecting organizational data within {{ breach_notification_window }}, disclosure of subprocessors, return or deletion of data at termination, and the right to obtain {{ assurance_rights }}.

Objective

Make vendors contractually accountable for protecting the organization's and its customers' data.

Implementation guidance

Maintain a standard security addendum and data processing agreement; legal tracks deviations and security approves them. Align the vendor notification window with the organization's own customer notification commitments. Record contract status in the vendor inventory so missing agreements are visible.

Parameters (2)

  • {{ assurance_rights }} — Assurance rights required from vendors (default: independent audit reports or security questionnaire responses at least annually)
  • {{ breach_notification_window }} — Vendor breach notification deadline (default: 72 hours)

Reviewed framework crosswalks (6)

  • intersects-with → requirement--nist-sp-800-53-r5-sa-4 reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-sr-3#b reviewed
  • intersects-with → requirement--soc2-tsc-2017-c1-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc9-2 reviewed
  • intersects-with → requirement--soc2-tsc-2017-p6-4 reviewed
  • intersects-with → requirement--soc2-tsc-2017-p6-5 reviewed
OGRL-TP-04 Ongoing Vendor Monitoring and SOC Report Review tp detective annual 3 crosswalks
control--ogrl-tp-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

For each vendor rated {{ monitored_tiers }}, obtain and review {{ assurance_evidence }} {{ monitoring_frequency }}; evaluate reported exceptions, coverage gaps, and complementary user entity controls the organization must operate; track remediation of identified issues; and record the review outcome and any risk acceptance.

Objective

Detect deterioration in vendor security posture and confirm the organization performs its share of vendor-dependent controls.

Implementation guidance

Track report periods and request bridge letters when coverage lapses. Map each relevant complementary user entity control to an internal control or owner. Subservice organizations carved out of the organization's own SOC 2 report need this review as evidence of monitoring. Also monitor public breach disclosures for critical vendors.

Parameters (3)

  • {{ assurance_evidence }} — Vendor assurance evidence reviewed (default: the vendor's most recent SOC 2 Type II report, ISO/IEC 27001 certificate, or equivalent independent assessment )
  • {{ monitored_tiers }} — Vendor tiers subject to periodic monitoring (default: high risk)
  • {{ monitoring_frequency }} — Vendor monitoring frequency (default: annually)

Reviewed framework crosswalks (3)

  • equivalent-to → requirement--nist-sp-800-53-r5-sa-9#c reviewed (maps sa_09_odp_02←assurance_evidence)
  • intersects-with → requirement--soc2-tsc-2017-cc4-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc9-2 reviewed
OGRL-VM-01 Vulnerability Scanning and SLA-Driven Remediation vm detective weekly 6 crosswalks
control--ogrl-vm-01 origin: standard 1 test(s) View YAML in ogrl-library ↗

Control statement

Scan in-scope infrastructure, container images, and application dependencies for vulnerabilities {{ scan_cadence }}, remediate confirmed findings within {{ remediation_sla }}, and share advisories with {{ advisory_audience }}.

Objective

Identify and remediate exploitable software flaws and misconfigurations before adversaries leverage them.

Implementation guidance

Combine authenticated infrastructure scanning with CI/CD dependency/container scanning and track open vulnerabilities in an issue tracker with explicit SLA due dates.

Parameters (3)

  • {{ advisory_audience }} — Internal advisory recipients (default: engineering service owners and platform security leads)
  • {{ remediation_sla }} — Vulnerability remediation SLA (default: 15 days for critical and 30 days for high severity findings)
  • {{ scan_cadence }} — Vulnerability scanning frequency (default: at least weekly and on every release)

Library tests (1)

  • automated · weekly · required — Verify Vulnerability Scan Cadence and SLA Compliance: Confirm vulnerability scans completed within the configured cadence and no confirmed critical or high findings remain open past their remediation SLA.

Reviewed framework crosswalks (6)

  • equivalent-to → requirement--nist-sp-800-171-r3-03-11-02 reviewed (maps a_03_11_02_odp_01←scan_cadence, a_03_11_02_odp_03←remediation_sla)
  • equivalent-to → requirement--nist-sp-800-53-r5-ra-5#a reviewed (maps ra_5_prm_1←scan_cadence)
  • equivalent-to → requirement--nist-sp-800-53-r5-ra-5#d reviewed (maps ra_05_odp_03←remediation_sla)
  • equivalent-to → requirement--nist-sp-800-53-r5-ra-5#e reviewed (maps ra_05_odp_04←advisory_audience)
  • intersects-with → requirement--soc2-tsc-2017-cc3-2 reviewed
  • equivalent-to → requirement--soc2-tsc-2017-cc7-1 reviewed
OGRL-VM-02 Flaw Remediation and Patching vm corrective continuous 6 crosswalks
control--ogrl-vm-02 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Install security-relevant updates for operating systems, container base images, language runtimes, and third-party dependencies within {{ patch_sla }} of vendor release, test each update in a non-production environment before production deployment, and deploy updates through the standard change management process.

Objective

Close known software flaws quickly without destabilizing production.

Implementation guidance

Automate update pull requests (for example Dependabot or Renovate), rebuild images on base-image releases, and enable managed-service auto-patching with maintenance windows. Track patch age as a metric against the SLA. Vulnerability identification and scanning is covered by OGRL-VM-01.

Parameters (1)

  • {{ patch_sla }} — Security update installation SLA (default: 14 days for critical, 30 days for high, and 90 days for other security updates)

Reviewed framework crosswalks (6)

  • subset-of → requirement--nist-sp-800-53-r5-si-2#a reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-si-2#b reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-si-2#c reviewed (maps si_02_odp←patch_sla)
  • equivalent-to → requirement--nist-sp-800-53-r5-si-2#d reviewed
  • subset-of → requirement--soc2-tsc-2017-cc7-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc8-1 reviewed
OGRL-VM-03 Malware Protection vm detective continuous 5 crosswalks
control--ogrl-vm-03 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Deploy centrally managed anti-malware or endpoint detection and response on {{ malware_protected_assets }}, keep engines and signatures automatically updated, scan files in real time on download, open, or execution and perform full scans {{ malware_scan_frequency }}, automatically {{ malware_response_action }} detected malicious code and alert {{ malware_alert_recipients }}, and verify agent coverage {{ malware_coverage_review_frequency }}.

Objective

Detect and contain malicious code on systems that can execute it.

Implementation guidance

Use MDM to deploy and lock the EDR agent on laptops, and runtime protection or EDR on general-purpose production hosts. Immutable containers rely on image scanning and least functionality (OGRL-CM-08) rather than agents. Scan customer-uploaded files before processing where the product accepts uploads. Compare the EDR agent list with the device inventory monthly.

Parameters (5)

  • {{ malware_alert_recipients }} — Malware detection alert recipients (default: the security on-call team)
  • {{ malware_coverage_review_frequency }} — Agent coverage verification frequency (default: monthly)
  • {{ malware_protected_assets }} — Assets requiring malware protection (default: workforce endpoints and production hosts running general-purpose operating systems )
  • {{ malware_response_action }} — Automatic response to detections (default: block and quarantine)
  • {{ malware_scan_frequency }} — Full malware scan frequency (default: weekly)

Reviewed framework crosswalks (5)

  • intersects-with → requirement--nist-sp-800-53-r5-si-3#a reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-si-3#b reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-si-3#c.1 reviewed (maps si_03_odp_02←malware_scan_frequency)
  • equivalent-to → requirement--nist-sp-800-53-r5-si-3#c.2 reviewed (maps si_03_odp_04←malware_response_action, si_03_odp_06←malware_alert_recipients)
  • subset-of → requirement--soc2-tsc-2017-cc6-8 reviewed
OGRL-VM-04 Security Alerts and Threat Intelligence vm detective continuous 4 crosswalks
control--ogrl-vm-04 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Subscribe to security advisories and threat intelligence from {{ advisory_sources }}, triage each advisory affecting in-scope technologies within {{ advisory_triage_sla }}, disseminate actionable advisories to {{ advisory_recipients }}, and track required actions to completion in the issue tracker.

Objective

Learn about relevant new threats and vulnerabilities promptly and ensure they result in action.

Implementation guidance

Route vendor security bulletins, the CISA Known Exploited Vulnerabilities feed, and GitHub security advisories into a shared channel or ticket queue owned by security. Record a triage decision on each relevant advisory. Remediation timelines follow OGRL-VM-01 and OGRL-VM-02.

Parameters (3)

  • {{ advisory_recipients }} — Advisory dissemination recipients (default: affected service owners and the engineering on-call channel)
  • {{ advisory_sources }} — Advisory and threat intelligence sources (default: vendors of in-scope software and cloud services, CISA (including the Known Exploited Vulnerabilities catalog), and GitHub security advisories )
  • {{ advisory_triage_sla }} — Advisory triage SLA (default: 2 business days)

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-53-r5-si-5#a reviewed (maps si_05_odp_01←advisory_sources)
  • equivalent-to → requirement--nist-sp-800-53-r5-si-5#c reviewed
  • intersects-with → requirement--nist-sp-800-53-r5-si-5#d reviewed
  • subset-of → requirement--soc2-tsc-2017-cc7-1 reviewed
OGRL-VM-05 Penetration Testing vm detective annual 3 crosswalks
control--ogrl-vm-05 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Engage {{ pentest_provider }} to perform penetration testing of {{ pentest_scope }} {{ pentest_frequency }} and after significant changes to the external attack surface, remediate findings within the organization's vulnerability remediation SLAs, and retest or otherwise validate fixes for critical and high findings.

Objective

Find exploitable weaknesses that automated scanning misses and confirm they are fixed.

Implementation guidance

Define rules of engagement and scope in a statement of work, include authenticated testing of multi-tenant isolation, and import findings into the vulnerability tracker. Keep the executive summary and retest letter as evidence; many customers will request them.

Parameters (3)

  • {{ pentest_frequency }} — Penetration test frequency (default: annually)
  • {{ pentest_provider }} — Penetration test provider (default: a qualified independent third party)
  • {{ pentest_scope }} — Penetration test scope (default: the production application, public APIs, and external-facing cloud infrastructure )

Reviewed framework crosswalks (3)

  • superset-of → requirement--nist-sp-800-53-r5-ca-8 reviewed (maps ca_08_odp_01←pentest_frequency, ca_08_odp_02←pentest_scope)
  • intersects-with → requirement--soc2-tsc-2017-cc4-1 reviewed
  • subset-of → requirement--soc2-tsc-2017-cc7-1 reviewed
OGRL-VM-06 Endpoint and Mobile Device Access Requirements vm preventive continuous 4 crosswalks
control--ogrl-vm-06 origin: standard 0 test(s) View YAML in ogrl-library ↗

Control statement

Permit access to organizational systems and data only from laptops and mobile devices enrolled in {{ device_management_platform }} that meet {{ device_security_requirements }}, enforce compliance with device-posture checks at sign-on, and block access from non-compliant devices and revoke access and remotely wipe company data on lost or stolen devices within {{ device_revocation_sla }} of report.

Objective

Ensure company data is only accessed from devices that can protect it, including outside the office.

Implementation guidance

Combine MDM (for example Jamf, Intune, or Kandji) with identity-provider device trust or conditional access so only compliant devices receive SSO sessions. Use app protection policies or work profiles for personal mobile devices. Evidence is the device compliance policy, the IdP conditional-access rule, and a compliance report.

Parameters (3)

  • {{ device_management_platform }} — Device management platform (default: the organization's mobile device management (MDM) platform)
  • {{ device_revocation_sla }} — Lost device revocation SLA (default: 24 hours)
  • {{ device_security_requirements }} — Device security requirements (default: full-disk encryption, screen lock after 15 minutes or less, a supported OS with automatic updates, and remote-wipe capability )

Reviewed framework crosswalks (4)

  • equivalent-to → requirement--nist-sp-800-53-r5-ac-19#a reviewed
  • equivalent-to → requirement--nist-sp-800-53-r5-ac-19#b reviewed
  • subset-of → requirement--soc2-tsc-2017-cc6-1 reviewed
  • intersects-with → requirement--soc2-tsc-2017-cc6-7 reviewed

Requirement Explorer

Loading 1,395 requirements…