Join

Bring a validator, a catalogue or an objection

A notation for compliance data is worth what the second and the third party make of it. JASCON has one maintainer, a released specification and no known user outside its repository. The work below is the work that only someone else can do.

01 What is needed

Six contributions, in order of weight

The standing invitationopen

A validator by someone who did not write the specification

Take the specification, appendices A to C and the conformance corpus, and build a validator in a language of your choice without reading the two existing ones. Every place where the text did not determine your implementation is a defect of the text. The vectors are the referee, and the result is recorded whichever way it goes.

Start: jascon/conformance/, handbook chapter 12.

Authorities

A catalogue converted by its own publisher

Eleven conversions exist, all by the project. A publisher knows what its props were meant to say. Ten requirements re-encoded by the people who wrote them test the kernel harder than a thousand converted by a script.

Start: the Import page, or chapter 14.

Review

Objections with counts

The handbook's appendix F answers 33 objections and lists the ones that changed the text. One review is due now: the 2.0.0 release candidate with its two new types, Risk and Check. Appendix F.10 says why JASCON does not extend Gemara, CycloneDX, XCCDF, CISO Assistant or OSCAL; a reader from one of those communities is the right person to say where that answer is wrong.

Start: CP-RISK-1, CP-CHECK-1 and the state of Check.

Measurement

Value arrival on the other ten corpora

Coverage is measured by source path. Where each value went is traced on one corpus, with a ledger that gives every source value a destination, a named rule or a stated reason. Whoever holds the source files of the others can build the ledger for one of them and report what is lost.

Start: backlog item 41, oscal_conv_lib.Ledger; convert_ifa.py shows its use.

Practice

A real ISMS in the notation

A risk register, a Statement of Applicability and one audit cycle of a real organisation, written as Risks, a Tailoring, Implementations and Findings. The Risk type was derived from three standards; it has not met an auditor.

Start: the Risk page of the app; anonymise and report what did not fit.

Code

Exports and bridges

Exports to the OSCAL mapping, profile and SSP models are missing. An in-toto predicate for the attestation would reach existing verifiers. A runner that executes the collectors of the Check type does not exist.

Start: jascon/scripts/export_oscal.py, PRIOR-ART.md.

02 How a change gets in

Evidence in, corpus first, implementations follow

The change process is built against one sentence from an old issue tracker: nobody can say why this rule exists.

01

A proposal leads with counts

"Three authorities encode this independently" is an argument. "It would be elegant" is none. An item enters the backlog with its evidence and leaves through an entry in the decision register, where the rejected alternatives stay on the record.

02

Every rule carries its reason

A rule has a machine id, a rationale and a failure message, and the rationale prints when the rule fails. A rule that cannot name the counted failure it prevents is a candidate for deletion.

03

A gap is closed by a version

Primitives, operations and code systems are closed sets with versions. A genuine gap becomes a change proposal with new conformance vectors and a decision on the version number. Both validators have to pass before a release.

The process in full: handbook, chapter 15. All 24 decisions with their scores and amendments: the decision register.

03 What to expect

A small project that keeps its record public

  • Findings are adjudicated on the record. A confirmed one is fixed and gets a conformance vector. A refuted one is written down with the reason, so that it stays refuted.
  • Corrections carry the weight of the claim they correct. The first published scan undercounted the German catalogue by 347 nested controls; the correction went out with the same prominence.
  • The licence is Apache 2.0 for specification, schema, vectors, validators and app. Converted catalogues stay under their publishers' terms.
  • Response times are those of one person working in personal capacity, without an organisation behind the project.

Open an issue

For a defect, an objection, a question or a catalogue you would like to see converted. State what you counted and where.

Issues on GitHub

Send a pull request

For a vector, a converter, a fix to a validator or to the handbook. A change to a rule comes with the vectors that fail without it.

Pull requests on GitHub

Use it and say so

A bundle published by a second party is the strongest evidence this project can get. If you publish one, an issue with the link is enough.

Get started