OWASP stands for Open Web Application Security Project and it is an international non-profit organization that works towards improving the security of software. OWASP has chapters worldwide including tens of thousands of members and through community-led open-source projects, they work to make the web more secure. All of the materials including documentation, tools, and videos are freely available on their website. One of the well-known projects of them is the OWASP Top 10.
OWASP Top 10 is a regularly-updated report containing the top 10 most critical risks for web application security. It is a standard web application security awareness document which is really important for developers. This document is compiled by a well-qualified team of security experts. It is recommended for companies to refer to this document when developing web applications to minimize security risks. OWASP Top 10 is a very good initiative for writing more secure code ensuring information security in organizations. There are ten security risks for web applications reported in this OWASP Top 10 report.
1. Injection: Different injection attack types like SQL injections, LDAP injections, NoSQL injections happen when untrusted data is sent to the interpreter as a part of the query or the code. If an attacker inserts SQL code into a form input and if these form inputs are not properly secured then there is a risk of that SQL code being executed. This is an example of SQL injection. These types of injections can be avoided by sanitizing or validating the form inputs before sending them to the backend.
2. Broken Authentication: Authentication is validating the identity of users allowing only authorized users to access the systems. If authentication is not properly implemented it will allow the attackers to compromise passwords, tokens, or keys. Two-factor authentication is one of the mechanisms that can be used to mitigate authentication vulnerabilities.
3. Sensitive Data Exposure: If sensitive information such as financials, healthcare, and military are not properly protected in web applications and APIs, they can be stolen by attackers using them to do credit card frauds and other types of cybercrimes such as identity theft.
4. XML External Entities (XEE): Poorly configured XML processors are vulnerable to attacks as they can reverence an external entity. Attackers try to exploit this vulnerability by ding data to unauthorized eternal entities.
5. Broken Access Control: Broken access controls allow attackers to bypass authorization and perform tasks as though they were privileged.
6. Security Misconfiguration: Displaying default configurations or displaying excessively verbose errors can be a vulnerability. This can be mitigated by removing unused features and making sure that the error is more general.
7. Cross-Site Scripting: If the web applications allow the users to add custom code to URL paths then it can be a vulnerability. This can be exploited to run malicious javascript code on the victim's browser.
8. Insecure Deserialization: This threat targets the many web applications which frequently serialize and deserialize data. Insecure deserialization often leads to remote code execution
9. Using Components With Known Vulnerabilities: Most web application developers use components like frameworks and libraries. These components will help the developers by minimizing redundant work. But the disadvantage of these components is that the attackers try to use vulnerabilities in these components.
10. Insufficient Logging And Monitoring: Many web applications do not have a proper mechanism to detect data breaches. If there is not an efficient logging and monitoring process then it will allow attackers to further attack systems. Therefore it is crucial to have proper logging and monitoring mechanisms in web applications.
REFERENCES
https://owasp.org/www-project-top-ten/



