[ad_1]
The Security Accounts Manager in Windows verifies account passwords by encrypting them with a hashing algorithm. It is integrated into the system registry and monitored by the kernel for security. However, there are still ways to trick the system, such as through virtual systems or computer errors.
Security Accounts Manager is the part of the Windows® operating system that verifies account passwords. The passwords stored by this system are encrypted using a hashing algorithm. Because the hash only encodes in one direction, passwords are relatively secure if found by an unauthorized user. The Security Account Manager is integrated into the system registry and its files are directly monitored by the kernel, making it difficult to tamper with or change the associated information. While this system is safe from most basic attacks, it has received several criticisms due to a select group of security flaws.
The main function of Security Accounts Manager is to store the passwords used to access Windows® accounts. This system contains only those passwords; other system passwords are stored in unrelated areas. The manager is used by the operating system to verify that the entered passwords are the correct ones.
When a user creates an account password, the system sends it via a hashing algorithm. This process converts the password into numbers and then runs those numbers through an equation. The output of the equation is a string of numbers that bears no resemblance to the original password. Windows will completely remove all traces of the original password, leaving only the numbers.
When a user enters his password, the process repeats. The Security Account Manager contains the final string of numbers, which are compared to the converted password. If the numbers match, the user can log in; otherwise, the system returns an invalid password error.
Security for the Security Account Manager is as tight as it gets. The processes that govern the system are integrated directly into the registry of the operating system. This is common for most intrinsic systems, but makes them more difficult to tamper with. True security comes from the kernel of the system. As soon as the kernel is activated, it takes possession of the Security Accounts Manager files and keeps them for as long as it is running. This makes moving or copying files extremely difficult.
The system is not infallible, and there are many ways to trick the kernel into giving up files. The most common methods involve mounting the Windows® installation on a virtual system. The kernel is easier to check during emulation and you can copy files. It’s also possible to cause a computer error, commonly called a blue screen, that dumps active memory into a file. This dump contains the Security Accounts Manager information.
