198
edits
Security Policy: Difference between revisions
→Specification of Services
| Line 410: | Line 410: | ||
The Crypto Officer role is assumed implicitly by invoking any installation or initialization service. For all other services the NSS User role needs to be explicitly assumed. | The Crypto Officer role is assumed implicitly by invoking any installation or initialization service. For all other services the NSS User role needs to be explicitly assumed. | ||
Routines have been specified for each service and denoted whether or not they are '''public''', meaning that the user doesn't need to authenticate to the module to use the routine, or '''NSS User''', meaning that the user needs to login to the module to use the routine. The following table lists the defined services and correlates role, service type and access to security-relavant information. | Routines have been specified for each service and denoted whether or not they are '''public''', meaning that the user doesn't need to authenticate to the module to use the routine, or '''NSS User''', meaning that the user needs to login to the module to use the routine. The following table lists the defined services and correlates role, service type and access to security-relavant information. Access type is Read, Write, Zeroize. | ||
<table border="1"> | <table border="1"> | ||