Riesgo cibernético y digital: normas aplicables
Las 5 normas enumeradas para el riesgo cibernético y digital en el registro, cada una con su estado, su UNI (Unique Nexus Identifier) y las reglas establecidas en su texto.
- Nexus Standards: NS-0, NS-9, NS-10, NS-11, NS-12.
- Normas abiertas: 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; Marco de Ciberseguridad 2.0 del NIST; 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).
- Se acopla con: riesgo financiero y económico; infraestructura crítica y entidades críticas; integridad de la información y confianza; ciberresiliencia y resiliencia operativa digital.
- Nexus Standards
- 5
- NS-0, NS-9, NS-10
- Estándares abiertos
- 8
- citado, nunca copiado
- Datos y flujos
- 4
- indicado como referencia
- Acoplamientos
- 4
- con otras áreas
Constitución y principios
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000004.
| Regla | Texto |
|---|---|
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 | Primero legible por máquina · Todo elemento normativo existe como datos (registro, esquema, cláusula) antes de existir como prosa; la prosa explica, los datos rigen. Una norma sin forma legible por máquina no es un 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 | Honesto · Un UNI identifica y resuelve; nunca certifica. 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 contextuales (despliegues, instancias, instancias de programa)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.
| Regla | Texto |
|---|---|
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 se establece y el estado pasa a ser WITHDRAWN or SUPERSEDED con supersededBy. |
NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
Políticas y cláusulas (obligaciones legibles por máquina: definición, carácter vinculante, evaluación y cumplimiento)
Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.
| Regla | Texto |
|---|---|
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 es el valor por defecto para blocking cláusulas en contextos de producción. |
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. |
Verificación y seguimiento (evidencia, atestaciones, observación de la conformidad de confianza cero)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.
| Regla | Texto |
|---|---|
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. |
Artefactos de software, modelos e IA/ML (cadena de suministro, fichas de modelo, fichas de conjuntos de datos)
Status proposed · software, models and capability lifecycle; trust, authorisation and assurance · NXS-STD-ST-000012.
| Regla | Texto |
|---|---|
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. |
Preguntas y respuestas.
Are these all the rules for cyber and digital risk?
¿Qué designa un identificador de regla como NS1-R5?
Around cyber and digital risk.
Contribuya a dar forma a los estándares de riesgo cibernético y digital.
Se invita a los gobiernos, los reguladores, los organismos de normalización, la industria, el mundo académico y las comunidades a dar forma al catálogo antes de su primera versión oficial, prevista para 2030: comentar un borrador, proponer un cambio, unirse a un grupo de trabajo o acoger un ejercicio sobre el terreno.
Estado y uso. Las Nexus Standards son normas propuestas, elaboradas mediante un proceso abierto según NS-13 y publicadas para uso voluntario; no constituyen certificación, acreditación ni aprobación regulatoria, y su adopción sigue siendo una decisión del Global Standards Council y, en cada país, de su Consejo Nacional de Normas. Un UNI (Unique Nexus Identifier) identifica un artefacto; no lo certifica. Los nombres de los organismos de normalización y de sus normas pertenecen a sus titulares y se usan solo para identificar los documentos; aquí no se reproduce ningún texto de una norma externa. Nexus Standards no está afiliada a ningún organismo de normalización aquí nombrado, ni respaldada o certificada por él.
Licencias: CC BY 4.0 para el texto de los estándares, los registros, los esquemas y los datos; Apache-2.0 para el código de referencia. Los estándares externos se citan por nombre, número y enlace, conforme a sus propias licencias. Los datos, bibliotecas y fuentes tipográficas de terceros conservan sus propias licencias: véanse los Avisos de terceros.