IF Commons GitHub

GRC governance

0002Active

0002-grc-governance · owner if · domain grc

Frameworks, catalogs and crosswalks

FR-001checkpassing

A framework MUST be a document of kind grc.framework with a slug id, a version, a title and controls, each with an id, a title and a statement; a control MUST be addressed by the stable URN urn:grc:<framework>:<version>:<control>, which controlUrn writes and parseControlUrn reads back, and a duplicate control id in a framework MUST be a problem.

Enforced (check): .github: cd commons/grc && bun run verify — suite/governance.test.ts

Proved by: grc/suite/governance.test.ts

Written in: grc/src/governance/kinds.ts, grc/src/governance/rules.ts

Tests: passed: suite/governance.test.ts a control has a stable URN that is written and read back, and a duplicate control is a pro

FR-002checkpassing

A crosswalk MUST be a document of kind grc.crosswalk whose mappings each join two control URNs by a Set Theory Relationship Mapping (NIST IR 8477: equal, subset-of, superset-of, intersects-with, no-relationship) with a strength from 1 to 10; mappedControls MUST give the controls reached from a control through crosswalks, in both directions, with the relationship read the other way for the reverse (subset-of and superset-of swap).

Enforced (check): .github: cd commons/grc && bun run verify — suite/governance.test.ts

Proved by: grc/suite/governance.test.ts

Written in: grc/src/governance/rules.ts

Tests: passed: suite/governance.test.ts a crosswalk maps controls in both directions and the relationship reads the other way for

Policy, check and requirement

FR-003checkpassing

A policy MUST be a document of kind grc.policy with its scope (platforms and tags), severity (info | low | medium | high | critical), rationale, the control URNs it maps to, the checks that show it, an owner and a review (an ISO 8601 cadence and the date it was last reviewed); reviewDue MUST say when its review falls due.

Enforced (check): .github: cd commons/grc && bun run verify — suite/governance.test.ts

Proved by: grc/suite/governance.test.ts

Written in: grc/src/governance/kinds.ts, grc/src/governance/rules.ts

Tests: passed: suite/governance.test.ts a policy carries scope, severity, mappings, owner and review, and says when its review fal

FR-004checkpassing

A check MUST be a document of kind grc.check that says what is asked (ask), what is expected (an expectation: empty, non-empty, equals, count with bounds, or every row matching a field comparison), where it applies (platforms), how fresh its result must be (an ISO 8601 duration), the control URNs it shows, and a runner as a kind id and an input of JSON data; a check MUST NOT carry code, and an input that is not JSON data MUST be refused by its decoder.

Enforced (check): .github: cd commons/grc && bun run verify — suite/governance.test.ts

Proved by: grc/suite/governance.test.ts

Written in: grc/src/governance/kinds.ts

Tests: passed: suite/governance.test.ts a check names a runner kind and an input of data, and refuses an input that is code

FR-005checkpassing

A requirement MUST be a document of kind grc.requirement with a statement, a level (MUST | SHOULD | MAY), a verification and a validation. The verification MUST be exactly a row of the enforcement register (mechanism: check | gate | review | none; by; note), and fromEnforcementRegister and toEnforcementRegister MUST read and write the register's TSV, so that Mizan's rows and requirements are one kind of data. The validation says that the requirement is the right one: its method (review | scenario | stakeholder | measure), who validated it and when.

Enforced (check): .github: cd commons/grc && bun run verify — suite/governance.test.ts

Proved by: grc/suite/governance.test.ts

Written in: grc/src/governance/kinds.ts, grc/src/governance/rules.ts

Tests: passed: suite/governance.test.ts a requirement's verification is a row of the enforcement register, read and written as its

FR-006checkpassing

An evidence policy MUST be a document of kind grc.evidence-policy saying what counts as evidence (evidence kinds, the longest age, the producers accepted), how long it is retained (an ISO 8601 duration), who may attest (roles), and the custody of the key an attestation needs (none | file | managed | hardware).

Enforced (check): .github: cd commons/grc && bun run verify — suite/governance.test.ts

Proved by: grc/suite/governance.test.ts

Written in: grc/src/governance/kinds.ts

Tests: passed: suite/governance.test.ts an evidence policy says what counts, retention, who may attest and the custody

Exceptions and accepted risk

FR-007checkpassing

An exception MUST be a document of kind grc.exception naming what it excuses (a control URN, a check or a policy), the subjects it covers (an id or a glob), the reason, who approved it, when it was granted and when it expires, and MAY carry an accepted risk (its owner, its level and its review date); one with no expiry, or an expiry not after its grant, MUST be refused, and exceptionApplies MUST be false at and after the expiry.

Enforced (check): .github: cd commons/grc && bun run verify — suite/governance.test.ts

Proved by: grc/suite/governance.test.ts

Written in: grc/src/governance/glob.ts, grc/src/governance/kinds.ts, grc/src/governance/rules.ts

Tests: passed: suite/governance.test.ts an exception needs an expiry after its grant and does not apply at or after it

Validation of a set

FR-008checkpassing

governanceProblems MUST find, as data, each control URN that no loaded framework holds, a check a policy names that does not exist, a policy that maps to no control, an id used twice, an invalid duration, a runner kind that is not a stable id, and an exception that excuses nothing that exists.

Enforced (check): .github: cd commons/grc && bun run verify — suite/governance.test.ts

Proved by: grc/suite/governance.test.ts

Written in: grc/src/governance/rules.ts

Tests: passed: suite/governance.test.ts the problems of a set are found as data

FR-009checkpassing

Durations MUST be ISO 8601 (P1D, PT1H, P30D, P1Y, P1W), parsed by parseDuration to an exact length in milliseconds with a year as 365 days and a month as 30, and addDuration MUST add them to an instant.

Enforced (check): .github: cd commons/grc && bun run verify — suite/governance.test.ts

Proved by: grc/suite/governance.test.ts

Written in: grc/src/governance/time.ts

Tests: passed: suite/governance.test.ts durations are exact: a year is 365 days, a month 30, and they add to an instant

Scenarios

  • Given the URN urn:grc:nist-800-53:5.2.0:AC-2(1), When it is parsed, Then the framework is nist-800-53, the version 5.2.0 and the control AC-2(1), per FR-001.
  • Given a crosswalk that says A is a subset-of B, When the controls mapped from B are asked, Then A is given as superset-of, per FR-002.
  • Given an exception granted on 1 March that expires on 31 March, When it is asked on 1 April, Then it does not apply, per FR-007.
  • Given a check whose input holds a function, When it is read, Then the decoder refuses it, per FR-004.

Out of scope

Edge cases

  • A framework with no controls: valid, with none judged, per FR-001.
  • A URN with a colon in the control id: refused, per FR-001.
  • P1M against P30D: one month is 30 days, per FR-009.

Assumptions

Open questions

OQ-1open question

Whether validation should be a register of its own beside enforcement.tsv.

Key entities

  • Framework, Control, Crosswalk, Policy, Check, Requirement, EvidencePolicy, Exception.

Success criteria

SC-001success criterion

A policy set that points at a control no framework holds is found before anything runs.

Review & acceptance checklist

  • [x] Every requirement is testable (MUST / MUST NOT), not aspirational
  • [x] No company fact is asserted here
  • [x] Every open item is marked, not silently decided

Cited by

governance/kinds, governance/mod, GRC, GRC catalog data packages, GRC groups of entities

Titles, headings, exports, tables, columns and requirements. Esc closes.