T/ZISIA 0102.2-2025 Active Group standards

T/ZISIA 0102.2-2025 General purpose operating system commercial cryptographic subsystem function calling interface specification Part 2:User mode interface

Publish Date: 2025-12-31 Implement Date: 2025-12-31 For services related to genuine standard inquiry, procurement, translation, and other related services in China, please Contact Us

Price: $ 20.00

Out of stock

Basic Information

Standard Code: T/ZISIA 0102.2-2025

Standard Type: Group standards

Standard Status: Active

is_force_gb: no

CCS Name: -

ICS Name: Comprehensive Application of Information Technology

Publish Date: 2025-12-31

Implement Date: 2025-12-31

Scope

This standard is divided into two parts: Part 1: Kernel-State Interface; Part 2: User-State Interface. 1. Password Function Call Interface Framework It standardizes the kernel-state and user-state password functions of the OS commercial cryptography subsystem, including kernel-state and user-state APIs (northbound interface) and kernel-state and user-state commercial cryptography resource hooking interfaces (southbound interface). 2. Data Type Definition It defines password algorithm identifiers, basic data types, and data structures. 3. Commercial Cryptography Function Call APIs It defines OS commercial cryptography kernel-state and user-state APIs (northbound interface), including interface functions for asymmetric algorithms, symmetric algorithms, and hashing algorithms. 4. Commercial Cryptography Resource Hooking Interface It defines the Engine mechanism of the commercial cryptography subsystem. New commercial cryptography resources can be extended or replaced with the cryptographic algorithms of the commercial cryptography subsystem through the Engine mechanism, achieving the hooking of commercial cryptography resources with the OS commercial cryptography subsystem. The hooked cryptographic resources can be either software cryptographic modules or cryptographic hardware. 5. Example of the Engine Interface for Commercial Cryptography Resources It provides an example for cryptographic resource developers to develop cryptographic resource engines using the kernel-state and user-state hooking interfaces of OS commercial cryptography.