Zero Trust Engineering — Multi-factor and phishing-resistant authentication

/02 About

Identity and access engineering reference for multi-factor and phishing-resistant authentication, including policy, logical interfaces, recovery and assurance.

Purpose: Multi-factor and phishing-resistant authentication. Domain: Identity and access. Family: decision. Scenario trigger: Challenge principal for strong authentication. Input assurance: Authenticator possession, verifier origin and phishing resistance. Evaluation: Evaluate multifactor proof and assurance requirements. Governing policy: Risk-adjusted authenticator acceptance policy. Resource-side obligation: Accept verified factors or demand stronger authenticator. Protected concern: High-sensitivity access request. Logical interface: Authenticator proof challenge factor binding and assurance assertion. Evidence: Authentication factor challenge outcome and assurance evidence. Failure: Phishable factor or mismatched verifier origin. Required recovery: Block session and invoke alternative trusted proof. Architectural invariant: Strong authentication must resist credential replay and unintended verifier binding Adoption: replace reference roles with concrete owner-controlled services. Specify exact provider/consumer identities, schema fields and classifications, signal provenance and freshness, idempotency, authorization lifetime, timeout/retry limits, observation and tamper evidence. A denied or failed operation must not silently become a permitted one. Scope: original vendor-neutral, implementation-agnostic technical reference model. Illustrative logical components and behaviors are neither a deployed system nor evidence of regulatory compliance. Package identities remain stable within the package; cross-package semantic reconciliation requires separate explicit registry support.

Curated · other · unspecified · Published by Lattix · 28 elements · 34 relationships · validated on publish