Penetration testing · Brussels

Penetration testing in Brussels

In Brussels, we test your web applications, APIs, cloud and networks the way an attacker would. You get proven findings ranked by business risk, clear fixes and a retest to confirm they hold.

  • Brussels-Capital Region
  • French, Dutch, English
  • On site or remote
Brussels
0 kmour office is in the city centre

Local context

Penetration testing in Brussels for regulated and public bodies

Brussels organisations expose a lot online: citizen portals, client extranets, multilingual websites and APIs shared with partners. Each language version or partner integration can hide its own access control flaw. We test them as an attacker would, often with grey box access for better coverage. Each finding comes with its business impact explained for management.

For banks and insurers, DORA requires regular testing of ICT systems, and some entities must also run threat-led penetration tests. In Belgium, the NBB runs the TIBER-BE framework for such exercises. We scope classic pentests that feed your wider DORA testing programme. Law and consulting firms usually focus instead on Microsoft 365, remote access and document platforms.

Internal tests often need someone on your network for a few days. Our office at Place Sainte-Gudule is in the city centre, so on-site sessions in the 19 communes are simple to arrange. We report in French, Dutch or English. A retest after your fixes confirms each issue is closed.

Brussels concentrates EU institutions, federal administrations, company headquarters, banks, insurers and law and consulting firms. Many organisations work in French, Dutch and English at the same time, and answer to both Belgian and European supervisors.

Our office is at Place Sainte-Gudule 14, in the city centre. We work on site in the 19 communes and the periphery, or remotely.

  • RegionBrussels-Capital Region
  • Working languagesFrench, Dutch, English
  • Getting there0 km · our office is in the city centre
  • AuthoritiesCCB, APD / GBA, NBB / FSMA

What is at stake

Why act now

[ 01 ]

Scanners miss what attackers exploit

Automated scans list known flaws but miss logic errors and chained weaknesses. Manual testing shows what can really be reached and stolen.

[ 02 ]

Regulations ask for proof that controls work

NIS 2, DORA and ISO 27001 all expect you to test the effectiveness of security measures. A test report is often the evidence auditors ask for.

[ 03 ]

Customers ask for a recent pentest

Enterprise buyers and partners request a recent test before signing. An outdated or vague report raises more questions than it answers.

Key sectors in Brussels

Penetration testing: what changes for key sectors in Brussels

Public sector and institutions

Public portals hold citizen data and are frequent targets, so testing them before attackers do protects both service and trust.

Banking, insurance and finance

DORA requires regular testing of ICT systems, and penetration tests provide the evidence supervisors expect.

Professional services

Firms storing client files in cloud platforms need to confirm that sharing and identity settings do not leak data.

Software and SaaS

Software vendors need a recent test of their product and APIs to pass customer due diligence.

What we do

Four workstreams, prioritised for your situation

We do not start everything at once. The scoping call shows which workstream matters most, and we start there.

[ 01 ]

Web application and API testing

We test authentication, access control, business logic and data exposure. The approach follows the OWASP testing guidance.

[ 02 ]

External and internal infrastructure

We probe your internet-facing perimeter and, from inside, test how far an attacker could move. Active Directory and segmentation are in scope when relevant.

[ 03 ]

Cloud and Microsoft 365 configuration

We review cloud and identity settings for weaknesses that lead to data exposure or account takeover.

[ 04 ]

Black, grey or white box

We choose the level of prior knowledge that matches your goal. Grey box often gives the best coverage for the time spent.

When did someone last try to break in?

A 30-minute call is enough to define a test scope that matches your risks.

Scope my pentest

Regulators

The authorities that apply in Belgium

CCB

Centre for Cybersecurity Belgium: national NIS 2 authority, registration and incident notification.

APD / GBA

Belgian Data Protection Authority: GDPR supervision and complaints.

NBB / FSMA

Financial supervisors for banks, insurers and investment firms, including DORA.

NIS 2 law

Belgian law of 26 April 2024, in force since 18 October 2024, with CyberFundamentals as the reference framework.

The method

Six steps, one written deliverable each

Each step ends with a document you keep, even if the engagement stops.

[ Step 01 ]Scoping call

A free 30-minute call to agree targets, test type and constraints.

Deliverable : Written scope and fixed price per lot
[ Step 02 ]Rules of engagement

We fix test windows, contacts, exclusions and the legal authorisation to test.

Deliverable : Signed rules of engagement
[ Step 03 ]Reconnaissance and testing

We map the attack surface, then test manually with supporting tools.

Deliverable : Daily status notes and immediate alerts for critical findings
[ Step 04 ]Analysis and rating

We confirm each finding, remove false positives and rate impact on your business.

Deliverable : Findings list with severity and evidence
[ Step 05 ]Report and debrief

We present the results to technical teams and to management separately.

Deliverable : Penetration test report with executive summary
[ Step 06 ]Retest

Once fixes are in place, we test again the findings you have corrected.

Deliverable : Retest report showing the status of each finding
30 minfree scoping call, no obligation
1named counterpart for the whole engagement
6written deliverables you keep
3working languages: FR, NL, EN

Scope and budget

What a Penetration testing engagement in Brussels includes

  • Scoping of targets and test approach in writing
  • Manual testing backed by recognised methods such as OWASP
  • Immediate notice of any critical vulnerability
  • Report with executive summary and technical detail
  • Remediation advice per finding, ranked by risk
  • Debrief session and retest of corrected findings

Questions

Questions before you start

Do we need to inform anyone before a pentest of our Brussels systems?

You must authorise the test in writing, and some hosting or cloud providers require notice under their terms. We formalise all this in signed rules of engagement. If a supplier hosts a target, we check its testing policy before starting.

Does a pentest meet DORA's threat-led testing requirement?

No. Threat-led penetration testing under DORA follows a specific framework with threat intelligence and supervisor involvement. A classic pentest supports your wider testing programme and prepares your teams. We tell you clearly which category each engagement falls into.

How long does a penetration test take for a company in Brussels?

It depends on the scope. A single web application often takes a few days of testing. We give you the exact duration in the written scope after the call.

Will the test disrupt our operations in Brussels?

We agree test windows and exclusions in advance. Risky actions are confirmed with you first. Production systems can be tested with care or replaced by a staging copy.

How often should we run a penetration test?

At least once a year is common practice. You should also test after major changes, such as a new application or a migration.

Do you work on site in Brussels?

Our office is at Place Sainte-Gudule 14, in the city centre. We work on site in the 19 communes and the periphery, or remotely.

Last step

Plan your penetration test

Tell us what you want tested and by when. You receive a written scope and a fixed price per lot after our call.

Office : Place Sainte-Gudule 14, 1000 Brussels
We reply within one business day. Your data is only used to answer your request. Privacy policy.
Thank you. We will get back to you within one business day.