Abstract: Additional security is provided for users by implementing a module that notifies an account holder when the account is accessed to change in password, logout or lock the account via notifications to smartphone apps, browser plugin, etc. User can use mobile apps or browser plugin from any device to immediately stop the access by logging out the user from the already logged in systems, lock the user account, or change the password.

Abstract: Additional security is provided for users by implementing a module that notifies an account holder when the account is accessed to change in password, logout or lock the account via notifications to smartphone apps, browser plugin, etc. User can use mobile apps or browser plugin from any device to immediately stop the access by logging out the user from the already logged in systems, lock the user account, or change the password.

Abstract: Additional security is provided for users by implementing a module that notifies an account holder when the account is accessed to change in password, logout or lock the account via notifications to smartphone apps, browser plugin, etc. User can use mobile apps or browser plugin from any device to immediately stop the access by logging out the user from the already logged in systems, lock the user account, or change the password.

Abstract: The invention includes a method and apparatus for preventing phishing attacks. A first method, for informing a user that a remote server is valid, remote server sends the dynamic identifier to the system (client) and token app, then user validates and confirms whether the dynamic identifier matches between the system and the token app. The server receives, validates the confirmation and proceed with user authentication in the system. A second method, remote server and token app receives the dynamic identifier from the third party token provider. Remote server displays the dynamic identifier in the system. Token provider validates the entity of the remote server and displays that verified information in the token app along with dynamic identifier. Then user validates and confirms whether the dynamic identifier matches between the system and the token app. The token server receives, validates the confirmation and sends message to the entity server to proceed with user authentication in the system.