Security Testing

What is Security Testing ?

Security Testing is defined as a type of Software Testing that ensures software systems and applications are free from any vulnerability, threats, risks that may cause a big loss. Security testing of any system is about finding all possible loopholes and weaknesses of the system which might result into a loss of information, revenue, repute at the hands of the employees or outsiders of the Organization.

The goal of security testing is to identify the threats in the system and measure its potential vulnerabilities, so the system does not stop functioning or is exploited. It also helps in detecting all possible security risks in the system and help developers in fixing these problems through coding.

Types of Security Testing :

There are seven main types of security testing as per Open Source Security Testing methodology manual. They are explained as follows:

Vulnerability Scanning :

This is done through automated software to scan a system against known vulnerability signatures.

Penetration testing :

This kind of testing simulates an attack from a malicious hacker. This testing involves analysis of a particular system to check for potential vulnerabilities to an external hacking attempt.

Risk Assessment :

This testing involves analysis of security risks observed in the organization. Risks are classified as Low, Medium and High. This testing recommends controls and measures to reduce the risk.

Security Auditing :

This is an internal inspection of Applications and Operating systems for security flaws. An audit can also be done via line by line inspection of code.

Ethical hacking :

It's hacking an Organization Software systems. Unlike malicious hackers, who steal for their own gains, the intent is to expose security flaws in the system.

Posture Assessment :

This combines Security scanning, Ethical Hacking and Risk Assessments to show an overall security posture of an organization.

How to do Security Testing

It is always agreed, that cost will be more if we postpone security testing after software implementation phase or after deployment. So, it is necessary to involve security testing in the SDLC life cycle in the earlier phases.

Let's look into the corresponding Security processes to be adopted for every phase in SDLC

Request for Proposal

Project Document (if any):