Card Life Cycle

The Java Card life cycle describes the various states that a Java Card can go through during its usage. These states are as follows:

• OP_READY: This is the initial state of the Java Card after it is powered on. In this state, the runtime environment shall be available and the Issuer Security Domain, acting as the selected Application, shall be ready to receive, execute and respond to APDU commands from the card reader.
  The following functionality shall be present when the card is in the state OP_READY:
  • The runtime environment shall be ready for execution.
  • The OPEN shall be ready for execution.
  • The Issuer Security Domain shall be the implicitly selected Application for all card interfaces.
  • Executable Load Files that were included in Immutable Persistent Memory shall be registered in the GlobalPlatform Registry.
  • An initial key shall be available within the Issuer Security Domain
• INITIALIZED: In this state, the Java Card has been initialized by the application and is ready to execute the code that has been loaded onto it. This state indicates that the card has passed its self-tests and is functioning properly. The state INITIALIZED is an administrative card production state. The state transition from OP_READY to INITIALIZED is irreversible. Its functionality is beyond the scope of this Specification. This state may be used to indicate that some initial data has been populated (e.g. Issuer Security Domain keys and/or data) but that the card is not yet ready to be issued to the Cardholder.
• SECURE: In this state, the Java Card has been authenticated and is in a secure mode. This state is typically reached after a successful mutual authentication between the card and the card reader, and indicates that the card is ready to perform secure operations. The state SECURED is the intended operating card Life Cycle State in Post-Issuance. This state may be used by Security Domains and Applications to enforce their respective security policies. The state transition from INITIALIZED to SECURED is irreversible. The SECURED state should be used to indicate to off-card entities that the Issuer Security Domain contains all necessary keys and security elements for full functionality.
• CARD_LOCKED: In this state, the Java Card has been locked due to multiple incorrect authentication attempts. In order to unlock the card, a specific PIN or other authentication mechanism must be used. Setting the card to this state means that the card shall only allow selection of the application with the Final Application privilege
• TERMINATED: This is the final state of the Java Card, indicating that the card has been permanently disabled or destroyed. This state can be reached due to various reasons, such as expiration of the card, physical damage, or deliberate destruction.

The Java Card life cycle is an important concept in smart card technology, as it helps ensure that the card is secure and functioning properly throughout its usage. The card reader and the application on the card typically monitor the life cycle of the Java Card to ensure that it is being used appropriately and securely.

The card Life Cycle States OP_READY and INITIALIZED are intended for use during the Pre-Issuance phases of the card’s life.

The states SECURED, CARD_LOCKED, and TERMINATED are intended for use during the Post-Issuance phase of the card although it is possible to terminate the card at any point during its life.

AM SD: Security Domain with Authorized Management privilege
DM SD: Security Domain with Delegated Management privilege
SD: Other Security Domain
X: Support required
Blank cell: Support optional or prohibited

NOTE: If an SD does have the Final Application privilege, it may be selected and process the SELECT command in the CARD_LOCKED life cycle state. Otherwise, it may not be selected; however, it may be able to process commands received and internally forwarded to it through a trusted framework.