Security Architecture
Where identity, Agent, provider and key boundaries live.
Security →Assess identity, authorization, signing keys, verification and evidence against published scope.
Organizational governance and certificate scope
Identity and federated authentication
Authentication and authorization • module scope
Certificate and infrastructure-scoped signing
Transaction outcomes • not organizational certification
Where identity, Agent, provider and key boundaries live.
Security →Certificate, chain, status and time.
Verification →Transaction context that survives beyond signing.
Evidence →An enterprise reviewer needs to see which evidence belongs to organizational governance, which belongs to authentication/cryptographic modules, and which belongs to an individual signing transaction.
ISO/IEC 27001 anchors information-security governance, risk, audit and improvement within the certificate scope.
VNeID, OpenID and FIDO2 answer different identity/authentication questions.
Consent, Passkey and Trusted SIC relate to how user intent/approval is established for a transaction.
CA/RSSP/QSCD/HSM form the applicable signature-creation layer.
Validation examines integrity, certificate/status and trusted time under an applicable policy.
Transaction identifiers, hashes, events, results and audit records create a traceable evidence chain.
Evidence in one layer must not be used as proof for every other layer.
Choose a topic to review implementation details.
Applies only to the certificate scope and source.
Requires matching verification evidence.
Public source; not proof of a specific deployment.
Requires confirmed contract and environment.
A model for assessment and integration design.
A proposed design, not a deployed system.
Offline data and results.