Penetration Testing Dortmund

A penetration test, or "pentest" for short, is a security check that emulates an attack by a malicious party on a network or application to identify security vulnerabilities. This test is coordinated in advance and conducted in such a way that no system is damaged. At the end of the test, you will receive a report that includes the problems and vulnerabilities found, along with suggestions on how to fix them.

In black-box testing, the pentester attempts to attack the target without any prior knowledge of addresses, systems, applications and processes. The main argument for this approach is that this scenario comes closest to the real world and thus simulates a real attack scenario. However, this is only partially true because a real attacker does not have just a week or two like a contracted pentester, but has the entire time, including months or years, to prepare the attack. In fact, some of the most successful hacker attacks have taken place over a period of up to 12 months.
This bias means that black-box testing is often inconclusive and gives customers a false sense of security. Redlings therefore recommends black-box testing only in exceptional cases. The argument that attackers (must) implement a black-box approach also only works to a limited extent, since a long preparation time can lead to extensive internal informtions.

In a white-box test, the pentester receives all relevant information about the target system(s). The advantage is that this approach saves time - and thus costs. It is also generally true that white-box tests are more effective in improving the security of IT systems and should usually be preferred.
Generally speaking, black-box testing can be a suitable means of uncovering security issues against a specification (e.g., a Web API interface), but is very poorly suited to identifying flaws within specific components. In the latter case, white-box testing should be the preferred means.

As with any business service, the cost of a penetration test varies significantly depending on several factors. significantly depending on several factors.

Scoping details such as network IP addresses, complexity and number of (web) applications and employees for social engineering are key factors in determining project size. Taking these variables into consideration, our team works diligently to, align the scope details with your organization's security requirements.

Nevertheless, some empirical values that can serve as an initial guide can be mentioned. A high-quality, professional pentest performed by experts usually costs usually from about €10,000, but can be for large projects also significantly above this amount.

Redlings also offers discounts for multi-year contracts ("continuous pentesting") to ensure, that your company has a consistent pentesting partner, and can can stretch the security budget further.

The scope of a penetration test should always be jointly adapted to the specifics of the company as well as the system to be tested.

In the case of a Web application, the scope often consists of the server and operational landscape as well as the user interfaces and APIs. Often, there are enterprise applications that have been specifically was written and that you want to have looked at.

Other considerations also play a role in a network pentest. In particular, the scope you choose should include mission-critical systems that would Could compromise security in the event of a compromise, e.g. because they store sensitive data, such as user information, passwords or customer data.

One question that is not asked often enough is how much of the testing is automated and how much is manual. Automated tools, especially at the beginning of a project, can save save a pentester a lot of time and their use also depends on the project. However, experience shows that about 90-95% of the pentest is "manual work".

This is not to say that automated vulnerability scanners do not add value; Vulnerability scans are quick and easy tools that should be used on a regular basis to should be used to identify missing patches or outdated software in larger environments.