Security Policy: Difference between revisions

Security Policy (view source)

127 bytes removed , 18 August 2006

198

edits

@@ Line 373: / Line 373: @@
 ==Specification of Services==
-Since there is only one role, the user has access to '''ALL''' the services. 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 '''private''', meaning that the user needs to authenticate to the module to use the routine. This model allows a type of '''safety state''' by allowing a NSS user to log out (thus disallowing any access to private services) without ending the session, and then log back in to re-authenticate and access private services rendered by the cryptographic module. All public and private services are listed in the following table:
+The Crypto officer role is entered implicitly by invoking any installation or initialization service. For all other services the User role is 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 cryptographically significant resources.
 <table border="1">