Method and system for web integrity validator
A computer-implemented method and system for the validation of a true browsing user on a website is disclosed. The invention allows for the collection of data regarding the evolving threat landscape created by online attackers. The system and method fingerprint user behavior to detect differences between a local user, a remote/foreign user, and an automated script. The system then covertly transmits that information back to a financial institution client without giving online attackers the opportunity to notice such transmittal. Certain embodiments of the invention also correspond with the browsing user to validate their identity. The claimed system and method proactively reveal attackers and attack ploys, additionally enabling institutions and security consultants to adapt to attacks in an automated fashion.
1. A computer-implemented method for network security and integrity validation. comprising the steps of:
detecting, within a computer network, at least one codepath difference between a local user, a remote/foreign user, and an automated script, wherein said detecting is performed by a fingerprinter, said fingerprinter being configured to emit a source code to measure a manner in which a function is run within a browser,
transforming a source code emitted from said fingerprinter, wherein said transforming is performed by a mutator, said mutator being configured to send the same detection a plurality of times more in a mutated yet functionally equivalent form to require an attacker to emulate a same human action for each such transformation, said transformation being undetectable by a human user,
and employing defensive mechanisms for security-auditing,
wherein said detecting, transforming, and employing of defensive algorithms occurs concurrently and continuously,
thus enabling the collection of information regarding a browsing user.
2. The method of claim 1 , further comprising:
collecting said information regarding the browsing user in a central database,
processing said collected information via a maintainer application interface, and
corresponding, via a user interface façade, with a specific browsing user to validate said user's integrity if a security threat is detected.
3. The method of claim 2 , wherein said user interface façade comprises variable themes.
4. The method of claim 2 , wherein said security threat is a “Man-in-the-Browser” attack.
5. The method of claim 1 , further comprising randomizing defenses, which is performed by the mutator.
6. The method of claim 1 , wherein said defensive mechanisms further comprise defensive algorithms, encryption and obfuscating methodologies, attack tracing methodologies, and defensive design characteristics.
7. The method of claim 1 , wherein said transforming of source code is polymorphic.
8. The method of claim 1 , wherein said mutator additionally inserts anti-debugging, anti-tampering, and/or proof of work code in intertwined locations within the source code.
9. The method of claim 1 , wherein said at least one codepath difference is signified by the following: a mismatch between claimed and detected software versions, information about the visual environment being displayed to the user, information on the patterns of user input, timing, an availability of resources, and an ability to use functions normally not available.
10. The method of claim 1 , wherein said mutator is configured to reorder statements and functions without violating data flow constraints.
11. The method of claim 1 , wherein said imitator is configured to replace direct variable access with enumeration and computed hash comparisons.
12. The method of claim 1 , wherein said mutator is configured to replace single event listeners with code inside a personal global event dispatcher.
13. The method of claim 1 , wherein said imitator is configured to bind encryption routines to an expected environment.
14. The method of claim 1 , wherein said mutator is configured to convert constants into computations, wherein said computations are moved within the code.
15. The method of claim 1 , wherein said mutator is configured to convert variable access into a memory array.
16. The method of claim 1 , wherein said imitator is configured to convert source computations into a custom-written bytecode.
17. The method of claim 1 , wherein the mutator is configured to move computations out of scripting languages into computations performed by a rendering engine in the course of evaluating markup.
18. The method of claim 1 , wherein the mutator is configured to use a first encryption key for a first part of a code, and a second encryption key for a second part of the code, said first and second keys being requested at runtime from a backend server.
19. The method of claim 1 , wherein the defensive algorithms are configured to require a unique identifier with a cryptographic signature for each transformation.
20. A computer implemented system for validating a secure computer network, comprising a computing device including a processor that is coupled to a computer memory and a server, wherein the system performs the steps of:
detecting, within a computer network, at least one codepath difference between a local user, a remote/foreign user, and an automated script, wherein said detecting is performed by a fingerprinter, said fingerprinter being configured to emit a source code to measure a manner in which a function is run within a browser,
transforming a source code emitted from said fingerprinter, wherein said transforming is performed by a mutator, said mutator being configured to send the same detection a plurality of times more in a mutated yet functionally equivalent form to require an attacker to emulate a same human action for each such transformation, said transformation being undetectable by a human user,
and employing defensive mechanisms for security-auditing,
wherein said detecting, transforming, and employing of defensive algorithms occurs concurrently and continuously.