Reference Guide

16 Crypto-C ME Cryptographic Toolkit
RSA BSAFE Crypto-C Micro Edition 4.1.4 Security Policy Level 1
1.3 Roles, Services and Authentication
Crypto-C ME meets all FIPS 140-2 Level 1 requirements for roles services and
authentication, implementing both a Crypto User role and Crypto Officer role. As
allowed by FIPS 140-2, Crypto-C ME does not support user identification or
authentication for these roles. Only one role can be active at a time and Crypto-C ME
does not allow concurrent operators. After loading, the cryptographic module is
implicitly in the Crypto User role.
1.3.1 Crypto Officer Role
The Crypto Officer is responsible for installing and loading the cryptographic module.
After the module is installed and operational, an operator can assume the Crypto
Officer role by calling
R_PROV_FIPS140_assume_role() with
R_FIPS140_ROLE_OFFICER.
An operator assuming the Crypto Officer role can:
• Perform the full set of self tests.
• Call any Crypto-C ME function. For a complete list of functions available to the
Crypto Officer, see Services.
1.3.2 Crypto User Role
A Crypto Officer can assume the Crypto User role by calling
R_PROV_FIPS140_assume_role() with R_FIPS140_ROLE_USER.
An operator assuming the Crypto User role can use the entire Crypto-C ME API
except for
R_PROV_FIPS140_self_tests_full(), which is reserved for the
Crypto Officer. For a complete list of Crypto-C ME functions, see Services.