Skip to content
AmazingaUhlelo lokuhambisanaUkuhambisana
Uhlelo lokuhambisana

Conformance programme: conformance

How an implementer in conformance programme demonstrates conformance: a self-assessment against the rules, clauses evaluated from evidence, attestations and a generated report. Each result names its evaluator and the time of evaluation, and each artefact is identified by a UNI (Unique Nexus Identifier).

Uhlelo lokuhambisana
What this area is built from: the Nexus Standards it applies (marked), the open standards it names and the data and feeds it reads, then the areas it couples with.Source: the Nexus Standards registry: the area record.
  • Nexus Standards: NS-11, NS-14.
  • Open standards: Open Security Controls Assessment Language (OSCAL); in-toto attestation framework; Verifiable Credentials Data Model 2.0; Supply-chain Levels for Software Artifacts (SLSA) 1.1; OpenStand principles (RFC 6852).
  • Data and feeds: GLEIF Golden Copy (LEI Level 1 and Level 2 data); ROR data dump.
  • Couples with: Verification services; Conformance and crosswalk to external; the Global Centre for Risk and Innovation (GCRI Canada) evidence pathway; Institutional adoption pathway.
01Ukubuka konke

Summary

  1. 01Self-assessmentagainst the rules
  2. 02Clause setNS-10
  3. 03Evidencereferenced, not embedded
  4. 04AttestationNS-11, named evaluator
  5. 05Reportgenerated from results
Nexus Standards
2
NS-11, NS-14
Open standards
5
named, never copied
Data and feeds
2
listed for reference
Couplings
4
with other areas
02Coverage

Standards listed in the readiness pathways tier

The programme areas of this tier against the standards they list in the registry; the row for this area sets the initial scope of a self-assessment.

Coverage matrix · standards across, programme areas downNexus Standards registry
Listed, standard proposedListed, standard in progressNot listed
16 of 36 programme and standard pairs are listed, across 4 programmes and 9 standards. Source: Nexus Standards programme register and standards index.

Coverage matrixA filled cell indicates that the area lists the standard in the registry. Status terms are those of the registry.

03The baseline

Conformance to NS-0

An implementation conforms to NS-0 when it:

  • names the canonical repository and the versions of the standards it applies;
  • does not fork a registry;
  • runs the repository validator, or an equivalent, on the copies of the registries it uses;
  • records its implementation status per standard in registry/consumers.yaml truthfully; and
  • carries the honesty fields (legalState, claimCeiling, status) on every record it publishes.

Conformance to NS-0 is a statement by the implementation, verifiable under NS-11. It is not a certification by the Secretariat or by the Global Standards Council.

04Self-assessment

Initial self-assessment for conformance programme

The first rules of each applicable standard. A self-assessment is a statement by the implementer, verifiable under NS-11.

RuleRequirementIzinga
NS11-R1A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest.NS-11
NS11-R2Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary.NS-11
NS11-R3Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12).NS-11
NS14-R1The text of an external standard shall not be reproduced; it shall be cited by identifier, clause number and URL.NS-14
NS14-R2Relation claims shall come from the register and from clause sets, not from prose.NS-14
NS14-R3"Compliant" and "certified" shall appear only as quotations of an authority decision cited by reference.NS-14
05NS-11 · Attestations

Attestations

One attestation is recorded per clause, per subject, per evaluation (AT category, append-only). Results: PASS; FAIL; INDETERMINATE (evidence missing or unresolvable); NOT_APPLICABLE (the subject was outside the clause’s selectors at that instant); REFUSED (the evaluator lacked a mandate or the evidence was not accessible; the refusal is itself recorded). An attestation carries a canonical digest and, optionally, a signature; certifiesTruth is always false. A later attestation supersedes an earlier one for the same clause and subject, and the history is kept.

Crosswalks: an attestation can be exported as a W3C Verifiable Credential under the Verifiable Credentials Data Model 2.0 (subject: the contextual UNI; issuer: the evaluator; evidence: the refs), as an in-toto attestation (for software subjects) or as a PROV-O activity (NS-3b). The Nexus attestation remains the key and the record of truth.

06NS-11 · Monitoring

Ukuqapha

Monitoring is continuous evaluation together with observation records. For each bound policy and context, the monitoring service records (a) the latest attestation per clause, (b) coverage (which clauses have no current attestation, and why), (c) drift (a change in a subject’s records that invalidates an attestation) and (d) the availability of evaluators and evidence sources. Monitoring records are observations with record UNIs. Dashboards and panels are projections of them and show the timestamp and the evaluator for every value; no verdict is stored.

07NS-11 · Reporting

Reporting

A conformance report for a context is generated, not written: policy by policy and clause by clause, with attestation UNIs, evidence refs, conformance levels (NS-10 section 3) and the honesty fields. Reports are catalogued artefacts (RP) and may be published (NS-8) only when their legalState allows. A report does not say "certified" or "compliant" except when it quotes an authority decision by reference.

08NS-14 · claims

Display of conformance statements

A context (NS-9) or artefact claims a relation to an external standard only through a clause set (NS-10) that cites that standard and is evaluated (NS-11). The claim is displayed as "implements clauses derived from <standard> (n of m with a current PASS)", with attestation UNIs. It is never displayed as "compliant with" or "certified to" unless a decision of the body entitled to say so is referenced. Where a body operates its own certification, conformance under the Nexus Standards is explicitly not that certification.

09Imibuzo

Questions and answers.

How does a conformance report in conformance programme relate to the decisions of other bodies?
A conformance report states clause results and their evidence. Where a decision of an authority or another body is relevant, the report cites it by reference.
What happens when evidence is missing?
The attestation is recorded as indeterminate rather than as a pass. Missing evidence, rights state or verification results in a reasoned refusal (NS0-P12).
Amazinga

Shape the standards for conformance programme.

Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.

Isimo nokusetshenziswa. Ama-Nexus Standards angamazinga ahlongozwayo athuthukiswe ngenqubo evulekile ngaphansi kwe-NS-13 futhi ashicilelwe ukuze asetshenziswe ngokuzithandela; akusona isitifiketi, ukugunyazwa noma imvume yomlawuli, futhi ukwamukela kuhlala kuyisinqumo se-Global Standards Council futhi, ezweni ngalinye, se-National Standards Council yalo. I-UNI (Unique Nexus Identifier) ihlonza into; ayiyiqinisekisi. Amagama ezinhlaka zamazinga namazinga azo angawabaphathi bawo futhi asetshenziswa kuphela ukuhlonza amadokhumenti; awukho umbhalo wezinga langaphandle okhiqizwe kabusha lapha. I-Nexus Standards ayihlangene, ayesekwa futhi ayiqinisekiswanga yinoma iyiphi inhlangano yamazinga eshiwo lapha.

Amalayisense: i-CC BY 4.0 embhalweni wezindinganiso, amarejista, amaskimu nedatha; i-Apache-2.0 kukhodi yereferensi. Izindinganiso zangaphandle zicashunwa ngegama, inombolo nesixhumanisi ngaphansi kwamalayisense azo. Idatha, amalabhulali namafonti abantu besithathu agcina amalayisense awo: bheka Izaziso zabantu besithathu.