Identity, authorisation and zero trust: conformance
How an implementer in identity, authorisation and zero trust 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).
- Nexus Standards: NS-9, NS-10, NS-11.
- オープン標準:NIST SP 800-207 Zero Trust Architecture、OpenID Connect Core 1.0、The OAuth 2.1 Authorization Framework(インターネット・ドラフト)、Verifiable Credentials Data Model v2.0、CISA Zero Trust Maturity Model 2.0、Web Authentication Level 2。
- データとフィード:FIDO Metadata Service(MDS3)、CISA Known Exploited Vulnerabilities カタログ。
- 関連分野:ゼロトラスト基盤、方針と条項、検証と監視。
概要
- 01自己評価規則に照らして
- 02条項群NS-10
- 03証拠参照のみで、埋め込みはしない
- 04証明NS-11、指名された評価者
- 05報告書結果から生成
- Nexus Standards
- 3
- NS-9, NS-10, NS-11
- オープン標準
- 6
- 名称を示し、複製しない
- データとフィード
- 2
- 参考として掲載
- 連動
- 3
- 他の分野との
横断的能力の階層に掲載されている標準
この階層のプログラム領域を、レジストリに掲載された標準と対照したものです。この領域の行が、自己評価の初期範囲を定めます。
カバレッジ・マトリクス塗りつぶされたセルは、そのエリアが登録簿に当該標準を掲載していることを示します。状態の用語は登録簿のものに従います。
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.yamltruthfully;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.
Initial self-assessment for identity, authorisation and zero trust
各適用標準の最初の規則。自己評価は実装者による表明であり、NS-11 に基づいて検証できます。
| 規則 | 要件 | 標準 |
|---|---|---|
NS11-R1 | A conformance statement shall rest on an attestation, and an attestation shall name an evaluator, a mandate, evidence references and a digest. | NS-11 |
NS11-R2 | Under zero trust, subject and evaluator shall be distinct, and production evaluations shall run outside the subject’s trust boundary. | NS-11 |
NS11-R3 | Missing or unresolvable evidence shall yield INDETERMINATE or REFUSED, never PASS (NS0-P12). | NS-11 |
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. | NS-10 |
NS10-R2 | Subjects shall be contextual UNIs; names, labels or free text shall not bind. | NS-10 |
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. | NS-10 |
アテステーション
One attestation is recorded per clause, per subject, per evaluation (AT カテゴリー、追記のみ)。結果: 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 常に 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.
モニタリング
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.
報告
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)であり、公開(NS-8)できるのは次の場合に限られます:その legalState allows. A report does not say "certified" or "compliant" except when it quotes an authority decision by reference.
適合性声明の表示
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.
質問と回答。
How does a conformance report in identity, authorisation and zero trust relate to the decisions of other bodies?
エビデンスが欠けている場合はどうなりますか。
Around identity, authorisation and zero trust.
Shape the standards for identity, authorisation and zero trust.
政府、規制当局、標準化団体、産業界、学界、コミュニティの皆さまには、初の正式リリース(2030 年を目標)に先立ち、カタログの形づくりにご参加いただけます。草案へのコメント、変更の提案、作業部会への参加、フィールド演習の主催などです。
位置づけと利用。Nexus Standards は NS-13 に基づく公開プロセスで策定され、任意利用のために公表される提案標準です。認証、認定、規制上の承認には当たらず、採用は Global Standards Council と各国の国家標準評議会の決定事項です。UNI(Unique Nexus Identifier)は成果物を識別するものであり、認証するものではありません。標準化機関とその標準の名称はそれぞれの管理者に帰属し、文書の識別のためにのみ使用します。外部標準の本文はここに転載していません。Nexus Standards はここに挙げたいかなる標準化機関とも提携しておらず、推奨や認証も受けていません。
ライセンス:標準の本文、登録簿、スキーマ、データは CC BY 4.0、参照コードは Apache-2.0 です。外部標準は名称、番号、リンクで引用し、それぞれのライセンスに従います。第三者のデータ、ライブラリ、フォントはそれぞれのライセンスに従います。「第三者に関する告知」をご覧ください。