• Penetration testing


Penetration tests are popularly described as simulating an attack against a specified IT area. The subject of a penetration test is always a certain isolated part of a company’s IT ecosystem, such as a web application, mobile application, desktop application, or network infrastructure.

The biggest weakness of penetration tests lies precisely in isolation. As a result of periodic execution of these tests, information can be that all security risks have been reduced to an acceptable level and the tested system  is resistant to attacks. 

So, the main reason why penetration tests are essential to an organisation's security is because they help personnel learn how to handle any type of hacker attack. Penetration tests allow you to determine whether your network environment is truly resilient. Through testing, we look for weaknesses in the system and potential targets of a hacker attack. This helps our clients protect their networks from external threats. 




In the pre-penetration testing phase, the tester and the client define the scope of the penetration test, such as what systems will be tested, what methods the tester will be using, and what the other objectives and legal implications are.


The survey requires the tester to gather as much information as possible about the test subject, including information about personnel, technology and systems.


After gathering sufficient information about the client's system, the testers begin to model the real threats that the client will might face and then scan for relevant system vulnerabilities that would typically be targeted by these attacks.


In this phase, all identified vulnerabilities are exploited in accordance with the scope specified in the pre-engagement phase.


After the testing period or after all relevant systems have been exploited, all testing methods and vulnerabilities - including associated devices, ports or personnel - are logged.


The tester creates a penetration testing report for the client that describes the methods used, vulnerabilities exploited, remediation measures, and other important information.


After the client has had time to resolve the vulnerabilities listed in the initial report, the tester can go back and perform the same penetration tests on the client's system to verify that the vulnerabilities have been resolved. This phase is not as common, but may be requested by the client.


The goal is to verify whether an organisation's information system can be penetrated. The tester uses the means and methods most quickly leading to the goal.

  • identifying the environment from the outer perimeter;
  • designing risk mitigation measures.
  • implementing environment tests; 
  • designing the tests performed; 

The output of the test is a final report that includes:

  • a test execution record containing details of the penetration methods and procedures tested;
  • a summary of the results obtained, including access data, information, etc.;
  • a list of vulnerabilities exploited to perform the penetration.




There are three main strategic approaches to penetration testing, each involving different steps and tools. The main differences in these approaches relate to the extent of the attacker's theoretical knowledge of the target system or network.

In a grey-box penetration test, the tester has a basic understanding of the target system, such as initial access credentials, a network infrastructure map or a logical application schema. Penetration tests of this type create a realistic attack scenario because malicious hackers usually do not attack without first gathering information about their target.


In contrast, in a black-box penetration test, the tester has no prior knowledge of the target network or system. Because the tester does not have access to information such as internal code, software, credentials or sensitive data, black-box penetration tests force testers to think like a potential hacker when searching for vulnerabilities. However, unlike a true malicious hacker, a penetration tester in a closed environment has only a limited amount of time in which to access and test the system.

White-box penetration tests are less like a cyberattack and more like a complete scan of the system at the source code level. In an open-box penetration test, the tester has the highest possible level of access to the target system. The goal is to allow the tester to break through the system's security measures to find logic errors, misconfigurations, poorly written code and inadequate security measures. Although open-shell penetration tests are comprehensive, they can fail to identify vulnerabilities that an attacker would exploit.