Tools
Sorted by:
Try your query at:
 |
 |
 |
 |
 |
 |
Results 1 - 10
of
4,945
Table 1. Security Requirements related to message authentication, integrity, confidentiality and authorization.
Table 1. Comparison of three scenarios for multi-authored authenticated dictionaries. All bounds are asymptotic, with the big-Oh omitted to simplify the notation
2003
Cited by 9
Table 3: GSSAPI Authentication Authentication Time Minimum Maximum Average
"... In PAGE 5: ... This allowed us to draw the maximum achievable band- width using parallel streams. The time taken for Grid server authentication and authorization was measured separately over number of runs to compare the Grid security implemen- tations of MyCoG and Java CoG, as shown in Table3 . The X.... ..."
Table 5: Authentication Methods for authentication service
"... In PAGE 2: ... For task minimum authentication security level required is 0.2 and this is compared with security level and corresponding overhead given in Table5 . Incase security requirement does not directly match with table value next higher security level is being considered.... In PAGE 5: ... The authentication service insured that all task must be submitted by authorized users. Three authentication methods are used in paper which is shown in Table5 where each authentication method is assigned a security level value. Security level of a required authentication method (other than given in table 4) can be calculated using equation 5.... In PAGE 9: ... These results are shown in the table 5. Table5 : Feasibility analysis after improvement phase with modified approach Task Authentication overhead(security value) Confidentiality overhead(security value) Integrity overhead(security value) Finish time ( +Overhead+ wi ) Deadli ne 90(0.2) 5.... ..."
Table 1. Number of authentications required by the system in a working week.
"... In PAGE 7: ... First, we would like to show some measures about the number of explicit authentications that must be performed in a Plan B desktop formed by three terminals and three large displays controlled by Omero. Table1 shows the num- ber of explicit authentications required by the author in a... ..."
TABLE 6. The Administrator must always be available (AVA01). The framework must assure basic delivery properties such as: messages must be delivered at least once (REL01) and must be delivered in a sequence (REL02). Two security requirements are: authentication (SEC01) and authorization (SEC02). Authentication ensures that the access to data is restricted to those who can provide a proof of identity. Authorization decides whether an entity can access a particular resource. Both are assured by the earlier functional requirements. Scalability allows increasing total throughput under an increased load when new resources are added. For instance, a system is scalable if registering new members does not increase the time for sending messages (SCA01).
2007
Table 4 - Authentication Mechanisms Cross-Comparison
2006
"... In PAGE 8: ...able 3 - SP800-63 Token Mappings to OMB M-04-04 Assurance Levels ................................ 15 Table4 - Authentication Mechanisms Cross-Comparison .... In PAGE 23: ... Each authentication method has strengths and weakness. Table4 below summarizes at a very high level some of the relative strengths (blue) and weakness (pink) for four method categories against nine areas of comparison [1]. NOTE: With the permission of the original author, the descriptions in the table have been modified slightly to align with the purpose of the report.... In PAGE 65: ... 7.5 Entropy / Strength of Function Section 5 (in particular Table4 ) of this document introduced a comparative analysis of authentication mechanisms based on characteristics ranging from technical to procedural; this section discusses entropy and strength of function which is a common characteristic used in comparing secrets based and cryptographic authentication mechanisms. Appendix A of the NIST Special Publication 800-63 provides a discussion on the entropy and strength of passwords.... ..."
Table 1. Classification of authentication amp; access control policies
"... In PAGE 2: ... - Authentication level assignment (ID amp; password, smart card/security token, biometrics, multi-modal) - Authorization and access control level assignment (location restriction, time limit, duration limit) - Confidentiality level assignment (data encryption, data signature, virtual private network) To develop systems, which provide context-aware services, flexible authentication and access control policies should be implemented. Table1 indicates examples of the policies we have developed for the context-aware policy engine in the authentication and access control agent framework. Table 1.... ..."
Table 2. Technologies for achieving Security Requirements Security Requirement Technique Used Authorization Passwords, Access Control List (ACL), Firewall Authentication Shared Secret, Public Key Infrastructure (PKI), Digital signatures, Digital certificates Privacy (Partially by) Encryptions, Mechanisms to hide locations and Routing protocols used Data Confidentiality Encryption
"... In PAGE 4: ...3). Table2 shows examples of some of these technologies. These technologies could be applied to achieve the objectives of the security requirements in the relations from (1) to (7).... ..."
Table 1 Access matrix of the authorization model
"... In PAGE 5: ...509v3 certin0ccate presented from the client when the protected document is requested. Table1 shows the main elements of our authentica- tion scheme in terms of access matrix model n28Ford 1994n29. The user identity is related to the subject n0celd of the client certin0ccate and can be mapped over one or more authentication roles, that are the handlers that identify a single certin0ccate n28or a group of themn29 inside the ACL.... ..."
Results 1 - 10
of
4,945
