Specification of Crypto Driver, No.807, AUTOSAR R21-11(272) CP

Specification of Crypto Driver, No.807, 2021-11

https://www.autosar.org/fileadmin/standards/classic/21-11/AUTOSAR_SWS_CryptoDriver.pdf

AUTOSAR R21-11記事一覧はこちら。

AUTOSAR 21-11,160文書読んだ。2022年5月中に全部読み。

https://qiita.com/kaizen_nagoya/items/9935c9e58bf82e1e63d2

AUTOSAR 21-11, 62文書読んだ。2022年5月中に半分到達予定。

https://qiita.com/kaizen_nagoya/items/648b32867635993410c8

AUTOSAR R21-11(0) 仕様ダウンロード一覧。単語帳。参考文献資料作成

https://qiita.com/kaizen_nagoya/items/9b3a1b9b8d1e8d7e288e

# 用語(terms)
|Term|Description|
|:--|:--|
|CDD| Complex Device Driver
|CSM| Crypto Service Manager
|CRYIF| Crypto Interface
|CRYPTO| Crypto Driver
|DET |Default Error Tracer
|HSM| Hardware Security Module
|HW |Hardware
|SHE| Security Hardware Extension
|SW| Software
|Crypto Driver Object|A Crypto Driver implements one or more Crypto Driver Objects. The Crypto Driver Object can offer different crypto primitives in hardware or software. The Crypto Driver Objects of one Crypto Driver are independent of each other. There is only one workspace for each Crypto Driver Object (i.e. only one crypto primitive can be performed at the same time) The only exception of independency between Crypto Driver Object is the usage of a default Random Number Generator (see [SWS_Crypto_00225]).
|Key| A Key can be referenced by a job in the Csm. In the Crypto Driver, the key references a specific key type.
|Key Type| A key type consists of references to key elements. The key types are typically pre-configured by the vendor of the Crypto Driver.
|Key Element |Key elements are used to store data. This data can be e.g. key material or the IV needed for AES encryption. It can also be used to configure the behaviour of the key management functions.
|Channel| A channel is the path from a Crypto Service Manager queue via the Crypto Interface to a specific Crypto Driver Object.
|Job |A 'Job' is a configured 'CsmJob'. Among others, it refers to a key, a cryptographic primitive and a reference channel.
|Crypto Primitive |'Primitive' is an instance of a configured cryptographic algorithm realized in a Crypto Driver Object. Among others it refers to a functionality provided by the CSM to the application, the concrete underlining 'algorithmfamily' (e.g. AES, MD5, RSA, ...), and a 'algorithmmode' (e.g. ECB, CBC, ...).
|Operation |An operation of a crypto primitive declares what part of the crypto primitive shall be performed. There are three different operation  modes:It is also possible to perform more than one operation at once by concatenating the corresponding bits of the operation mode argument.
|START| Operation mode indicates a new request of a crypto  primitive, and it shall cancel all previous requests of the same job and primitive.
|UPDATE| Operation mode indicates, that the crypto primitive expects input data.
|FINISH |Operation mode indicates, that after this part all data are fed completely and the crypto primitive can finalize the calculations.
|Priority |The priority of a job defines the importance of it. The higher the priority (as well in value), the more immediate the job will be executed. The priority of a cryptographic job is part of the configuration.
|Service |A 'Service' shall be understood as defined in the TR_Glossary document: A service is a type of operation that has a published  specification of interface and behavior, involving a contract between the provider of the capability and the potential clients.

## 英日
日本語は仮訳

T.B.D.

# 参考(reference)

[1] AUTOSAR Layered Software Architecture
AUTOSAR_EXP_LayeredSoftwareArchitecture.pdf
[2] AUTOSAR General Requirements on Basic Software Modules
AUTOSAR_SRS_BSWGeneral.pdf
[3] AUTOSAR General Specification for Basic Software Modules
AUTOSAR_SWS_BSWGeneral.pdf
[4] AUTOSAR Specification of Crypto Interface
AUTOSAR_SWS_CryptoInterface.pdf
[5] AUTOSAR Specification of Crypto Service Manager
AUTOSAR_SWS_CryptoServiceManager.pdf
[6] AUTOSAR Requirements on Crypto Modules
AUTOSAR_SRS_CryptoStack.pdf
[7] AUTOSAR Specification of Secure Hardware Extension
AUTOSAR_TR_SecureHardwareExtension.pdf
[8] Glossary, AUTOSAR_TR_Glossary
https://www.autosar.org/fileadmin/standards/foundation/21-11/AUTOSAR_TR_Glossary.pdf
[9] Specification of the 3GPP Confidentiality and Integrity Algorithms 128-EEA3 & 128-EIA3: Document 1: 128-EEA3 and 128-EIA3 Specification, Version 1.7, 30th Dec 2011 Document 2: ZUC Specification, Version 1.6, 28th June 2011
[10] ISO/IEC 10118-3:2018 Part 3: Dedicated hash-functions (SM3)
[11] ISO/IEC 14888-3:2018 IT Security techniques — Digital signatures with appendix — Part 3: Discrete logarithm based mechanisms (SM2)
[12] IEC 7498-1 The Basic Model, IEC Norm, 1994