198
edits
Security Policy: Difference between revisions
m
→Specification of Services
| Line 410: | Line 410: | ||
The Crypto Officer role is assumed implicitly during installation of the module. The NSS User role is entered by authenticating, or logging in, to the module. Some services require the user to assume the NSS User role. Other services do not impose any role requirement. | The Crypto Officer role is assumed implicitly during installation of the module. The NSS User role is entered by authenticating, or logging in, to the module. Some services require the user to assume the NSS User role. Other services do not impose any role requirement. | ||
Each service is provided by a PKCS #11 function. The following table lists the defined services and correlates role, service type and type of access to security- | Each service is provided by a PKCS #11 function. The following table lists the defined services and correlates role, service type and type of access to security-relevant information. Access type is Read/Write/Zeroize. | ||
<table style="width: 944px; height: 2066px;" border="1"> | <table style="width: 944px; height: 2066px;" border="1"> | ||
| Line 419: | Line 419: | ||
Category</b></font></font></p> | Category</b></font></font></p> | ||
</td> | </td> | ||
<td style="text-align: center; font-weight: bold;"><font | <td | ||
style="text-align: center; font-weight: bold;"> | |||
<p><font face="Palatino"><font size="2"><b>Role</b></font></font></p> | |||
</td> | |||
<td | <td | ||
style="text-align: center; vertical-align: middle; width: 155px;"> | style="text-align: center; vertical-align: middle; width: 155px;"> | ||