IF Commons GitHub

GRC engineering

0007Draft

0007-grc · owner if · domain commons

Catalogs, controls and verdicts (kernel)

FR-001reviewno test run

GRC engineering MUST take catalogs and mappings from the library grc (@intellectual-frontiers/grc, grc FR-001), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-001

FR-002reviewno test run

GRC engineering MUST take controls from the library grc (@intellectual-frontiers/grc, grc FR-002), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-002

FR-003reviewno test run

GRC engineering MUST take verdicts and severities from the library grc (@intellectual-frontiers/grc, grc FR-003), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-003

FR-004reviewno test run

GRC engineering MUST take findings from the library grc (@intellectual-frontiers/grc, grc FR-004), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-004

FR-005reviewno test run

GRC engineering MUST take waivers from the library grc (@intellectual-frontiers/grc, grc FR-005), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-005

Evidence (kernel)

FR-006reviewno test run

GRC engineering MUST take the canonical form and the digests of evidence from the library grc (@intellectual-frontiers/grc, grc FR-006), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-006

FR-007reviewno test run

GRC engineering MUST take the evidence ledger from the library grc (@intellectual-frontiers/grc, grc FR-007), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-007

Cited by: pure/chain, Quality evidence

FR-008reviewno test run

GRC engineering MUST take manifests from the library grc (@intellectual-frontiers/grc, grc FR-008), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-008

FR-009reviewno test run

GRC engineering MUST take evidence bundles from the library grc (@intellectual-frontiers/grc, grc FR-009), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-009

Assessment (kernel)

FR-010reviewno test run

GRC engineering MUST take coverage from the library grc (@intellectual-frontiers/grc, grc FR-010), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-010

FR-011reviewno test run

GRC engineering MUST take freshness from the library grc (@intellectual-frontiers/grc, grc FR-011), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-011

Cited by: ifqs/ifqs, Quality, pure/freshness, Quality evidence

FR-012reviewno test run

GRC engineering MUST take drift from the library grc (@intellectual-frontiers/grc, grc FR-012), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-012

FR-013reviewno test run

GRC engineering MUST take the change-impact gate from the library grc (@intellectual-frontiers/grc, grc FR-013), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-013

FR-014reviewno test run

GRC engineering MUST take the risk register from the library grc (@intellectual-frontiers/grc, grc FR-014), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-014

FR-015reviewno test run

GRC engineering MUST take the requirement trace from the library grc (@intellectual-frontiers/grc, grc FR-015), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-015

Formats (kernel)

FR-016reviewno test run

GRC engineering MUST take findings as OCSF from the library grc (@intellectual-frontiers/grc, grc FR-016), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-016

FR-017reviewpassing

GRC engineering MUST take assessments as OSCAL from the library grc (@intellectual-frontiers/grc, grc FR-017), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-017

Proved by: crypto/suite/uuid.test.ts

Tests: passed: suite/uuid.test.ts uuidV5 gives RFC 9562's example and the well-known vectors of each standard namespace; passed: suite/uuid.test.ts UUIDs read any case and a urn:uuid: prefix, refuse what is not one, and round-trip through; passed: suite/uuid.test.ts every version 5 UUID has version 5 and the RFC variant, and is the same for the same names; passed: suite/uuid.test.ts names made of parts are kept apart: [a/b] and [a, b] give different UUIDs

Cited by: uuid, Quality evidence

FR-018reviewpassing

GRC engineering MUST take attestations from the library grc (@intellectual-frontiers/grc, grc FR-018), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-018

Proved by: crypto/suite/uuid.test.ts

Tests: passed: suite/uuid.test.ts uuidV5 gives RFC 9562's example and the well-known vectors of each standard namespace

Cited by: uuid

The host (runtime)

FR-019reviewno test run

GRC engineering MUST take the run of a pack as signals from the library grc (@intellectual-frontiers/grc, grc FR-019), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-019

FR-020reviewno test run

GRC engineering MUST take signing and verifying from the library grc (@intellectual-frontiers/grc, grc FR-020), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-020

FR-021reviewno test run

The runtime MUST take Git, read by running it from the library system (@intellectual-frontiers/system, system FR-014), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library system: 0001-system FR-014

Cited by: git, System

FR-022reviewno test run

GRC engineering MUST take the loaders of settings from the library grc (@intellectual-frontiers/grc, grc FR-021), where it is specified and proved (0032-libraries-by-concern FR-010), and MUST NOT specify it here.

Enforced (review): 0032-libraries-by-concern FR-010 — kept by the library grc: 0001-grc-engineering FR-021

Out of scope

  • The content of catalogs (the Secure Controls Framework, NIST SP 800-53, FedRAMP's key security indicators): its licences are each harness's to check, so it stays in the harness that uses it.
  • Connectors to clouds and services, stolos's SQLite estate, erga's spec-kit grammar and ontology terms.
  • Sigstore and transparency logs.

Edge cases

  • catalog.control("XX-99") where the catalog has no such control: does not compile, per FR-001.
  • A control whose check throws for one host of ten: error for that host, the nine others judged, per FR-002.
  • fail joined with pass: fail; pass joined with not-applicable: pass, per FR-003.
  • A waiver granted on 1 March that expired on 31 March, at 1 April: does not apply, per FR-005.
  • A waiver for a control whose check gave error: does not apply, per FR-005.
  • {"b":1,"a":2.0} and {"a":2,"b":1}: one digest, per FR-006.
  • A ledger whose third entry was edited: verification names entry 3, per FR-007.
  • A ledger whose last entry was removed: not detectable from the ledger alone, so the digest of its last entry is what a signature covers, per FR-007 and FR-008.
  • A bundle with a file added after its manifest was written: refused, naming the file, per FR-009.
  • Evidence of 29 days for a cadence of P30D: due, per FR-011.
  • A change touching infra/** declared for a control whose newest verdict is fail: blocked, naming the control, per FR-013.
  • Likelihood high and impact very-high: very-high, as Table I-2 gives it; the middle level is moderate, per FR-014.
  • The same findings written twice to OSCAL: byte for byte the same document, per FR-017.
  • git not installed: an Err, never a thrown error, per FR-021.

Assumptions

  • OCSF 1.9.0, OSCAL 1.2.3 and CycloneDX 1.6 are the versions the harnesses write today (stolos writes these OCSF classes and OSCAL documents already). From OSCAL 1.1.2 to 1.2.3 the members of the four documents written did not change; 1.2 widened enumerations (component types, the discovery observation type, CVSS v4), made an SSP's users optional and added the mapping model, which is not written.
  • A role is enough to say who approved a waiver or owns a risk in this public repository; a harness that must name people adds them in its own records.

Open questions

OQ-1open question

Whether to add the OSCAL profile and catalog models when a harness resolves profiles itself.

Key entities

  • Catalog - a framework's controls, as a typed constant.
  • Control - a check of one kind of subject, implementing catalog controls.
  • Verdict - a status and severity for one subject under one control.
  • Finding - a verdict with its detail, evidence and waiver.
  • Waiver - an approved, expiring acceptance of a failing verdict.
  • Ledger - the hash chain of evidence.

Success criteria

SC-001success criterion

erga and stolos keep no type of their own for a control, a verdict, a finding, a waiver or a ledger entry.

SC-002success criterion

The same findings give the same OCSF, OSCAL and CycloneDX on Bun and Node.

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

uuid, ifqs/ifqs, Quality, pure/chain, pure/freshness, git, System, Quality evidence, Intellectual Frontiers Quality System, Subject profiles

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