Access conditions

Description

Access conditions are a set of security attributes associated with a file in a smart card or Universal Integrated Circuit Card (UICC). They define the conditions under which the file can be accessed, read, updated, or otherwise manipulated. These conditions are specified in 3GPP specifications such as TS 21.905 and TS 31.121, which cover the UICC and its applications. Access conditions are crucial for ensuring the security and integrity of data stored on the UICC, such as subscriber credentials, phonebook entries, and network parameters.

In the context of the UICC, files are organized in a hierarchical file system. Each file has a set of access conditions that specify the required security level for various operations. For example, a file might be readable by anyone but only writable by the network operator after authentication. The access conditions are typically defined in the file's header or in a separate access control list. They can include conditions such as 'always' (no restriction), 'never' (no access), 'PIN protected', 'ADM protected' (administrative access), or 'network protected' (requires authentication with the network).

The access conditions are enforced by the UICC's operating system when an application or terminal attempts to access a file. If the required conditions are not met, the access is denied, and an error is returned. This mechanism prevents unauthorized access to sensitive data and ensures that only authorized entities can modify critical parameters. For instance, the IMSI (International Mobile Subscriber Identity) is stored in a file that is typically read-protected and only accessible to the network after authentication.

Access conditions are also used in the context of Over-the-Air (OTA) provisioning, where the network operator can update files on the UICC remotely. The access conditions ensure that only the operator with the correct keys can perform such updates. This is essential for maintaining the security of the UICC and preventing fraud.

The concept of access conditions has been part of 3GPP specifications since Release 4 and has remained largely unchanged. The definition is concise: 'A set of security attributes associated with a file.' This stability reflects the fundamental nature of access control in smart cards, which has not required significant changes over the years. However, the specific access conditions and their encoding may be detailed in other specifications, such as TS 31.101 and TS 31.102, which define the UICC file system and its access conditions.

Purpose & Motivation

Access conditions exist to provide a security mechanism for controlling access to files stored on a UICC or smart card. In the context of mobile networks, the UICC holds sensitive information such as the IMSI, authentication keys, and subscriber data. Unauthorized access to these files could lead to identity theft, fraud, or network disruption. Access conditions ensure that only entities with the appropriate privileges (e.g., the network operator, the user with a PIN, or the card issuer) can read or modify the files.

Historically, as smart cards became more prevalent in mobile communications, the need for a standardized way to define and enforce access control became apparent. The 3GPP specifications defined access conditions to provide a common framework that all UICC manufacturers and terminal vendors could follow. This ensures interoperability and security across different networks and devices.

The access conditions address the limitation of having no access control, which would leave the UICC vulnerable to attacks. They also provide flexibility by allowing different files to have different security requirements. For example, a phonebook file might be accessible to the user after entering a PIN, while the authentication keys are only accessible to the network. This granularity is essential for balancing usability and security. The concept has been stable since its introduction, demonstrating its effectiveness and the maturity of the UICC security architecture.