Four level login security (assuming the room itself has no forms of identification security before letting the person in the room, and assuming local login capability):

1. Login code first process would require an retina scan to verify they are someone authorized to use the computer. Without this scan, the computer will not complete the booting process, because the BIOS itself calls upon a security check for the scan. If the retina scan is removed, there is no confirmation and logging process. Consider this a BIOS boot level check with the ability for it to check a network database. There is a 15 second security reset. If the scanner is not used within fifteen seconds then the computer is shutdown again and the event is logged. If a scanner receives incorrect information 3 times in a row, the computer is shutdown again and a "BIOS lock" begins which locks the actual BIOS from booting, and the event is logged.

2. Login code second process, after confirming the retina, would be a biometric confirmation for the operating system to load. Fingerprint authentication would be required during the booting process of the Operating System kernel, meaning only the drivers for the biometric scanner and base OS files (for database checking of the fingerprint) are loaded at this time. The system then halts until a successful match is made and when made the rest of the operating system loads as normal. There is a ten second confirmation match on the fingerprint authentication, and if that time is exceeded the system will shutdown and log the event. There is a three time error policy, in which if the fingerprint authentication is failed three times in a row the system will shutdown and preform a "BIOS lock" (see #1).

3. After those two levels of authentation we have the run of the mill password system. The system itself is encrypted (save /boot) and a passphrase is used to decrypt the system for loading (think pgp for entire partitions). The encryption itself is on 4096 bits and requires an actual passphrase (minumim fifteen words) to decrypt. Once the correct passphrase is inputted through the keyboard the decryption process will begin and the operating system will be loaded. However, there is a 15 second period in which the password must be inputted or face a system shutdown. There is also a three trial attempt on the password, in whichcase if the password fails a third time then an alarm goes off (now that basic OS drivers are loaded we could actually use networking) which results in the system shutting down and preforming a "Bios lock" (see #1) and the event being logged.

4. Have this only be terminal access and have the actual physical server locked up as should be elsewhere. The harddisk is partitioned as needed (usually /home /boot /bin , etc etc etc) and have appropriate read-only permissions set per partitions.



Of course, this could be done both on Windows and Linux, and while it isn't foolproof, there's a base idea we could work with.