Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
BS ISO IEC 09798 — Information Technology — Security Techniques — Entity Authentication Series
Information Technology — Security Techniques — Entity Authentication (1999–2010 Editions, 4 Parts)
🔐 BS ISO/IEC 9798 is the British Standard implementation, adopted by BSI, of the ISO/IEC 9798 international series prepared by Technical Committee IST/33 (IT — Security techniques), classified under ICS 35.040. The series provides a standardized cryptographic framework for entity authentication, defining the protocol structures and technical mechanisms by which a trusted confirmation of identity is established between communicating parties. It is a foundational standard for the design and evaluation of identity authentication schemes in electronic banking, access control, network authentication, smart cards, and mobile payments.
💡 The essence of entity authentication is “proving that I know a secret without revealing it.” The BS ISO/IEC 9798 series normalizes various proof methods (cryptographic check, zero-knowledge, manual transfer) into interoperable mechanisms, giving security protocol design a clear structure and evaluation a sound basis.
1. Series Overview 📌
The BS ISO/IEC 9798 series consists of several parts; this batch covers Parts 1, 4, 5, and 6. Part 1 is the general part, giving the common model, terminology, and requirements for entity authentication; Part 4 specifies mechanisms using a cryptographic check function (e.g., MAC); Part 5 specifies mechanisms using zero-knowledge techniques; Part 6 specifies mechanisms using manual data transfer. The series supersedes earlier editions and incorporates technical corrigenda from 2009 and 2012, reflecting continued refinement of authentication mechanism security.
The series primarily serves security protocol and cryptographic algorithm designers, PKI and identity-management implementers, smart card and secure-chip vendors, risk-assessment and compliance auditors, and solution architects in banking, government, and telecommunications where strong identity authentication is required.
2. Structure and Technical Highlights 📋
| Standard | Title | Core Content |
|---|---|---|
| BS ISO/IEC 9798-1:2010 | General | Common model, terms and definitions, and general requirements for entity authentication, providing the framework for the other parts |
| BS ISO/IEC 9798-4:1999 | Mechanisms using a cryptographic check function | One-way and mutual authentication mechanisms based on message authentication codes (MAC)/cryptographic check functions, including two-pass and three-pass flows |
| BS ISO/IEC 9798-5:2009 | Mechanisms using zero-knowledge techniques | Authentication mechanisms based on zero-knowledge proofs, allowing the prover to prove identity without the verifier learning the secret |
| BS ISO/IEC 9798-6:2010 | Mechanisms using manual data transfer | Mechanisms for establishing or confirming authentication by manually transferring data (scanned version, written from public-domain knowledge) |
⚠️ BS ISO/IEC 9798-6 in this material is a scanned version; its description is written from public-domain knowledge of the standard. Please refer to the official BSI publication for the authoritative text.
3. Key Technical Requirements 🔧
The key technical requirements of the BS ISO/IEC 9798 series center on the security properties of the authentication protocol:
- One-pass authentication: a single message exchange confirms one party’s identity to another; suitable for low-cost, low-risk simple scenarios.
- Two-pass / Mutual authentication: both parties confirm each other’s identity, typically via two or three message exchanges, preventing replay and impersonation attacks.
- Cryptographic check function (Part 4): use a message authentication code (MAC) or cryptographic check function over identifiers and random numbers; the verifier confirms identity by the check result.
- Zero-knowledge techniques (Part 5): the prover convinces the verifier that it knows a secret without revealing any useful information about the secret, protecting the prover’s long-term key.
- Replay protection: use random numbers, timestamps, or sequence numbers to prevent an attacker from intercepting and replaying legitimate authentication messages.
- Manual data transfer (Part 6): in the absence of a trusted communication channel, confirm keys or identity by manually transferring a small amount of verification data (e.g., check codes).
🚨 The security of an entity authentication scheme depends on the unpredictability of random numbers and the secrecy of keys. If the random number generator is weak or key management is poor, even a standard-compliant protocol structure may be broken by replay, pre-computation, or side-channel attacks.
4. Engineering Practice Applications 🛠️
In engineering practice, the BS ISO/IEC 9798 series is mainly applied to:
- 🔍 Network access and device authentication: in VPN and WLAN 802.1X, MAC-based authentication mechanisms verify the legitimate identity of terminals and network devices.
- 🔧 Financial and payment security: bank cards, e-cash, and mobile payment terminals confirm both parties’ identity via mutual authentication mechanisms, preventing counterfeit cards and man-in-the-middle attacks.
- 📊 Smart cards and secure chips: smart cards and readers, security modules and hosts mutually authenticate per the standard mechanisms, forming the basis of application-layer security.
- 📋 Key management and zero-knowledge identity proofs: zero-knowledge mechanisms in identity-proofing systems let users verify identity without exposing passwords or private keys, suited to high-security authentication scenarios.
✅ It is recommended that security solution designers combine the BS ISO/IEC 9798 series with ISO/IEC 9797 (message authentication codes) and ISO/IEC 18033 (encryption algorithms), build authentication protocols per the standard mechanisms, and validate resistance to attack through security evaluation.
5. Frequently Asked Questions ❓
❓ Q: What is the difference between entity authentication and message authentication?
A: Message authentication (e.g., message authentication codes per ISO/IEC 9797) verifies message integrity and origin, while entity authentication (this series) confirms the identity of the communication peer at session establishment, typically including a random-number exchange to bind the session and prevent replay. The two are often used together.
A: Message authentication (e.g., message authentication codes per ISO/IEC 9797) verifies message integrity and origin, while entity authentication (this series) confirms the identity of the communication peer at session establishment, typically including a random-number exchange to bind the session and prevent replay. The two are often used together.
❓ Q: Why are zero-knowledge techniques more secure than traditional password authentication?
A: In traditional password authentication, the password is transmitted or stored on the server, creating leak risk. Zero-knowledge proofs let the prover convince the verifier of knowledge of a secret without revealing any useful information; even an eavesdropper who captures all communication cannot recover the secret, giving significantly higher security.
A: In traditional password authentication, the password is transmitted or stored on the server, creating leak risk. Zero-knowledge proofs let the prover convince the verifier of knowledge of a secret without revealing any useful information; even an eavesdropper who captures all communication cannot recover the secret, giving significantly higher security.
❓ Q: In Part 4, what is the difference between “two-pass” and “three-pass” authentication?
A: Two-pass authentication typically has one party initiate and the other respond, suitable for one-way or simple mutual confirmation; three-pass adds an extra confirmation message, enabling stricter mutual authentication and preventing certain replay and man-in-the-middle attacks, suited to high-security scenarios.
A: Two-pass authentication typically has one party initiate and the other respond, suitable for one-way or simple mutual confirmation; three-pass adds an extra confirmation message, enabling stricter mutual authentication and preventing certain replay and man-in-the-middle attacks, suited to high-security scenarios.
❓ Q: When is manual data transfer used?
A: When there is no trusted electronic channel between parties (e.g., first pairing, initial key distribution, off-device authentication), a small amount of verification data (short check codes, digital fingerprints) is manually checked or entered to confirm keys or identity, preventing man-in-the-middle key substitution.
A: When there is no trusted electronic channel between parties (e.g., first pairing, initial key distribution, off-device authentication), a small amount of verification data (short check codes, digital fingerprints) is manually checked or entered to confirm keys or identity, preventing man-in-the-middle key substitution.
❓ Q: How does BS ISO/IEC 9798 relate to actual protocols such as TLS/SSL?
A: Actual protocols like TLS embody the authentication mechanism ideas standardized in ISO/IEC 9798 (e.g., certificate- and MAC-based mutual authentication), but TLS is an industry protocol while ISO/IEC 9798 is an abstract standard mechanism framework — a “mechanism specification” versus “engineering implementation” relationship.
A: Actual protocols like TLS embody the authentication mechanism ideas standardized in ISO/IEC 9798 (e.g., certificate- and MAC-based mutual authentication), but TLS is an industry protocol while ISO/IEC 9798 is an abstract standard mechanism framework — a “mechanism specification” versus “engineering implementation” relationship.