Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/felixfaisal/automated-securit-testing


https://github.com/felixfaisal/automated-securit-testing

Last synced: 15 days ago
JSON representation

Awesome Lists containing this project

README 

        
# Automated Web Application Security Testing 



![Made With JavaScript](https://img.shields.io/badge/Made_With-JavaScript-yellow?style=for-the-badge&logo=JavaScript)

![Made With Python](https://img.shields.io/badge/Made_With-Python-blue?style=for-the-badge&logo=Python)

![Made For Web](https://img.shields.io/badge/Made_For-Web-blue?style=for-the-badge&logo=web)



## Why is Testing Necessary?



Human errors can cause a ***defect*** or ***failure*** at any stage of the ***software development life cycle***. The results are classified as trivial or catastrophic, depending on the consequences of the error.



The requirement of rigorous testing and their associated documentation during the software development life cycle arises because of the below reasons:



- *To identify defects*

- *To reduce flaws in the component or system*

- *Increase the overall quality of the system*

- *The testing is important since it discovers defects/bugs before the delivery to the client, which

guarantees the quality of the software.*

- *It makes the software more reliable and easy to use.*

- *Thoroughly tested software ensures reliable and high-performance software operation.*



# What is Web Application Security?



Web application security is a central component of any web-based business. The global nature of the Internet exposes web properties to attack from different locations and various levels of scale and complexity. Web application security deals specifically with the security surrounding websites, web applications and web services such as APIs.



## What is Web Application Security Testing?



From web-based email to online shopping and  banking, organizations are bringing their businesses directly to customers' web browsers every day, circumventing the need for complex installations or update rollouts. Additionally, organizations are rolling out internal web applications for finance, marketing automation,and even internal communication that are often homegrown, or at least fine-tuned for their particular needs.



While web applications offer convenience to businesses and customers alike, their ubiquity makes them a popular attack target for cybercriminals. As a result, web application security testing, or 

scanning and testing web applications for risk, is essential.



# AUTOMATED WEB APPLICATION SECURITY TESTING



In this interface, we would like to combine automated testing and security testing to create automated security testing allowing young developers to write secure code from the very beginning by including it into CI/CD actions or running it locally via CLI. 

This application will mainly test for top 10 Owasp Web Vulnerabilities, which are: 



1. **[Injection](https://owasp.org/www-project-top-ten/2017/A1_2017-Injection)**. Injection flaws, such as SQL, NoSQL, OS, and LDAP injection, occur when untrusted data is sent to an interpreter as part of a command or query. The attacker’s hostile data can trick the interpreter into executing unintended commands or accessing data without proper authorization.

2. **[Broken Authentication](https://owasp.org/www-project-top-ten/2017/A2_2017-Broken_Authentication)**. Application functions related to authentication and session management are often implemented incorrectly, allowing attackers to compromise

passwords, keys, or session tokens, or to exploit other implementation

flaws to assume other users’ identities temporarily or permanently.

3. **[Sensitive Data Exposure](https://owasp.org/www-project-top-ten/2017/A3_2017-Sensitive_Data_Exposure)**. Many web applications and APIs do not properly protect sensitive data, such as financial, healthcare, and PII. Attackers may steal or modify such weakly protected data to conduct credit card fraud, identity theft, or other crimes. Sensitive data may be compromised without extra protection, such as encryption at rest or in transit, and requires

special precautions when exchanged with the browser.

4. **[XML External Entities (XXE)](https://owasp.org/www-project-top-ten/2017/A4_2017-XML_External_Entities_(XXE))**. Many older or poorly configured XML processors evaluate external entity references within XML documents. External entities can be used to disclose internal files using the file URI handler, internal file shares, internal port scanning, remote code execution, and denial of service attacks.

5. **[Broken Access Control](https://owasp.org/www-project-top-ten/2017/A5_2017-Broken_Access_Control)**. Restrictions on what authenticated users are allowed to do are often

not properly enforced. Attackers can exploit these flaws to access unauthorized functionality and/or data, such as access other users’ accounts, view sensitive files, modify other users’ data, change access rights, etc.

6. **[Security Misconfiguration](https://owasp.org/www-project-top-ten/2017/A6_2017-Security_Misconfiguration)**. Security misconfiguration is the most commonly seen issue. This is commonly a result of insecure default configurations, incomplete or ad hoc configurations, open cloud storage, misconfigured HTTP headers, and verbose error messages containing sensitive information. Not only must all operating systems, frameworks, libraries, and applications be securely configured, but they must be patched/upgraded in a timely

fashion.

7. **[Cross-Site Scripting (XSS)](https://owasp.org/www-project-top-ten/2017/A7_2017-Cross-Site_Scripting_(XSS))**. XSS flaws occur whenever an application includes untrusted data in a new web page without proper validation or escaping, or updates an existing web page with user-supplied data using a browser API that can create HTML or JavaScript. XSS allows attackers to execute scripts in the victim’s browser which can hijack user sessions, deface web sites, or redirect the user to malicious sites.

8. **[Insecure Deserialization](https://owasp.org/www-project-top-ten/2017/A8_2017-Insecure_Deserialization)**. Insecure deserialization often leads to remote code execution. Even if deserialization flaws do not result in remote code execution, they can be used to perform attacks, including replay attacks, injection attacks, and privilege escalation attacks.

9. **[Using Components with Known Vulnerabilities](https://owasp.org/www-project-top-ten/2017/A9_2017-Using_Components_with_Known_Vulnerabilities)**. Components, such as libraries, frameworks, and other software modules run with the same privileges as the application. If a vulnerable

component is exploited, such an attack can facilitate serious data loss or server takeover. Applications and APIs using components with known vulnerabilities may undermine application defenses and enable various attacks and impacts.

10. **[Insufficient Logging & Monitoring](https://owasp.org/www-project-top-ten/2017/A10_2017-Insufficient_Logging%2526Monitoring)**. Insufficient logging and monitoring, coupled with missing or ineffective integration with incident response, allows attackers to further attack systems, maintain persistence, pivot to more systems, and tamper, extract, or destroy data. Most breach studies show time to detect a breach is over 200 days, typically detected by external parties rather than internal processes or monitoring.