Abstract

Maintenance revision

Status
Published
Publication Date
30-Jun-2005
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Jul-2005
Due Date
01-Jul-2005
Completion Date
01-Jul-2005

Buy Documents

Standard

SIST EN 300 175-7 V1.8.1:2005

English language (101 pages)
Preview
Preview
e-Library read for
×1 day

SIST EN 300 175-7 V1.8.1:2005 is the Slovenian adoption of ETSI EN 300 175-7 Version 1.8.1 for Digital Enhanced Cordless Telecommunications (DECT) Common Interface (CI), Part 7. It is a maintenance revision focused on DECT security features: authentication, confidentiality, key handling, and the way those functions are integrated into the air interface and network procedures. The standard is aimed at people who design, integrate, test, or operate DECT equipment and systems.

What does SIST EN 300 175-7 V1.8.1:2005 specify?

SIST EN 300 175-7 V1.8.1:2005 specifies the DECT security architecture, the cryptographic processes used to support it, and the rules for integrating those security features into the DECT Common Interface. It also describes how the security functions are managed and how they relate to fixed systems and local network configurations.

The document is organized around four main clauses:

  • Clause 4 - security architecture
  • Clause 5 - algorithms for security processes
  • Clause 6 - integration of security
  • Clause 7 - use of security features
AnnexWhat it covers
ASecurity threats analysis
BSecurity features and operating environments, including enrolment and roaming
CReasons for not adopting public key techniques
DOverview of security features
ELimitations of DECT security
FSecurity features related to target networks and example profiles
GCompatibility of DECT and GSM authentication, including SIM and DAM functionality
HDECT Standard Authentication Algorithm (DSAA)
JDECT Standard Cipher (DSC)
KClarifications, bit mappings and examples for DSAA and DSC
LBibliography
MChange history

What are the key requirements of SIST EN 300 175-7 V1.8.1:2005?

SIST EN 300 175-7 V1.8.1:2005 defines five security services for DECT and then shows how they are built from authentication and key-stream processes. In practice, the standard tells implementers what security functions must be supported, how the keys and challenges are used, and how the network and radio layers exchange the related messages.

1) The security architecture is built around five services

Clause 4.2 defines authentication of a PT, authentication of an FT, mutual authentication, data confidentiality, and user authentication. That matters because a DECT system can be designed to support only some of these services, depending on the deployment and the operator’s security policy.

2) Authentication uses challenge-response exchanges and session keys

Clause 4.3 describes authentication of a PT and authentication of an FT as challenge-response procedures based on an authentication key K. The PT and FT derive session keys - KS and KS' - from K and a shared value RS, then use random values such as RAND_F and RAND_P to produce response values RES1, RES2, XRES1, and XRES2.

In practice, this means the authentication key itself is not sent over the air. Instead, both sides prove knowledge of the key by computing matching results, which is the basis for admitting or rejecting the call.

3) Confidentiality can use either a derived or a static cipher key

Clause 4.3.4 and clause 4.4.3.3 describe data confidentiality using a Derived Cipher Key (DCK) or a Static Cipher Key (SCK). The DCK is typically derived during authentication, while the SCK is a fixed key used for confidentiality in systems that rely on that model.

For implementers, this distinction affects how often keys change and how much key management the system needs. The document also ties confidentiality to the key stream generator (KSG), which produces the stream used by the cipher.

4) Security services can be combined in defined ways

Clause 4.6 lists the intended combinations of services, such as PT authentication alone, PT authentication followed by FT authentication, and authentication followed by confidentiality using a DCK. It also identifies confidentiality using an SCK and confidentiality using a previously established DCK.

This is important because it shows the supported operating sequences. A system designer can see whether a deployment should authenticate first and then encrypt, or use a fixed confidentiality key, and can plan network control accordingly.

5) Clause 6 integrates security into NWK and MAC procedures

Clause 6 maps the security services into DECT procedures. The NWK layer handles authentication exchanges and access-rights messages, while the MAC layer handles ciphering control, encryption start and stop, and handover of the encryption process.

In practice, this is where the standard becomes implementable:

  • AUTHENTICATION-REQUEST and AUTHENTICATION-REPLY carry the authentication exchange
  • ACCESS-RIGHTS-REQUEST, ACCESS-RIGHTS-ACCEPT, and ACCESS-RIGHTS-REJECT negotiate algorithms and keys
  • START.REQ, START.CONF, START.GRANT, STOP.REQ, STOP.CONF, and STOP.GRANT control ciphering

6) The encryption method is defined for several slot and modulation cases

Clause 6.4 adapts encryption to singlesubfield and multisubfield protected B-field formats, as well as half slot, double slot, multi-bearer, and 4-, 8-, 16- and 64-level modulation formats. The clause also defines how data bits are mapped to key-stream bits.

This matters because the encryption procedure is not a single fixed frame format. Implementers must apply the right mapping for the chosen radio format so that encryption and decryption remain interoperable.

7) Key management supports roaming and central administration

Clause 7 describes how authentication keys, session keys, and cipher keys may be generated, distributed, stored, and reused in fixed networks. It discusses roaming use cases and the use of session keys when the actual authentication key K is not held at the point where authentication is performed.

For operators, this is the practical key-management guidance. It shows when a network can use K directly, when it can use RS-KS-KS' triples, and how a DCK can be retained for later calls.

8) The document also covers access-rights negotiation and UAK allocation

Clause 6.5 lets a PT signal the authentication and cipher algorithms it wants to use through <<AUTH-TYPE>> and <<CIPHER-INFO>>, and clause 6.5.6.2 describes over-the-air allocation of a UAK from a manually distributed AC. That matters for subscription and provisioning workflows, because the system can negotiate security capabilities instead of relying on a single fixed setup.

What terms does SIST EN 300 175-7 V1.8.1:2005 define?

SIST EN 300 175-7 V1.8.1:2005 uses a set of security terms that recur throughout the procedures and annexes.

  • Portable radio Termination (PT) - the portable DECT entity that participates in authentication and confidentiality exchanges.
  • Fixed radio Termination (FT) - the fixed DECT entity that verifies the portable side and can also be authenticated by it.
  • User Authentication Key (UAK) - a secret key used as part of user-related authentication key generation.
  • Derived Cipher Key (DCK) - a cipher key generated from authentication procedures and used for confidentiality.
  • Static Cipher Key (SCK) - a fixed cipher key used for confidentiality in systems that rely on a non-derived key.
  • DECT Standard Authentication Algorithm (DSAA) - the standard DECT authentication algorithm referenced in the annexes and examples.
  • DECT Standard Cipher (DSC) - the standard DECT cipher referenced for encryption.
  • User Personal Identification (UPI) - a value entered by the user and used in user authentication.

Who uses SIST EN 300 175-7 V1.8.1:2005?

SIST EN 300 175-7 V1.8.1:2005 is used by DECT equipment manufacturers, chipset and firmware developers, and system integrators who need to implement authentication and ciphering correctly. It is also used by network operators and service providers in Public Access Service (PAS), Business Cordless Telecommunications (BCT), and Residential Use (RU) environments.

Test laboratories and certification teams use it to check message formats, key handling, and encryption control. Security architects and quality managers use it to decide which DECT security services a product or deployment supports and how those services are managed in roaming and subscription scenarios.

Which standards are used with SIST EN 300 175-7 V1.8.1:2005?

SIST EN 300 175-7 V1.8.1:2005 relies on several related DECT and interface documents:

  • EN 300 175-1 - provides the general DECT Common Interface overview and base terms and definitions.
  • EN 300 175-2 - provides the Physical Layer (PHL) referenced by the DECT air interface.
  • EN 300 175-3 - provides the Medium Access Control (MAC) layer details used for the protected B-field formats and encryption placement.
  • EN 300 175-5 - provides the Network (NWK) layer procedures and message coding used in authentication exchanges.
  • EN 300 175-6 - provides identities and addressing, which are used when associating keys with DECT identities.
  • ETSI TS 100 977 - provides the SIM-ME interface reference used in the DECT and GSM compatibility discussion.
  • ETR 056 - provides the DECT system description and the target network environments referenced in Annex F.

What does the SIST EN 300 175-7 V1.8.1:2005 document contain?

The document contains the security architecture, process definitions, procedure descriptions, and integration rules needed to implement DECT security features. It includes message structures, authentication flows, ciphering control, handover behavior, and key-management options.

It also contains several useful technical aids:

  • Table-based message definitions for authentication and access-rights procedures
  • Encryption bit-mapping tables for different slot and modulation formats
  • Figures showing the overall security process, encryption start and stop sequences, and handover behavior
  • Worked examples and clarifications in Annex K to resolve DSAA and DSC interpretation issues
  • Annexes on threats, roaming, limitations, target-network profiles, and DECT/GSM compatibility

For implementation and testing, the most practical parts are the NWK and MAC procedures in clause 6, the key-management guidance in clause 7, and the clarifications and examples in Annex K.

Buy Documents

Standard

SIST EN 300 175-7 V1.8.1:2005

English language (101 pages)
Preview
Preview
e-Library read for
×1 day

Get Certified

Connect with accredited certification bodies for this standard

ANCE

Mexican certification and testing association.

EMA Mexico Verified

Intertek Slovenia

Intertek testing, inspection, and certification services in Slovenia.

UKAS Slovenia Verified

LNE (Laboratoire National de Métrologie et d'Essais)

French national laboratory for metrology and testing.

COFRAC France Verified

Sponsored listings

Frequently Asked Questions

SIST EN 300 175-7 V1.8.1:2005 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 7: Security features". This standard covers: Maintenance revision

Maintenance revision

SIST EN 300 175-7 V1.8.1:2005 is classified under the following ICS (International Classification for Standards) categories: 33.070.30 - Digital Enhanced Cordless Telecommunications (DECT). The ICS classification helps identify the subject area and facilitates finding related standards.

SIST EN 300 175-7 V1.8.1:2005 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


SLOVENSKI STANDARD
01-julij-2005
'LJLWDOQHL]EROMãDQHEUH]YUYLþQHWHOHNRPXQLNDFLMH '(&7 6NXSQLYPHVQLN &, 
GHO9DUQRVWQHODVWQRVWL
Digital Enhanced Cordless Telecommunications (DECT); Common Interface (CI); Part 7:
Security features
Ta slovenski standard je istoveten z: EN 300 175-7 Version 1.8.1
ICS:
33.070.30 'LJLWDOQHL]EROMãDQH Digital Enhanced Cordless
EUH]YUYLþQHWHOHNRPXQLNDFLMH Telecommunications (DECT)
'(&7
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

European Standard (Telecommunications series)

Digital Enhanced Cordless Telecommunications (DECT);
Common Interface (CI);
Part 7: Security features
2 ETSI EN 300 175-7 V1.8.1 (2004-11)

Reference
REN/DECT-000215-7
Keywords
DECT, radio, security
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2004.
All rights reserved.
TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI EN 300 175-7 V1.8.1 (2004-11)
Contents
Intellectual Property Rights.7
Foreword.7
Introduction .7
1 Scope.10
2 References.10
3 Definitions and abbreviations.11
3.1 Definitions.11
3.2 Abbreviations.11
4 Security architecture.12
4.1 Background.12
4.2 Security services.13
4.2.1 Authentication of a PT.13
4.2.2 Authentication of an FT.13
4.2.3 Mutual authentication.13
4.2.4 Data confidentiality.13
4.2.5 User authentication.13
4.3 Security mechanisms.13
4.3.1 Authentication of a PT.13
4.3.2 Authentication of an FT.15
4.3.3 Mutual authentication.16
4.3.4 Data confidentiality.16
4.3.4.1 Derived Cipher Key (DCK) .16
4.3.4.2 Static Cipher Key (SCK).16
4.3.5 User authentication.17
4.4 Cryptographic parameters and keys .17
4.4.1 Overview.17
4.4.2 Cryptographic parameters.17
4.4.3 Cryptographic keys.18
4.4.3.1 Authentication key K.19
4.4.3.2 Authentication session keys KS and KS'.19
4.4.3.3 Cipher key CK .20
4.5 Security processes.20
4.5.1 Overview.20
4.5.2 Derivation of authentication key, K.21
4.5.2.1 K is derived from UAK.21
4.5.2.2 K is derived from AC.21
4.5.2.3 K is derived from UAK and UPI.21
4.5.3 Authentication processes.22
4.5.3.1 Processes for the derivation of KS and KS'.22
4.5.3.2 Processes for the derivation of DCK, RES1 and RES2.22
4.5.4 Key stream generation .23
4.6 Combinations of security services.23
5 Algorithms for security processes .24
5.1 Background.24
5.1.1 A algorithm.24
5.2 Derivation of session authentication key(s).24
5.2.1 A11 process.24
5.2.2 A21 process.25
5.3 Authentication and cipher key generation processes.25
5.3.1 A12 process.25
5.3.2 A22 process.25
6 Integration of security .26
ETSI
4 ETSI EN 300 175-7 V1.8.1 (2004-11)
6.1 Background.26
6.2 Association of keys and identities .26
6.2.1 Authentication key.26
6.2.1.1 K is derived from UAK.26
6.2.1.2 K derived from AC.26
6.2.1.3 K derived from UAK and UPI .27
6.2.2 Cipher keys.27
6.3 NWK layer procedures.27
6.3.1 Background.27
6.3.2 Authentication exchanges.28
6.3.3 Authentication procedures.29
6.3.3.1 Authentication of a PT .29
6.3.3.2 Authentication of an FT .29
6.3.4 Transfer of Cipher Key, CK.29
6.4 MAC layer procedures .30
6.4.1 Background.30
6.4.2 MAC layer field structure .30
6.4.3 Data to be encrypted .31
6.4.4 Encryption process.31
6.4.5 Initialization and synchronization of the encryption process.34
6.4.6 Encryption mode control.34
6.4.6.1 Background.34
6.4.6.2 MAC layer messages.35
6.4.6.3 Procedures for switching to encrypt mode .35
6.4.6.4 Procedures for switching to clear mode .38
6.4.7 Handover of the encryption process .39
6.4.7.1 Bearer handover, uninterrupted ciphering.39
6.4.7.2 Connection handover, uninterrupted ciphering .39
6.4.7.3 External handover - handover with ciphering .40
6.4.8 Modifications for half slot specifications.40
6.4.8.1 Background.40
6.4.8.2 MAC layer field structure .40
6.4.8.3 Data to be encrypted.41
6.4.8.4 Encryption process.41
6.4.8.5 Initialization and synchronization of the encryption process .41
6.4.8.6 Encryption mode control.41
6.4.8.7 Handover of the encryption process.41
6.4.9 Modifications for double slot specifications.41
6.4.9.1 Background.41
6.4.9.2 MAC layer field structure .42
6.4.9.3 Data to be encrypted.42
6.4.9.4 Encryption process.42
6.4.9.5 Initialization and synchronization of the encryption process .43
6.4.9.6 Encryption mode control.43
6.4.9.7 Handover of the encryption process.44
6.4.10 Modifications for multi-bearer specifications.44
6.4.11 Modifications for 4-, 8-, 16- and 64-level modulation formats .44
6.4.11.1 Background.44
6.4.11.2 MAC layer field structure .45
6.4.11.3 Data to be encrypted.45
6.4.11.4 Encryption process.45
6.4.11.5 Initialization and synchronization of the encryption process .49
6.4.11.6 Encryption mode control.49
6.4.11.7 Handover of the encryption process.49
6.5 Security attributes.49
6.5.1 Background.49
6.5.2 Authentication protocols.50
6.5.2.1 Authentication of a PT .50
6.5.2.2 Authentication of an FT .51
6.5.3 Confidentiality protocols.52
6.5.4 Access-rights protocols.54
6.5.5 Key numbering and storage .55
ETSI
5 ETSI EN 300 175-7 V1.8.1 (2004-11)
6.5.5.1 Authentication keys.55
6.5.5.2 Cipher keys.55
6.5.6 Key allocation.56
6.5.6.1 Introduction.56
6.5.6.2 UAK allocation.56
7 Use of security features .57
7.1 Background.57
7.2 Key management options.58
7.2.1 Overview of security parameters relevant for key management.58
7.2.2 Generation of authentication keys .59
7.2.3 Initial distribution and installation of keys .60
7.2.4 Use of keys within the fixed network .60
7.3 Confidentiality service with a Cordless Radio Fixed Part (CRFP).64
7.3.1 General.64
7.3.2 CRFP initialization of PT cipher key.64
Annex A (informative): Security threats analysis.65
A.1 Introduction.65
A.2 Threat A - Impersonating a subscriber identity.66
A.3 Threat B - Illegal use of a handset (PP).66
A.4 Threat C - Illegal use of a base station (FP) .66
A.5 Threat D - Impersonation of a base station (FP) .67
A.6 Threat E - Illegally obtaining user data and user related signalling information .67
A.7 Conclusions and comments.68
Annex B (informative): Security features and operating environments.70
B.1 Introduction.70
B.2 Definitions.70
B.3 Enrolment options.70
Annex C (informative): Reasons for not adopting public key techniques.72
Annex D (informative): Overview of security features .73
D.1 Introduction.73
D.2 Authentication of a PT .73
D.3 Authentication of an FT .74
D.4 Mutual authentication of a PT and an FT.74
D.4.1 Direct method.74
D.4.2 Indirect method 1.74
D.4.3 Indirect method 2.74
D.5 Data confidentiality.74
D.5.1 Cipher key derivation as part of authentication.75
D.5.2 Static cipher key .75
D.6 User authentication.75
D.7 Key management in case of roaming .75
D.7.1 Introduction.75
D.7.2 Use of actual authentication key K.76
D.7.3 Use of session keys.77
D.7.4 Use of precalculated sets .78
Annex E (informative): Limitations of DECT security.79
ETSI
6 ETSI EN 300 175-7 V1.8.1 (2004-11)
E.1 Introduction.79
E.2 Protocol reflection attacks.79
E.3 Static cipher key and short Initial Vector (IV) .79
E.4 General considerations regarding key management.80
E.5 Use of a predictable challenge in FT authentication .80
Annex F (informative): Security features related to target networks.81
F.1 Introduction.81
F.1.1 Notation and DECT reference model .81
F.1.2 Significance of security features and intended usage within DECT.81
F.1.3 Mechanism/algorithm and process requirements .82
F.2 PSTN reference configurations .83
F.2.1 Domestic telephone.83
F.2.2 PBX.84
F.2.3 Local loop.85
F.3 ISDN reference configurations.86
F.3.1 Terminal equipment.86
F.3.2 Network termination 2.88
F.3.3 Local loop.88
F.4 X.25 reference configuration.88
F.4.1 Data Terminal Equipment (DTE).88
F.4.2 PAD equipment.88
F.5 GSM reference configuration.89
F.5.1 Base station substation .89
F.5.2 Mobile station.89
F.6 IEEE.802 reference configuration.89
F.6.1 Bridge.89
F.6.2 Gateway.89
F.7 Public access service reference configurations .89
F.7.1 Fixed public access service reference configuration .89
Annex G (informative): Compatibility of DECT and GSM authentication.90
G.1 Introduction.90
G.2 SIM and DAM functionality .90
G.3 Using an SIM for DECT authentication.91
G.4 Using a DAM for GSM authentication .91
Annex H (informative): DECT Standard Authentication Algorithm (DSAA) .93
Annex I (informative): Void 94
Annex J (informative): DECT Standard Cipher (DSC).95
Annex K (normative): Clarifications, bit mappings and examples for DSAA and DSC .96
K.1 Ambiguities concerning the DSAA.96
K.2 Ambiguities concerning the DSC DECT-standard cipher.97
Annex L (informative): Bibliography .99
Annex M (informative): Change history .100
History .101
ETSI
7 ETSI EN 300 175-7 V1.8.1 (2004-11)

Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by ETSI Project Digital Enhanced Cordless
Telecommunications (DECT).
The present document is part 7 of a multi-part deliverable. Full details of the entire series can be found in part 1 [1].
The following cryptographic algorithms are subject to controlled distribution:
a) DECT standard cryptographic algorithms;
b) DECT standard cipher.
These algorithms are distributed on an individual basis. Further information and details of the current distribution
procedures can be obtained from the ETSI Secretariat at the address on the first page of the present document.
Further details of the DECT system may be found in TR 101 178 and ETR 043 (see bibliography).

National transposition dates
Date of adoption of this EN: 12 November 2004
Date of latest announcement of this EN (doa): 28 February 2005
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 31 August 2005
Date of withdrawal of any conflicting National Standard (dow): 31 August 2005

Introduction
The present document contains a detailed specification of the security features which may be provided by DECT
systems. An overview of the processes required to provide all the features detailed in the present document is presented
in figure 1.
ETSI
8 ETSI EN 300 175-7 V1.8.1 (2004-11)
AC Authentication Code
IV Initialization Value obtained from frame counter
CK Cipher Key
SCK Static Cipher Key
Authentication
KS Session Authentication Key
UAK [128]
Key Selection
KS' Reverse Authentication Key
B2
UPI [e.g. 128]
RAND-F Value generated and transmitted by FP
RAND-P Value generated and transmitted by PP
RES 1 Value computed and transmitted by PP
RES 2 Value computed and transmitted by FP
RS Value transmitted by FP in authentication protocol
UAK [128]
B1
UAK User authentication Key
UPI User Personal Identity
DCK Derived Cipher Key
K Authentication Key
A11, A12 Authentication Processes
AC [e.g. 16-32]
B1
A21, A22 Authentication Processes
B1, B2 Authentication Key Stream Processes
K [128]
KSG Key Stream Generator
Authentication of
PP processes
RES1 [32]
A11
KS [128]
RS [64]
A12
RAND F [64] DCK
CK [64]
Key
SCK
SCK [64]
KSG
Stream
IV [35]
Key Stream generation
Authentication of
for encryption process
FP processes
A21
KS' [128]
A22 RES2 [32]
RAND P [64]
Figure 1: Overview of DECT security processes
The present document consists of four main clauses (clauses 4 to 7), together with a number of informative and
important annexes (A to K). The purpose of this introduction is to briefly preview the contents of each of the main
clauses and the supporting annexes.
Each of the main clauses starts with a description of its objectives and a summary of its contents. Clause 4 is concerned
with defining a security architecture for DECT. This architecture is defined in terms of the security services which may
be offered (see clause 4.2), the mechanisms which shall be used to provide these services (see clause 4.3), the security
parameters and keys required by the mechanisms (challenges, keys, etc.), and which shall be passed across the air
interface or held within DECT Portable Parts (PPs), Fixed Parts (FPs) or other network entities
(for example management centres) (see clause 4.4), the processes which are required to provide the security
mechanisms (see clause 4.5) and the recommended combinations of services (see clause 4.6).
Clause 5 is concerned with specifying how certain cryptographic algorithms are to be used for the security processes.
Two algorithms are required:
- a key stream generator; and
- an authentication algorithm.
The key stream generator is only used for the encryption process, and this process is specified in clause 4.4. The
authentication algorithm may be used to derive authentication session keys and cipher keys, and is the basis of the
authentication process itself. The way in which the authentication algorithm is to be used to derive authentication
session keys is specified in clause 5.2. The way in which the algorithm is to be used to provide the authentication
process and derive cipher keys is specified in clause 5.3.
Neither the key stream generator nor the authentication algorithm is specified in the present document. Only their input
and output parameters are defined. In principle, the security features may be provided by using appropriate proprietary
algorithms. The use of proprietary algorithms may, however, limit roaming in the public access service environment, as
well as the use of PPs in different environments.
ETSI
9 ETSI EN 300 175-7 V1.8.1 (2004-11)
For example, for performance reasons, the key stream generator will need to be implemented in hardware in PPs and
FPs. The use of proprietary generators will then limit the interoperability of systems provided by different
manufacturers.
Two standard algorithms have been specified. These are the DECT Standard Authentication Algorithm (DSAA,
see annex H) and the DECT Standard Cipher (DSC, see annex J).
Because of the confidential nature of the information contained in them, these annexes are not included in the present
document. However, the algorithms will be made available to DECT equipment manufacturers. The DSAA may also
need to be made available to public access service operators who, in turn, may need to make it available to
manufacturers of authentication modules.
Clause 6 is concerned with integrating the security features into the DECT system. Four aspects of integration are
considered. The first aspect is the association of user security parameters (in particular, authentication keys) with DECT
identities. This is the subject of clause 6.2. The second aspect of integration is the definition of the NWK layer protocol
elements and message types needed for the exchange of authentication parameters across the air interface. This is dealt
with in clause 6.3. The MAC layer procedures for the encryption of data passed over the air interface are the subject of
clause 6.4. Finally, clause 6.5 is concerned with security attributes which DECT systems may support, and the NWK
layer messages needed to enable PPs and FPs to identify which security algorithms and keys will be used to provide the
various security services.
Clause 7 is concerned with key management issues. Careful management of keys is fundamental to the effective
operation of a security system, and clause 7.2 is intended to provide guidance on this subject. The clause includes an
explanation of how the DECT security features may be supported by different key management options.
For example, schemes which allow authentication keys to be held in a central location within a public access service
network are described, as are schemes which allow authentication keys to be derived locally in public access service
base stations. The clause is very much less specific than the other clauses in the present document. This is because the
key management issues discussed are not an integral part of the CI. In the end it is up to network operators and service
providers to decide how they are going to manage their cryptographic keys. The present document can at best provide
some suggestions and guidelines.
The main text is supplemented by a set of informative annexes. There are two types of annex. Those of the first type
provide background information justifying the inclusion of a particular service, or the use of a particular type of
mechanism in the security features. Those of the second type provide guidance on the use and management of certain of
the security features. The content of each of the annexes is briefly reviewed below.
Annex A contains the results of a security threats analysis which was undertaken prior to designing the DECT security
features.
Annex B is concerned with the impact of the security features on roaming, in particular with the concurrent use of a PP
in public access service, wireless Private Branch eXchange (PBX) and residential environments.
Annex C is provided for background information. It contains a justification for some of the decisions taken by EG-1, for
example, why symmetric rather than public key (asymmetric) cryptographic mechanisms were selected.
Annex D provides an overview of the DECT security features specified in the present document.
No security system is perfect, and annex E discusses the limitations of the DECT security features.
Annex F relates the security features specified in the present document to the DECT environments identified in
TR 101 178 (see bibliography). Each of the local networks identified in the reference model is considered in turn. For
each of these networks a security profile is suggested. The networks considered are Public Switched Telephone
Network (PSTN), Integrated Services Digital Network (ISDN), ITU-T Recommendation X.25, Global System for
Mobile communications (GSM), Local Area Networks (LANs) and public access service.
Annex G consists of a brief discussion of the compatibility of DECT and GSM authentication. In
...