Cyber- und digitales Risiko: anwendbare Normen
Die 5 im Register für Cyber- und digitale Risiken aufgeführten Standards, jeweils mit Status, UNI (Unique Nexus Identifier) und den in ihrem Text festgelegten Regeln.
- Nexus Standards: NS-0, NS-9, NS-10, NS-11, NS-12.
- Offene Standards: 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).
- Gekoppelt mit: Finanzen und Wirtschaft; Kritische Infrastrukturen und kritische Einrichtungen; Informationsintegrität und Vertrauen; Cyberresilienz und digitale operationale Resilienz.
- Nexus Standards
- 5
- NS-0, NS-9, NS-10
- Offene Standards
- 8
- genannt, nie kopiert
- Daten und Feeds
- 4
- zur Referenz aufgeführt
- Kopplungen
- 4
- mit anderen Bereichen
Verfassung und Grundsätze
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000004.
| Regel | Text |
|---|---|
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 | Zuerst maschinenlesbar · Jedes normative Element existiert als Daten (Register, Schema, Klausel), bevor es als Prosa existiert; Prosa erklärt, Daten regeln. Ein Standard ohne maschinenlesbare Form ist kein 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 | Ehrlich · Ein UNI identifiziert und löst auf; er zertifiziert niemals. 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. |
Kontextuelle UNIs (Bereitstellungen, Instanzen, Programminstanzen)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.
| Regel | Text |
|---|---|
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 wird gesetzt und der Status wird WITHDRAWN or SUPERSEDED mit supersededBy. |
NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
Richtlinien und Klauseln (maschinenlesbare Verpflichtungen: Definition, Bindung, Evaluierung und Durchsetzung)
Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.
| Regel | Text |
|---|---|
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 ist die Voreinstellung für blocking Klauseln in Produktionskontexten. |
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. |
Verifizierung und Überwachung (Evidenz, Attestierungen, Zero-Trust-Beobachtung der Konformität)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.
| Regel | Text |
|---|---|
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. |
Software-, Modell- und KI/ML-Artefakte (Lieferkette, Modellkarten, Datenblätter)
Status proposed · software, models and capability lifecycle; trust, authorisation and assurance · NXS-STD-ST-000012.
| Regel | Text |
|---|---|
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. |
Fragen und Antworten.
Sind dies alle Regeln für Cyber- und digitale Risiken?
Was bezeichnet eine Regelkennung wie NS1-R5?
Around cyber and digital risk.
Gestalten Sie die Standards für Cyber- und digitale Risiken mit.
Regierungen, Regulierungsbehörden, Normungsgremien, Wirtschaft, Wissenschaft und Gemeinschaften sind eingeladen, den Katalog vor seiner ersten offiziellen Veröffentlichung, die für 2030 angestrebt wird, mitzugestalten: einen Entwurf kommentieren, eine Änderung vorschlagen, einer Arbeitsgruppe beitreten oder eine Feldübung ausrichten.
Status und Nutzung. Die Nexus Standards sind vorgeschlagene Standards, die in einem offenen Verfahren nach NS-13 entwickelt und zur freiwilligen Nutzung veröffentlicht werden; sie stellen keine Zertifizierung, Akkreditierung oder behördliche Genehmigung dar, und die Annahme bleibt eine Entscheidung des Global Standards Council und, in jedem Land, seines National Standards Council. Eine UNI (Unique Nexus Identifier) identifiziert ein Artefakt; sie zertifiziert es nicht. Die Namen von Normungsorganisationen und ihren Standards gehören deren Trägern und werden nur zur Identifizierung der Dokumente verwendet; kein Text eines externen Standards wird hier wiedergegeben. Nexus Standards ist mit keiner hier genannten Normungsorganisation verbunden, wird von keiner unterstützt und ist von keiner zertifiziert.
Lizenzen: CC BY 4.0 für Standardtexte, Register, Schemata und Daten; Apache-2.0 für Referenzcode. Externe Standards werden mit Name, Nummer und Link unter ihren eigenen Lizenzen zitiert. Daten, Bibliotheken und Schriften Dritter behalten ihre eigenen Lizenzen: siehe Hinweise Dritter.