SNIP_CLASSIC_KEYM_SECTION_7_3_Custom_Handling

7.3 Custom Handling Incoming service requests to KeyM can be processed either locally on KeyM or alternatively on an adapted Crypto Driver (e.g. HSM). This is realized by linking KeyM service requests through custom CSM jobs and APIs to an adapted Crypto driver. The adapted Crypto driver may transfer the requests to HSM. This way the KeyM acts as a proxy and the certificate operations which are configured accordingly are processed completely in the crypto stack (e.g. HSM). The KeyM APIs remain the same, independently if the certificate is handled on KeyM locally or in the Crypto Driver. This has the advantage that serialization and deserialization of passed data is handled completely within Crypto Stack . To be able to execute the KeyM job as a custom crypto job, a mapping to an asynchronous or synchronous job processing at Csm is provided in a dedicated profile in Crypto (see SWS Crypto Driver Chapter 7.5.2 .<ref>). For KeyM synchronous functions like status requests the Csm_CustomSync function is used. The Crypto Driver profile also defines settings for it. [SWS_KeyM_00176] Upstream requirements: SRS_CryptoStack_00115, SRS_CryptoStack_00125 ⌈All certificates of a chain shall either by processed by KeyM locally or Csm Custom handling.⌋ [SWS_KeyM_00177] Upstream requirements: SRS_CryptoStack_00115, SRS_CryptoStack_00125 ⌈If the configuration container KeyMCertificateCustomService is included to the configuration of a certificate, the certificate submodule shall use the provided Csm Jobs and functions for custom processing (Csm_CustomService and Csm_CustomSync) using the reference definition KeyMCertCsmCustomJobRef.⌋