Cyberrisques et risques numériques : normes applicables
Les 5 normes répertoriées pour le risque cyber et numérique dans le registre, chacune avec son statut, son UNI (Unique Nexus Identifier) et les règles énoncées dans son texte.
- Nexus Standards: NS-0, NS-9, NS-10, NS-11, NS-12.
- Normes ouvertes : STIX Version 2.1 ; TAXII Version 2.1 ; Common Security Advisory Framework 2.0 ; Common Vulnerability Scoring System v4.0 ; Supply-chain Levels for Software Artifacts (SLSA) 1.1 ; NIST Cybersecurity Framework 2.0 ; NIST SP 800-207 Zero Trust Architecture ; Open Security Controls Assessment Language (OSCAL).
- Data and feeds: National Vulnerability Database (CVE enrichment API); Known Exploited Vulnerabilities catalogue; OSV open source vulnerability database; MITRE ATT&CK knowledge base (STIX 2.1).
- Couplé avec : risques financiers et économiques ; infrastructures critiques et entités critiques ; intégrité de l'information et confiance ; cyberrésilience et résilience opérationnelle numérique.
- Nexus Standards
- 5
- NS-0, NS-9, NS-10
- Normes ouvertes
- 8
- nommées, jamais copiées
- Données et flux
- 4
- cité pour référence
- Couplages
- 4
- avec d'autres domaines
Constitution et principes
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000004.
| Règle | Texte |
|---|---|
NS0-P1 | Open · The standards, their registries, schemas, catalogues and reference tools are published in the canonical repository under the licences recorded in LICENSING.md. Participation in development is open to every community and stakeholder under GOVERNANCE.md. No standard depends on a proprietary artefact, product, account or mark to be applied. |
NS0-P2 | Lisible par machine d'abord · Chaque élément normatif existe sous forme de données (registre, schéma, clause) avant d'exister sous forme de prose ; la prose explique, les données régissent. Une norme sans forme lisible par machine n'est pas une Nexus Standard. |
NS0-P3 | Identified · Every artefact, record, deployment, policy and clause carries a UNI (NS-1, NS-3, NS-9). Nothing is cited by a name alone. |
NS0-P4 | Verified, not asserted · Conformance is a claim with evidence: receipts, digests, signed attestations and observations (NS-11). A claim without evidence is recorded as a claim, never as a fact, and the supported claim level of the implementation bounds every statement it makes. |
NS0-P5 | Zero trust · Authenticated is not authorised; entitled is not authorised; access is denied by default. Every verification, monitoring and enforcement path assumes no implicit trust between systems, tenants, sites or agents, and records who verified what under which mandate. |
NS0-P6 | Real-time · Standards express obligations that can be evaluated continuously against live records (observations, releases, corrections, deployments), and the standards themselves are versioned so that an implementation can state exactly which version it conforms to at any instant. |
NS0-P7 | Provenance everywhere · Every artefact records what it was derived from, who produced it, under which release and policy decision, and what corrected it (NS-3b, PROV-O profile). Corrections supersede; nothing is silently rewritten. |
NS0-P8 | Honnête · Un UNI identifie et résout ; il ne certifie jamais. legalState defaults to review-required. Readiness, approval and production status are never implied by a standard, a status, a page, a score or a badge. |
NS0-P9 | Nexus-aware · Standards address cross-domain interdependence (water, energy, food, health, biodiversity, climate and the sectors they touch) explicitly: an obligation can reference artefacts in another domain, and cascades are first-class. |
NS0-P10 | Names are governed · Codes are never names. Public names follow the marks policy (governance/OPEN_BOUNDARY_IPR_AND_LICENSING.md, section 7). A system or component is shown by its neutral display name and its UNI; the UNI may change with context (NS-9), and no name infringes anyone’s mark. |
NS0-P11 | Community-owned development · Proposals, comments, decisions and versions of every standard are themselves artefacts with UNIs. The development process is specified (NS-13) and open, and authority to adopt is recorded, never assumed. |
NS0-P12 | Fail closed · Missing evidence, a missing legal state, a missing policy decision or unavailable verification results in a refusal with a typed reason, never in a pass. |
UNI contextuels (déploiements, instances, instances de programme)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.
| Règle | Texte |
|---|---|
NS9-R1 | Each deployment or programme instance shall have one context record; the concept keeps its own UNI; context.ofUni is required and shall resolve. |
NS9-R2 | Context identifiers shall be allocated by the catalogue for their SCOPE; they shall not be derived from names or typed by hand. |
NS9-R3 | The supported claim level, legal state and conformance evidence of a context are its own; they shall not be inherited from the concept or from another context. |
NS9-R4 | Closing a context shall not delete it: context.validUntil est défini et le statut devient WITHDRAWN or SUPERSEDED avec supersededBy. |
NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
Politiques et clauses (obligations lisibles par machine : définition, caractère contraignant, évaluation et application)
Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.
| Règle | Texte |
|---|---|
NS10-R1 | Every obligation that an implementation enforces shall be a clause with a UNI; code may implement a rule, but no rule shall be enforced without a clause record that names it. |
NS10-R2 | Subjects shall be contextual UNIs; names, labels or free text shall not bind. |
NS10-R3 | The predicate shall be data in a declared language; evaluators shall record the engine and its version; two conformant evaluators shall reach the same result for the same clause and the same inputs. |
NS10-R4 | External obligations shall be cited, not copied. |
NS10-R5 | Failure effects shall be typed; refuse est la valeur par défaut pour blocking clauses dans des contextes de production. |
NS10-R6 | A clause or policy whose legalState is other than APPROVED may be evaluated, but its results shall be displayed as claims under review. |
NS10-R7 | Policies and clauses shall be append-only artefacts: withdrawal and supersession keep the record. |
Vérification et suivi (preuves, attestations, observation de la conformité en confiance zéro)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.
| Règle | Texte |
|---|---|
NS11-R1 | A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest. |
NS11-R2 | Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary. |
NS11-R3 | Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12). |
NS11-R4 | Attestations shall be append-only and superseded rather than changed; monitoring records shall be observations with record UNIs. |
NS11-R5 | Every displayed conformance value shall carry its evaluation instant and its evaluator; projections shall not store verdicts. |
NS11-R6 | Exports to Verifiable Credentials, in-toto or PROV-O are crosswalks; the Nexus attestation shall remain the record of truth. |
Artefacts logiciels, de modèles et d’IA/ML (chaîne d’approvisionnement, fiches de modèle, fiches de jeux de données)
Status proposed · software, models and capability lifecycle; trust, authorisation and assurance · NXS-STD-ST-000012.
| Règle | Texte |
|---|---|
NS12-R1 | Each software release shall carry a bill of materials, a build attestation and signatures as evidence of the UNI version. |
NS12-R2 | Each model shall carry a model card and each dataset a dataset sheet; both shall cite their sources by UNI. |
NS12-R3 | Agents shall act under recorded mandates and shall be credited as agents; they shall not adopt or certify. |
NS12-R4 | AI governance obligations shall be clauses bound to contextual UNIs and evaluated, not prose assurances. |
Questions et réponses.
Are these all the rules for cyber and digital risk?
Que désigne un identifiant de règle tel que NS1-R5 ?
Around cyber and digital risk.
Contribuez à façonner les normes relatives au risque cyber et numérique.
Les gouvernements, les autorités de réglementation, les organismes de normalisation, l'industrie, le monde universitaire et les communautés sont invités à façonner le catalogue avant sa première version officielle, prévue pour 2030 : commenter un projet, proposer une modification, rejoindre un groupe de travail ou accueillir un exercice sur le terrain.
Statut et usage. Les Nexus Standards sont des normes proposées, élaborées selon un processus ouvert sous NS-13 et publiées pour un usage volontaire ; elles ne constituent ni une certification, ni une accréditation, ni une approbation réglementaire, et leur adoption reste une décision du Global Standards Council et, dans chaque pays, de son Conseil national des normes. Un UNI (Unique Nexus Identifier) identifie un artefact ; il ne le certifie pas. Les noms des organismes de normalisation et de leurs normes appartiennent à leurs détenteurs et ne servent qu’à identifier les documents ; aucun texte de norme externe n’est reproduit ici. Nexus Standards n’est ni affilié à, ni approuvé ou certifié par un organisme de normalisation nommé ici.
Licences : CC BY 4.0 pour le texte des normes, les registres, les schémas et les données ; Apache-2.0 pour le code de référence. Les normes externes sont citées par leur nom, leur numéro et un lien, sous leurs propres licences. Les données, bibliothèques et polices de tiers conservent leurs propres licences : voir Mentions relatives aux tiers.