“Penetration Testing” is a test attack in simulation to expose the existing vulnerabilities and risk elements of your network and system. It may include attempts to try to breach the application software, servers at backend, interfaces at front end, for better risk assessment and updating of the existing security mechanism.
The Penetration Testing stages mainly comprise of following:
Planning of the attack:
After clear demarcation of the mission goals and parts of the systems to be tested and checked, and the mode of testing. All the information is collected to study the response.
The information gathered in the first stage is analyzed here to have a better understanding of the responses. This when done during run time is called dynamic analysis and when done otherwise is called static analysis. The run time version is preferred for more practical results.
In this stage, methods like SQL Injection are used to penetrate and try to gather the data from the servers. The idea is to not just get the access to the system but also remain there for more deeper penetration.
In the final stage, all the data is gathered to make a list of all the vulnerabilities that were exploited in the process, the data that was compromised and the parts of the system that were affected, along with the time that the whole process took and the penetration survived for.
Following are various types of Penetration Testing:
Only the visible and public assets of the company are attacked here.
The penetration is deeper and within the firewall protection to gather the vulnerabilities of the internal setup.
This provides a better and more practical approach as here the testing can target any random part of the system to check the security measures and response time.
Here the tester and the security team keep a real time check on each other to have a one-on-one response check to find out the system’s security status in case of an intense showdown during actual scenario.