2. Security and authentication
3. Methods of verification
a. Psychological verification
i. Finger Print.
ii. Hand Print.
iii. Face Measurement.
iv. Retinal Scanning.
v. DNA Analysis.
b. Behavioral verification
8. ...view middle of the document...
It relies on the users special item -token like card-id.
2.Secret based security:
It relies on an individual secret id number like password.
Neither of the two can accurately determine whether the password that posses a token nor knows some secret information of the individual it represents. Tokens can be stolen and information can be guessed or fraudulently obtained.
Biometric is a technology where the password for entry is you, which identifies your psychological and behavioral characteristics.
Security and Authentication
Web-Based Enterprise Management (WBEM) supports a limited form of security for the Microsoft® Windows® 98 platform that involves validating a user's logon for the local machine and for remote access. A validated user is granted access to the entire Common Information Model (CIM) schema. WBEM does not secure system resources, such as individual classes, instances, and namespaces. Security is limited because Windows 98 is not a secure operating system and does not support file system or registry security.
All security-related information is represented by instances of WBEM system classes located in the Root\Security namespace. These classes and instances can only appear in the Root\Security namespace and must remain there permanently.
The WBEM Administrator application can be used to set permissions for WBEM users. It is similar to the User Manager application supplied with Microsoft® Windows NT®.
In WBEM, all security accounts are referred to as subjects. There are two types of subjects: user and group. Users are represented by instances of the NTLMUser system class, which describes individual users. Groups are represented by instances of the NTLMGroup system class, which describes multiple users. Both the NTLMUser and NTLMGroup classes derive indirectly from the subject system class, an abstract class that is not intended to be used for instantiation. More directly, NTLMUser derives from the generic User class and NTLMGroup derives from the generic Group class.
Microsoft SQL Server uses permissions to enforce database security. The SQL Server permissions system specifies which users are authorized to use which Transact-SQL statements, views, and stored procedures. The
ability to assign permissions is determined by each user's status (as SA, database owner, or database object owner). Permissions are set on database users or groups, not on login IDs.
SQL Server's permissions system recognizes four types of users: the SA, database owners, database object owners, and other users of the database.
The different types of users exist in a hierarchy (explained in the following sections and illustrated below).
Only the SA and database owners can grant statement permissions to other users.
Different Security Mechanisms:
To help you understand the...