Owing to the big quantity of facts saved in net packages and a growth with inside the range of transactions on the net, right Security Testing of Web Applications is turning into very critical day-via way of means of-day. In this tutorial, we are able to do an in depth have a look at approximately the meaning, gear and key phrases utilized in Website Security Testing at the side of It’s trying out approach.

What is Security Testing?

Security testing is a technique which assessments whether the exclusive facts remains exclusive or now no longer (i.e., it isn’t always uncovered to individuals/entities for which it isn’t always intended for) and the customers can carry out simplest the ones duties that they’re legal to carry out.

For Example, a consumer need to now no longer be capable of deny the capability of the internet site to different customers or a consumer need to now no longer be capable of extrude the capability of the net utility in an unintentional manner etc.

Some Key Terms Used in Security Testing

Let’s familiarize ourselves with some phrases which are regularly utilized in net utility Security Testing.

  1. Vulnerability:

This is a weak spot with inside the net utility. The purpose of such “weak spot” may be because of the insects with inside the utility, an injection (SQL/ script code) or the presence of viruses.


  1. URL Manipulation:

Some net packages talk extra statistics among the client (browser) and the server with inside the URL. Changing a few statistics with inside the URL may also from time to time cause unintentional conduct via way of means of the server and that is termed as URL Manipulation.


  1. SQL injection:

This is the technique of putting SQL statements via the net utility consumer interface into a few question, this is then carried out via way of means of the server.


  1. XSS (Cross-Site Scripting):

When a consumer inserts HTML/ client-facet script with inside the consumer interface of an internet utility, this insertion is seen to different customers, and it’s far termed as XSS.


  1. Spoofing:

Spoofing is the introduction of hoax look-alike websites and emails.


Methods for Web Security Testing

1) Password Cracking

The safety checking out on a Web Application may be kicked off by “Password Cracking”. In order to log in to the personal regions of the software, you may both bet a username/ password or use a few password cracker device for the same.

A listing of not unusual place usernames and passwords are to be had alongside open supply password crackers. If the internet software does now no longer put in force a complicated password (For Example, with alphabets, numbers, and unique characters or with as a minimum a required quantity of characters), it could now no longer take very lengthy to crack the username and password.

If a username or password is saved in cookies without being encrypted, then an attacker can use unique techniques to spouse borrow the cookies and the records saved with inside the cookies like username and password.


2) URL Manipulation through HTTP GET Methods

A tester must take a look at whether the utility passes crucial statistics with inside the question string or not. This takes place while the utility makes use of the HTTP GET approach to by skip statistics among the customer and the server.

The statistics is surpassed through the parameters with inside the question string. The tester can adjust a parameter price with inside the question string to test if the server accepts it. Via HTTP GET request, person statistics is surpassed to the server for authentication or fetching data.

The attacker can manage each enter variable surpassed from this GET request to a server so that you can get the specified statistics or to deprave the data. In such conditions, any uncommon conduct via way of means of utility or internet server is the entrance for the attacker to get into a utility.


3) SQL Injection

The subsequent aspect that ought to be checked is SQL Injection. Entering an unmarried quote (‘) in any textbox ought to be rejected with the aid of using the software. Instead, if the tester encounters a database blunders, it manner that the person enter is inserted in a few question that is then achieved with the aid of using a software. In the sort of case, the software is prone to SQL injection.

SQL injection assaults are very essential as an attacker can get critical statistics from the server database. To test SQL injection access factors into your internet software, discover the code out of your codebase in which direct MySQL queries are achieved at the database with the aid of using accepting a few person inputs. If the person enter records is crafted in SQL queries to question the database, an attacker can inject SQL statements or a part of the SQL statements as person inputs to extract critical statistics from a database.

Even if an attacker is a success in crashing the software, from the SQL question blunders proven on a browser, the attacker can get the statistics they’re searching for. Special characters from the person inputs ought to be handled/escaped well in such cases.


4) Cross-Site Scripting (XSS)

A tester should additionally check the web application for XSS (Cross-site scripting). Any HTML For Example, <HTML> or any script For Example, <SCRIPT> should not be accepted by the application. If it is, then the application can be prone to an attack by Cross-Site Scripting.

The attacker can use this method to execute a malicious script or URL on the victim’s browser. Using cross-site scripting, an attacker can use scripts like JavaScript to steal user cookies and information stored in the cookies.

Many web applications get some useful information and pass this information on some variables from different pages.

For Example, http://www.examplesite.com/index.php?userid=123&query=xyz

The attacker can easily pass on some malicious input or <script> as a ‘&query’ parameter which can explore important user/server data on the browser.


Important: During security testing, the tester should be very careful and should not modify any of the following:

  • Configuration of the application or the servers.
  • Services running on the server.
  • Existing user or customer data hosted by the application.
  • Additionally, a security test should be avoided in a production system.


Comments are closed.