Concessionárias de energia e redes: normas aplicáveis
As 5 normas listadas para concessionárias e redes de energia no registro, cada uma com seu status, seu UNI (Unique Nexus Identifier) e as regras enunciadas em seu texto.
- Nexus Standards: NS-0, NS-3, NS-9, NS-10, NS-11.
- Normas abertas: normas de confiabilidade NERC Critical Infrastructure Protection; Diretiva NIS2 (UE) 2022/2555; Diretiva relativa à resiliência das entidades críticas (UE) 2022/2557; NIST Cybersecurity Framework 2.0; NIST SP 800-161r1 Cybersecurity Supply Chain Risk Management Practices.
- Dados e feeds: Global Power Plant Database v1.3.0; ENTSO-E Transparency Platform; World Development Indicators; OECD Data Explorer (incluindo o Creditor Reporting System e estatísticas de seguros e pensões).
- Articula-se com: Concessionárias de água e bacias; Digital, telecomunicações e plataformas; Transporte, logística e cadeias de suprimentos; Finanças, seguros e mercados de capitais.
- Nexus Standards
- 5
- NS-0, NS-3, NS-9
- Normas abertas
- 5
- citadas, nunca copiadas
- Dados e feeds
- 4
- indicado para referência
- Acoplamentos
- 4
- com outras áreas
Constituição e princípios
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000004.
| Regra | 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 | Legível por máquina primeiro · Todo elemento normativo existe como dados (registro, esquema, cláusula) antes de existir como prosa; a prosa explica, os dados governam. Um padrão sem forma legível por máquina não é um 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 · Um UNI identifica e resolve; 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. |
UNIs de registros de risco (gramática, correspondência com o legado, autoridade de alocação)
Status proposed · trust, authorisation and assurance; canonical risk data, records and provenance · NXS-STD-ST-000003.
A NS-3 apresenta seus requisitos em seções, e não em uma tabela de regras.
UNIs contextuais (implantações, instâncias, instâncias de programa)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000005.
| Regra | 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 é definido e o status passa a ser WITHDRAWN or SUPERSEDED com supersededBy. |
NS9-R5 | Display names in context shall follow the marks policy; the UNI, not the name, is the key everywhere. |
Políticas e cláusulas (obrigações legíveis por máquina: definição, caráter vinculante, avaliação e execução)
Status proposed · trust, authorisation and assurance; integrated posture and executive synthesis · NXS-STD-ST-000006.
| Regra | 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 é o padrão para blocking cláusulas em contextos de produção. |
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. |
Verificação e monitoramento (evidências, atestações, observação da conformidade de confiança zero)
Status proposed · trust, authorisation and assurance · NXS-STD-ST-000007.
| Regra | 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. |
Perguntas e respostas.
Estas são todas as regras para concessionárias de energia e redes elétricas?
O que denota um identificador de regra como NS1-R5?
Around energy utilities and grids.
Ajude a moldar as normas para concessionárias e redes de energia.
Governos, reguladores, organismos de normalização, indústria, academia e comunidades são convidados a moldar o catálogo antes da sua primeira versão oficial, prevista para 2030: comentar um rascunho, propor uma alteração, ingressar em um grupo de trabalho ou sediar um exercício de campo.
Status e uso. As Nexus Standards são normas propostas, desenvolvidas por meio de um processo aberto segundo a NS-13 e publicadas para uso voluntário; não constituem certificação, acreditação nem aprovação regulatória, e a adoção continua sendo uma decisão do Global Standards Council e, em cada país, de seu Conselho Nacional de Normas. Um UNI (Unique Nexus Identifier) identifica um artefato; não o certifica. Os nomes dos organismos de normalização e de suas normas pertencem aos seus responsáveis e são usados apenas para identificar os documentos; nenhum texto de norma externa é reproduzido aqui. A Nexus Standards não é afiliada, endossada nem certificada por nenhum organismo de normalização aqui mencionado.
Licenças: CC BY 4.0 para o texto das normas, registros, esquemas e dados. Apache-2.0 para o código de referência. As normas externas são citadas por nome, número e link, sob suas próprias licenças. Dados, bibliotecas e fontes tipográficas de terceiros mantêm suas próprias licenças: veja os Avisos de terceiros.