Reference Guide

Crypto-C ME Cryptographic Toolkit 13
RSA BSAFE Crypto-C Micro Edition 4.1 Security Policy
Level 1
The underlying logical interface to Crypto-C ME is the API, documented in the RSA
BSAFE Crypto-C Micro Edition API Reference Guide
. Crypto-C ME provides for
Control Input through the API calls. Data Input and Output are provided in the variables
passed with the API calls, and Status Output is provided through the returns and error
codes documented for each call. This is illustrated in the following diagram.
Figure 1 Crypto-C ME Logical Interfaces
Note: Shared libraries for systems running a Mac OS X or iOS operating
system might include Apple code signatures applied by customers. If such a
signature is present, the signature is not included in the logical boundary and
is explicitly excluded from the software signature check.
Master shared library: cryptocme
Cryptographic Boundary
Application
Data In Data Out Control In Status Out
Resource shared libraries:
ccme_base ccme_base_non_fips ccme_ecdrbg
Operating System (OS)
Hardware
Software - Runs on Hardware
Hardware
Run on OS
Provides services for OS
Provides
services
for toolkit
Signature files:
cryptocme.sig
and
cryptocme_test_on_use.sig
Logical Boundary
ccme_ecc_non_fips ccme_ecc_accel_fips ccme_ecc_accel_non_fips
ccme_ecc
ccme_error_info
ccme_asym ccme_aux_entropy