Tampering and debugging
An application security would provide guidance to all those from OWASP highlights the threats developed by reverse engineering. There may be tampering with the application source code more so in applications that deals with sensitive data or undertake critical applications.
Standards and regulations, such as ISO27001, and NIST does mention the risk of having unprotected source code. It goes without saying that organizations have to put strict control measures in place to prevent the possibility of experiencing such type of attacks.
Anti- debugging would detect the use of debugging tools. It prevents the debugger from conducting reverse engineering process. It is something that is achieved with code traps or dead objects once the debugging tools stop to work as it makes the call stack to grow. This would prevent the user from inspecting the control flow of the app. An anti- tampering code changes and reacts in an appropriate manner.
Protection at client side
As the traditional form of security measures do not address the security issues at the client end, to address the growing threats companies would require complete control and validity at their end. Operation at a full time level, would address the behaviour of every single script and what it means is that since it injects more code. A concise inventory of the web scripts is necessary along with the network requests that they end up doing. If the rule engine is powerful it would provide a granular control over each of the script. It is automatically going to disallow tampering with code on the web page. It goes on to access the password on the log in form and getting in touch with some type of domains.