A computer implemented method to prevent attacks against authorization systems, wherein a second server, in connection with a computing device of a user, via a second dedicated program installed in said computing device, is used to manage a status of the accounts the user has in a first server and a status of the operations defined for a particular account, said account status and said operation status being set, whenever the user wants, as valid or as invalid by the user via the second dedicated program and stored in a memory of the second server, and said account status and said operation status being set by the user once a pairing process with the second server being completed, said pairing process ensuring privacy to the user, the method comprising: - receiving, by said first server, from the user using a first dedicated program including a browser, a request to be logged into a service of said first server, said request including the provision of identification information validating the identity of the user in the first server; - once user existence has been validated by the first server, receiving, by said second server, from said first server, a request about a status regarding an account of the user in the first server; - in response to receiving the request, initializing a first credential exchange between said first server and said second server in order to provide mutual authentication, the first credential exchange being performed via an authentication procedure based on certificates' exchange; - verifying, by the second server, said account status; - sending, by said second server, said account status to said first server; and - using, by said first server, said received account status for: ∘ authorizing said service login request if said account status is set as valid, or ∘ rejecting said service login request if said account status is set as invalid, wherein in response to said service login request being authorized, a further request is done by the user via the first dedicated program to perform an operation related to said account of the user in the first server, the method further comprises following steps: - determining, by the first server, what entry in a scheme of an hierarchy defined by said account corresponds with said requested operation; - associating, either by the first server or by the user via the second dedicated program, at least a hardware token such as a Near Field Communication, NFC, card to said requested operation to prevent Card Not Present, CNP, fraud; - requesting, by said first server, to said second server, the operation status defined by the user over said entry; - initializing a second credential exchange between the first server and the second server; - evaluating, by the second server, a scheme entry status information from a root of said hierarchy scheme to said entry; - sending, by the second server, the result of said scheme entry status information evaluation to the first server, and - using, by the first server, the result of said evaluation for allowing or blocking said requested operation. - receiving, by said first server, from the user using a first dedicated program including a browser, a request to be logged into a service of said first server, said request including the provision of identification information validating the identity of the user in the first server; - once user existence has been validated by the first server, receiving, by said second server, from said first server, a request about a status regarding an account of the user in the first server; - in response to receiving the request, initializing a first credential exchange between said first server and said second server in order to provide mutual authentication, the first credential exchange being performed via an authentication procedure based on certificates' exchange; - verifying, by the second server, said account status; - sending, by said second server, said account status to said first server; and - using, by said first server, said received account status for: ∘ authorizing said service login request if said account status is set as valid, or ∘ rejecting said service login request if said account status is set as invalid, ∘ authorizing said service login request if said account status is set as valid, or ∘ rejecting said service login request if said account status is set as invalid, - determining, by the first server, what entry in a scheme of an hierarchy defined by said account corresponds with said requested operation; - associating, either by the first server or by the user via the second dedicated program, at least a hardware token such as a Near Field Communication, NFC, card to said requested operation to prevent Card Not Present, CNP, fraud; - requesting, by said first server, to said second server, the operation status defined by the user over said entry; - initializing a second credential exchange between the first server and the second server; - evaluating, by the second server, a scheme entry status information from a root of said hierarchy scheme to said entry; - sending, by the second server, the result of said scheme entry status information evaluation to the first server, and - using, by the first server, the result of said evaluation for allowing or blocking said requested operation.