IF Commons GitHub

NIST SP 800 catalog package

0002Active

0002-sp800-package · owner if · domain commons

Requirements

FR-001checkpassing

The package MUST hold four grc.framework documents: nist-800-53 (version 5.2.0) and nist-800-171 (version 3), whose controls are the requirements that the source does not withdraw (1014 and 97), each with its identifier as the publication prints it (AC-2, AC-2(1), 03.01.01), its title, its statement as NIST wrote it with the inserted parameters written out in brackets, and its family; and nist-800-53a and nist-800-171a, whose controls are the assessment objectives that have no objective below them (2781 and 422), each of the requirement named as its family.

Enforced (check): .github: cd commons/catalog-nist-sp800 && bun run verify — suite/sp800.test.ts

Proved by: catalog-nist-sp800/suite/sp800.test.ts

Written in: catalog-nist-sp800/src/logical/convert.ts

Tests: passed: suite/sp800.test.ts the real package loads through the catalog loader with the counts of the publications, and; passed: suite/sp800.test.ts the conversion keeps the controls and enhancements that are not withdrawn, writes out the

Cited by: Catalog Nist Sp800, logical/convert

FR-002checkpassing

The manifest MUST record the repository and the commit the sources were read at, the address and the SHA-256 of each source file, the edition, the licence wording and that the content may be redistributed; the package MUST load through readCatalogPackage of grc with no problem.

Enforced (check): .github: cd commons/catalog-nist-sp800 && bun run verify — suite/sp800.test.ts

Proved by: catalog-nist-sp800/suite/sp800.test.ts

Written in: catalog-nist-sp800/src/governance/source.ts, catalog-nist-sp800/src/physical/package.ts

Tests: passed: suite/sp800.test.ts the real package loads through the catalog loader with the counts of the publications, and; passed: suite/sp800.test.ts the manifest records the repository, the commit, the digest of each source, the licence an

FR-003checkpassing

The package MUST be made by tools/generate.ts from the sources and never edited by hand: the tool MUST refuse a source file whose SHA-256 is not the one pinned, and --check MUST find any file of the package that differs from what the sources give.

Enforced (check): .github: cd commons/catalog-nist-sp800 && bun run verify — suite/sp800.test.ts

Proved by: catalog-nist-sp800/suite/sp800.test.ts

Written in: catalog-nist-sp800/src/governance/source.ts, catalog-nist-sp800/src/physical/package.ts, catalog-nist-sp800/tools/generate.ts

Tests: passed: suite/sp800.test.ts the manifest records the repository, the commit, the digest of each source, the licence an; passed: suite/sp800.test.ts the generator refuses a source that is not the pinned one, and the files on disk are those

FR-004checkpassing

The conversion MUST be a pure function of the catalogs: the same catalogs give the same documents, byte for byte, with no clock and no network.

Enforced (check): .github: cd commons/catalog-nist-sp800 && bun run verify — suite/sp800.test.ts

Proved by: catalog-nist-sp800/suite/sp800.test.ts

Written in: catalog-nist-sp800/src/logical/convert.ts, catalog-nist-sp800/src/physical/package.ts

Tests: passed: suite/sp800.test.ts the conversion keeps the controls and enhancements that are not withdrawn, writes out the ; passed: suite/sp800.test.ts the same catalogs give the same files, byte for byte

Cited by: Catalog Nist Sp800, logical/convert

Acceptance scenarios

  1. Given the pinned sources, When the package is made, Then it has 1014, 2781, 97 and 422 controls in its four frameworks and every objective names a requirement that is there, per FR-001.
  2. Given a source file that is not the pinned one, When the generator runs, Then it refuses, per FR-003.

Out of scope

  • SP 800-171 Rev 2, which CMMC Level 2 assesses today: NIST publishes no OSCAL content for it; it is read from the printed publications (0003-sp800-171-r2).
  • Baselines and profiles (FedRAMP's, NIST's): later packages, with crosswalks.
  • The guidance text and the assessment methods and objects of the publications.

Edge cases

  • A control that the source withdraws is not a control of the package, per FR-001.
  • A parameter that has only choices is written as a selection, per FR-001.

Assumptions

  • NIST's OSCAL content is faithful to the printed publications; the package carries it as published at the commit.

Open questions

  • None.

Key entities

  • Source, Package, Objective.

Success criteria

SC-001success criterion

The controls and assessment objectives of the two publications are available as framework data from a folder of JSON.

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

Catalog Nist Sp800, logical/convert, NIST SP 800-171 Revision 2 in the SP 800 package

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