|
|
| Common Data Security Architecture (CDSA) White Paper |
|
|
| Introduction to |
|
|
|
|
|
|
| Introduction to |
|
|
|
|
NOTE |
|
| This section provides a conceptual overview of CDSA |
|
|
| For a summary of how to create an |
|
|
| CDSA |
|
|
| For information on credentials required for any CSP |
|
|
| “Validating the CSP Credentials” on page 65 and “HP Signing Policy for |
|
|
| CSP |
|
|
|
|
The Role of Add-In Modules in the CDSA Framework
In
By convention, the
The CSSM acts as a “broker” between applications and
An application derives information about
The first time the module is attached, CSSM calls the module’s Initialize function to allow the module to perform initialization operations.
When CSSM attaches to a module service, it returns a module handle to the application that uniquely identifies the pairing of the application thread to the module service instance. The application uses this handle to identify the module service in future function calls. The module service uses the handle to identify the calling application.
During the initialization process, if the module is a CSP, it undergoes a series of integrity checks, including a bilateral authentication protocol to ensure the integrity of the CSSM, as part of CSSM_ModuleAttach. This verification must succeed for a CSP module to attach to CSSM.
Once the integrity of a CSP module is verified, the
CSSM_RegisterServices to register a function table with CSSM for each
48 | Chapter 1 |