Web Application Security Testing
Web App Security Testing
Web applications play a vital role in the success of a business and are an attractive target for cybercriminals. Web Application Penetration / Security Testing (WAPT / WAST) is the process of proactively identifying applications vulnerabilities, such as those that could lead to the loss of sensitive user data, company data and financial information. This includes misconfigured SaaS web applications and server-side security controls.
Certbar undertakes Web Application Security Testing (WAST) with manual approach with our unique and well researched methodology including but not limited to OWASP Top 10, OSSTMM guidelines, SANS Top 25, etc. helping our client's vital IT asset. We are highly focused on business logic vulnerabilities that are missed by automated scanners. Our team conducts internal discussions in a timely manner to discuss weird testing techniques which results in finding more vulnerabilities.
Our Approach to Dynamic Analysis
In this era of technology where the dynamic application analysis is used on a wide scale we ensure our clients stay ahead of the emerging threats. We adapt and integrate more in our methodology from the current security standards such as ASVS by OWASP, SANS top 25, MITRE | ATT & CK, NVD, OWASP top 10, NIST, and OSSTMM.
Penetration testing for web applications not only requires knowledge of the latest web application security testing tools but also a deep understanding of how to use them most effectively. To assess web app security, ethical hackers leverage a range of specialist tools. These range from specialist pen testing platforms (such as burp suite, Metasploit Pro and Kali Linux), to networking tools (such as Wireshark), and custom-developed tools and exploits written using Python, Java and PowerShell.
Web application might be interacting with another:
Reporting Standards
Technical Vulnerability Test Cases
Technical vulnerabilities can be easily found by fuzzing and our generic fuzzing list contains 400+ payloads to help our team identify those vulnerabilities. Our fuzzing list only works as an identifier. Post exploitation of that vulnerability is carried out manually. We keep on adding new and generic identifiers to our fuzzing list every quarter.-
SQL Injection
-
Cross Site Scripting (XSS)
-
Xpath Injection
-
Improper Input Validation
-
Directory Traversal
-
Buffer Overflow
-
OTP Bypass
-
Unrestricted File Upload
Business Logic Vulnerability Test Cases
CWE-840: Business Logic Errors: Weaknesses in this category identify some of the underlying problems that commonly allow attackers to manipulate the business logic of an application. Errors in business logic can be devastating to an entire application. They can be difficult to find automatically, since they typically involve legitimate use of the application’s functionality. However, many business logic errors can exhibit patterns that are similar to well-understood implementation and design weaknesses.-
Unverified Ownership
-
Authentication Bypass Using
an Alternate Path or Channel -
Authorization Bypass Through
User-Controlled Key -
Weak Password Recovery
Mechanism for Forgotten Password -
Incorrect Ownership Assignment
-
Unprotected Primary Channel
-
Insufficiently Protected
Credentials -
Trusting HTTP Permission
Methods on the Server Side
