<style>.wz-pt-dark [style*='transition-delay'],.wz-pt-dark .wz-pt-console-rows li,.wz-pt-dark .wz-pt-alert{opacity:1!important;transform:none!important}.wz-pt-dark .wz-pt-lane ol::before{transform:none!important}</style>
[email protected]

New at WZ-IT: autonomous white-box pentest

Automated pentesting at the speed of attackers

Agent swarms attack an isolated copy of your application, try to exploit every finding and show what can actually be exploited. The entire test runs on servers in Germany and the EU, and we operate the models ourselves.

  • Servers in Germany and the EU
  • No third-country transfer
  • Models operated by us
  • Every finding reviewed by us

Attackers work automatically. The test has to as well.

For years we have helped companies defend a growing attack surface with current security approaches from the open-source world. The same applies to software: if you release often but test manually only once a year, you are testing a state that is quickly out of date.

Annual manual pentest

  1. SchedulingAgree the scope, find a date with the test team
  2. TestTesting happens within the booked time frame
  3. ReportBy handover the code has often moved on
  4. RepeatThe next test frequently follows a year later

Autonomous pentest at WZ-IT

  1. HandoverHand over the source code, no staging of your own needed
  2. AttackAgent swarms test code and running copy in parallel
  3. ProofEvery finding is confirmed by exploit or rated as not exploitable
  4. RepeatAgain at the agreed interval when the code changes

How a pentest at WZ-IT works

Your production system stays untouched. We attack a copy that we build specifically for the test.

Step 1 / 5

You hand over the source code

Repository or archive, plus roles and the processes that are critical to your business.

  • No staging of your own needed
  • Roles and test accounts named
  • Critical processes named

White box, grey box, black box: what the difference costs

The three approaches differ in what the tester knows about the application. The more they know, the less time is lost on guesswork.

Black box

Knowledge
No source code and no inside knowledge, the view of an outside attacker
Result
What is reachable and visible from outside
Effort
A large part of the time goes into reconnaissance

Grey box

Knowledge
Partial knowledge, such as test user accounts and documentation
Result
Additionally flaws behind the sign-in
Effort
Less reconnaissance, the code stays unknown

White boxOur approach

Knowledge
Source code, configuration and architecture
Result
Also flaws in logic and permissions that are not visible from outside
Effort
For your own software usually the most efficient way: more time for testing and proof

What can be exploited comes first

Static code analysis produces long lists of hints. Which of them are dangerous stays open. We attack every finding in the test environment and rate it by exploitability and impact. That tells you what has to be fixed first.

  • Exploit as proof instead of assumption
  • Rated by exploitability and impact
  • A clear order for remediation

Example finding

Access to invoices of other accountsCritical

Proof
Exploit successful in the test environment
Impact
Read access to other customers' data
Remediation
Add an access check per record

Your source code does not leave the EU

Source code is among the most sensitive assets of a company. That is why we operate the models ourselves: large open-weight models with more than 500 billion parameters on GPU servers we run for this purpose. Models, test environment, analysis and report stay on servers in Germany and the EU.

  • Servers in Germany and the EU
  • No third-country transfer
  • Models operated by us
  • Open-weight models instead of third-party AI services

From a single test to continuous testing

Step by step we are offering customers the option to connect their Git repository. Changes to the source code are then analysed automatically at fixed intervals and attacked where something looks suspicious.

  1. 1

    Connect the repositoryYour Git repository is linked to the testing

  2. 2

    Check changesNew commits are analysed at intervals

  3. 3

    Attack and rateSuspicious spots go through pentest and exploit

  4. 4

    AlertYou are notified when a finding is confirmed

The connection is being rolled out to customers gradually.

For existing and new customers

The pentest is aimed at companies that operate software or have it developed.

Software by WZ-IT

Software we develop for customers goes through the pentest as standard.

Software development

Your own application

You develop in-house or with an agency and want the current state tested before a release.

Request a pentest

Find, fix, operate: on request we fix the findings and take over hosting and operations of the application.

Reviews & projects

Software projects with reliable outcomes

Proof for modernization, API extension, architecture, deployment and ongoing operations.

Networking & Provisioning

WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.
Steve KirchnerManaging Director, nextGYM GmbH
View project

International

Built in Germany's Ruhr Valley. Running worldwide.

WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.

Selected projects

Read client reviews

Frequently asked questions about the pentest

Answers to the most important questions

Request a pentest

Have your application attacked before others do it

You speak directly with the people who are technically responsible.

In the conversation we clarify:

  • Which application should be tested, and to what extent?
  • How does your source code reach our test environment?
  • Which findings do you fix yourself, which do we take over?

Your contactsTimo Wevelsiep & Robin Zins

The conversation is free and non-binding.

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH
Timo and Robin, founders of WZ-IT

Let's Talk About Your Idea

Contact us with a specific IT challenge or an early idea. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.

1 / 3 · Topic Selection

What is your inquiry about?

First select the service area that best matches your project.

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.
Jakob ÖschlbergerInno7 GmbH