Sign In |Help & Support
ALL SECTORS
  • ALL SECTORS
  • GB(National Standard)
  • CB(Shipping)
  • CECS(Engineering Construction)
  • CJ(Urban Construction)
  • CY(News and Publication)
  • DB(Provincial Standard)
  • DL(Electricity & Power)
  • DZ(Geology & Mineralogy)
  • FZ(Spinning & Textile)
  • GA(Public Security)
  • HB(Aviation)
  • HG(Chemical Industry)
  • HJ(Environmental Protection)
  • JB(Machinery)
  • JC(Building Materials)
  • JG(Building & Construction)
  • JJ(Metering)
  • JT(Highway & Transportation)
  • LY(Forestry)
  • MT(Coal)
  • NB(Energy)
  • NY(Agriculture)
  • QB(Light Industry)
  • QC(Automobile & Vehicle)
  • QJ(Aerospace)
  • SH(Petrochemical)
  • SJ(Electronics)
  • SL(Water Resources)
  • SN(Commodity Inspection)
  • SY(Oil & Gas)
  • TB(Railway & Train)
  • YB(Ferrous Metallurgy)
  • YC(Tobacco)
  • YD(Telecommunication)
  • YY(Medical Device)
Database: 365,228(8 Aug 2026)
orthoses medium power gas converter station introductionthe document
GB/T 36322-2018 in English

GB/T 36322-2018 in English

VALID

Information security technology-Cryptographic device application interface specifications

  • Issued on:2018-06-07
  • Implemented on:2019-01-01
  • File Format:PDF
  • Delivery:Via email within 5 business days
Price(USD): $610.00
$592.00
Standard No: GB/T 36322-2018
Document status: VALID
Title in English: Information security technology-Cryptographic device application interface specifications
Title in Chinese: 信息安全技术 密码设备应用接口规范
Language: English
File Format: Electronic (PDF)
Delivery: Via email within 5 business days
Issued on: 2018-06-07
Implemented on: 2019-01-01
ICS Classification: 35.040-Character sets and information coding
Professional Classification: GB-National Standard
Related Topics: password
code device
GB/T 36322-2018
GBT36322
GB/T 36322-2018
Instructions for use of safety interlocking equipment
gb/t 36322

《GB/T 36322-2018信息安全技术 密码设备应用接口规范》由TC260(全国网络安全标准化技术委员会)归口,主管部门为国家标准化管理委员会。


Introduction

Technical Architecture of Cryptographic Device Interface Specification

Technical LevelFunctional ModuleTypical Implementation
Device Management Layer Session Management/Random Number Generation/Access Control SDF_OpenSession/SDF_GenerateRandom
Key Management Layer Key Generation/Import and Export/Digital Envelope SDF_GenerateKeyPair_ECC/SDF_ExchangeDigitEnvelope
Algorithm Operation Layer Signature Verification/Encryption/Decryption/MAC Calculation SDF_InternalSign_ECC/SDF_CalculateMAC

Core Data Structure Analysis

ECC Key Structure Example

typedef struct ECCrefPublicKey_st { ULONG bits; // Key bit length BYTE x[ECCref_MAX_LEN]; // Public key x coordinate BYTE y[ECCref_MAX_LEN]; // Public key y coordinate } ECCrefPublicKey;

The standard clearly defines the algorithm identifiers that cryptographic devices need to support:

  • SM2: National Secret Elliptic Curve Algorithm (identification value 0x00000101)
  • SSL key negotiation SDF_GenerateKeywithECDHE_SSL → SDF_Encrypt SM2 key exchange + SM4 encryption Digital signature SDF_HashInit → SDF_HashUpdate → SDF_InternalSign_ECC SM3 hash + SM2 signature

    Implementation suggestions

    1. Key lifecycle management: The device key needs to be implanted during initialization, and the user key is dynamically generated through the management tool
    2. Error handling mechanism: The 28 error codes defined in Appendix A need to be fully implemented (such as SDR_SKOPERR indicates private key operation failure)
    3. Performance optimization: For high-frequency operations such as SDF_Encrypt, it is recommended to use a session multiplexing mechanism

    Standard evolution analysis

    Compared with the previous version of the standard, the 2018 version has the following major enhancements:

    • Added support for the SM9 algorithm (needs to be used with GB/T 35276)
    • Improved the ECC digital envelope conversion process
    • Refined the IPSec/SSL key derivation parameter requirements

Sample only — not a preview of GB/T 36322-2018
Page: 1 / 0
100%

Loading PDF document...

Error loading PDF. Please make sure the file is valid and try again.

We also recommend