Modules

wingbox-controls: from a control to the evidence that supports it

A team that prepares for ISO/IEC 27001, ISO/IEC 42001 or SOC 2 keeps by hand the mapping from each control to the evidence that supports it, and nothing checks that the evidence a control names was in fact produced. This library holds that mapping as a file and checks it against the records.

wingbox-controls is in development. Nothing of it is released, and there is no package to install.

What it is for

  • A versioned mapping file in the team's own repository: each control with its scope, the tests it requires and the role that reviews.
  • A check that every control of the file has the evidence it names, and that its scope is inside what was analysed.
  • A matrix for each of the three regimes: which evidence a run can give, what a reviewer still needs from elsewhere, and what code evidence cannot show.

What it takes in and gives out

Takes in

  • The mapping file of the team: its own controls, their scope, the tests each requires.
  • The evidence records of the runs.

Gives out

  • In development: for each control, the evidence a run produced for it and what is missing.
  • In development: the matrix, as a table per regime and as a file a machine can read.
  • In development: a traceability export in both directions, from a requirement to its evidence and from a result back to the obligation it answers.

The rules it holds to

Requirements of the library, from its public issues.

  • A record is technical evidence for a reviewer. Whether a control conforms is the reviewer's decision.
  • A file that exists, an edge of the graph, a test name or a command that passed does not show that a control operates.
  • Conformity with a whole framework is never inferred from a count of passed checks.
  • A mapping that is a draft, of the wrong edition or unapproved supports no claim.
  • No text of a standard is copied. The mapping content for a real framework is the team's and its auditor's.
  • No language model, in the library or in its tests.

Status

What is true today. Available: in a released version. Merged, in the next release: on the main branch, not released. In development: an open issue on GitHub.

A mapping file from a control to the evidence that supports it, with a check that the evidence was producedIn development
A control matrix for ISO/IEC 27001, ISO/IEC 42001 and SOC 2: which evidence the tool can give, and where it stopsIn development
Traceability in both directions, with what is unmappedIn development
Approved inputs from a protected baseline: the assurance profile and the control mapIn development