Assuming an unauthorised person is able to physically access a PC, how can you prevent him or her from also gaining access to the data located on or through that PC? This is the primary role of authentication security, the methods by which we validate that the person at the keyboard has permission to use that computer. Exactly how this is achieved depends on the desktop and network operating system, but certain security measures can be implemented in most environments, such as:
- Boot/power on passwords set in the BIOS.
- Network/Desktop logon name/password.
- Biometric devices for logon, such as thumb print or retinal scanners.
- Access tokens.
- Screen saver passwords.
- Setting passwords on individual files/folders/applications
- Restricting access times/days on the computer
- Forcing logout after X minutes of idle time
- Locating all data on network drives to prevent data being stolen if the PC is stolen
- Restricting access to removable media to prevent data theft
- Clearing page table on shutdown/reboot
This final action can be conveniently broken down into the following tasks:
- Decide how to implement the policy (i.e., can it be implemented with your organisation's current desktop and server OS? If not, should one or both of the operating systems be changed or should third-party software be purchased?).
- Assign responsibility. Who in the company is responsible for enforcement of what parts of the policy (i.e., who is responsible for initiating action if a user shares his or her password?)?
- Clearly define penalties for violation of the policy (i.e., what are the consequences of letting your mother-in-law borrow your notebook for the weekend?).
- Educate the users (i.e., what changes should they expect, what are their responsibilities, what are the consequences for violations?).
- Establish a procedure/schedule for reviewing the policy.






