A tailored parameter retunes the check
Tighten max-auth-tries from 6 to 4 in the Tailoring, and yesterday's observation of 5 turns from satisfied to not satisfied. No line of code changes, and an implementer cannot set its own pass mark.
Checks · kernel 2.0.0, release candidate
A scanner that exits with 0 or 1 hides its threshold, ignores the tailoring and leaves nothing to re-examine. A Check publishes the facts a collector must report and the comparisons that decide. The run record carries what was observed, so anyone recomputes the verdict from the record.
01 The gap
JASCON 1.0.0 can say that a requirement was assessed and what the assessor concluded. It cannot say how a machine decides.
Every one of them arrives in a converted bundle as an audit string with shell excerpts in prose. The pass condition is a sentence such as "verify the output is", which a person has to read.
The ISM, Grundschutz++ and SP 800-53 name methods (examine, interview, test) and required documentation. FedRAMP CR26 carries key tests as prose. None of them specifies a check a program can evaluate.
Counts: CP-CHECK-1, section 2.1, from the coverage reports of the converted corpora.
02 The design
The line is drawn where tools must agree. Two conformant tools given the same Check and the same observation return the same verdict. Everything that may differ between honest tools without changing the verdict stays outside the kernel.
A shell script, an Ansible task or an API call, carried on the Check so that the check's digest covers the exact code. It prints one observation and decides nothing.
Named, typed facts such as sshd.maxauthtries: integer. A collector reports effective values, with defaults resolved. An absent key means "looked and did not find".
A flat conjunction such as at-most {param}. The expected value is a literal or a parameter of the requirement, so the Tailoring that binds the parameter sets the pass mark.
Satisfied, not satisfied, inconclusive or not applicable: a pure function of the Check, the observation and the bound parameters. The validator recomputes every recorded verdict.
Tighten max-auth-tries from 6 to 4 in the Tailoring, and yesterday's observation of 5 turns from satisfied to not satisfied. No line of code changes, and an implementer cannot set its own pass mark.
The Assessment row holds the observation itself. A second party evaluates the criteria on it and compares. A recorded outcome that differs from the computed one is a validation error.
A failing row reads sshd.ciphers matches-not ".*-cbc", observed a list that contains aes128-cbc. An exit code would have said 1.
03 Try it
The worked example of the repository: one requirement with two clauses, a Tailoring for production hosts, two Checks and two recorded daily runs of a bastion host. Change what the collector saw or what the Tailoring binds.
s1 The SSH daemon allows at most 4 authentication attempts per connection.
s2 The SSH daemon offers no cipher in CBC mode.
Computed in your browser by the app's port of check-verdict, the code that passes the 205 check vectors. No collector runs here; the observation is the one you set.
{
"id": "https://cso.example/check/LNX-SSH-1-maxauthtries",
"requirement-ref": "https://cso.example/req/LNX-SSH-1",
"statement-ids": ["s1"],
"platform": "https://cso.example/platform/linux-host",
"observes": [
{ "name": "sshd.maxauthtries", "type": "integer" }
],
"criteria": [
{ "fact": "sshd.maxauthtries", "op": "at-most",
"expected": { "param": "max-auth-tries" } }
],
"validity": { "num": 24, "unit": "hours" },
"confidence": "reviewed",
"facets": {
"https://ns.jascon.net/stdlib/facet/collector@1": {
"collectors": [
{ "id": "bash", "runtime": "bash", "privileges": "root",
"source": "#!/bin/bash\nv=$(sshd -T | awk '$1==\"maxauthtries\"{print $2}') ..." }
]
}
}
}
{
"check-ref": "https://cso.example/check/LNX-SSH-1-ciphers",
"check-digest": "sha256:b5ec275f0904a0a882d27e1434efb28e0595a74c6c0814297b2537fa49833f56",
"collector-id": "bash",
"outcome": "not-satisfied",
"time": "2026-11-03T06:00:04Z",
"observation": {
"facts": {
"sshd.ciphers": ["chacha20-poly1305@openssh.com",
"aes256-gcm@openssh.com", "aes256-ctr", "aes128-cbc"]
}
},
"evidence-record": {
"ref": "evidence/sha256/61c0ab97f7c9033b00b61a1eb09b5aa40d648114422ffa040aa779b09a9118fc",
"digest": "sha256:61c0ab97f7c9033b00b61a1eb09b5aa40d648114422ffa040aa779b09a9118fc"
}
}
{
"id": "https://cso.example/finding/bastion-01-ssh-cbc",
"assessment-ref": "https://cso.example/assessment/bastion-01-2026-11-03",
"requirement-ref": "https://cso.example/req/LNX-SSH-1",
"statement-ref": "s2",
"check-ref": "https://cso.example/check/LNX-SSH-1-ciphers",
"state": "closed",
"actions": [
{ "description": { "en": "Remove aes128-cbc from the Ciphers line of sshd_config; the next daily run verifies." },
"status": "done" }
]
}
aes128-cbc, not satisfied. The Assessment's result is the aggregate of its rows.The example assessed no real host. Each run executed the bash collector of the Check, unchanged, against a stub sshd that prints a fixed configuration, and every evidence record says so.
04 The comparators
The set is small on purpose. A check that does not fit stays manual and is counted.
one-of, and negation lives in the operator pairs.at-most never binds a parameter that tightens upward, so that tightening a parameter cannot loosen a check.| Operator | On | Holds when |
|---|---|---|
equals | one value | the value equals the expected one; decimals by value |
not-equals | one value | the value differs from the expected one; inconclusive on a missing fact |
one-of | one value | the value is in the list |
at-least at-most | integer, decimal | ordering; decimals never as floats |
present absent | any fact | the key is, or is not, in the observation |
includes-all | a list | every listed value occurs |
excludes-all | a list | no listed value occurs |
subset-of | a list | every observed value is listed |
matches matches-not | string, code | the whole value matches an I-Regexp pattern, or none does |
The handbook rejects expression languages, because two conformant tools may then return two verdicts. Python, .NET and JavaScript disagree on exactly the constructs people reach for: \d, \w, anchors, flags, lookaround. The dialect is therefore I-Regexp (RFC 9485), built by the IETF for interoperability and used by JSONPath.
^ and $ are ordinary characters.\p{..} is read from the host's database (backlog 59).05 Evidence
Evidence is a directory beside the content manifest. Every file is named by the SHA-256 of its bytes. Redaction happens before hashing, and raw output is a separate file, so a retention delete leaves the record verifiable: the validator reports the file as withheld.
binds the semantic digest of the Assessment.
holds the observation inline, so that digest covers it. It names the Check by reference and by digest: a changed check is a different check.
names the check, the collector, the subject, start, end and exit status, and carries the digest of the same observation.
stdout or an API response, each by digest, with media type, size and a redaction flag.
06 Measured fit
The comparator set was drafted first and measured afterwards, against two open check corpora: the four CIS profiles for Ubuntu 24.04 in ComplianceAsCode (510 rules) and the CIS 1.12 checks of kube-bench (103 automated, 28 manual).
| Class | Rules of 510 |
|---|---|
| Fits23 of them only if the collector resolves effective values and reports mode bits as flag sets | 481 |
| Needs arithmeticcounts, uniqueness, time against now | 12 |
| Needs a comparison between two facts | 9 |
| Needs OR across facts | 6 |
| Needs version ordering | 2 |
| Needs a regex outside I-Regexp | 0 |
The set as drafted had no not-equal. The census found it twice in the OVAL states and 85 times across all kube-bench directories, and for a number nothing else says it. It was added on 12 November as the twelfth comparator. The 29 rules that do not fit stay manual.
07 State
On 12 November 2026 the author decided the open points of the proposal. Check has been part of the release candidate since 2.0.0-rc.2 and goes live with 2.0.0. The candidate, now rc.4, is not tagged.
collector@1; CHECK-1 to CHECK-15 and the primitive check-verdict, each with a rationale that prints on failure.| Question put to the author | Decision of 12 November 2026 |
|---|---|
| The promotion rule asks that two of three census authorities encode a type. None encodes a check. | The rule gained a clause for types that catalogue authorities do not publish: a recognised standard requires the record, or it is established practice shown by two counted open implementations; the other two tests hold; it rides a major version. Risk enters under the first branch, Check under the second. |
| Run rows: kernel field or facet? | Kernel field. A verdict is computation, and facets never define computation. |
| May a Check ship without the requirement it refers to? | Yes. A check pack for a catalogue that may not be passed on validates on its own. |
| Land now, or wait for a cloud API census? | Check goes live with 2.0.0. |
| A quantifier beside "every resource"? | None. Every resource is evaluated and recorded, the share of failures is reported, and the check fails. |
A twelfth comparator not-equals? | Added. |
The proposal with its census, the alternative that was not taken (criteria in a facet, promotion later) and the record of the decisions: drafts/CP-CHECK-1.md. The normative text: specification 2.0.0-rc.4, D24.
A kernel type is paid for by every validator for ever, and a correction after the tag costs a major version. The candidate needs readers who run scanners for a living: does the fact contract hold for your platform, and which of your checks falls outside twelve comparators?