Penetration testing · Liège

Penetration testing in Liège

In Liège, 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.

  • Province of Liège, Wallonia
  • French, English
  • On site or remote
Liège
1 hfrom our Brussels office

Local context

Penetration testing in Liège for aerospace, cargo and biotech

In Liège, the systems worth attacking are often engineering and research systems. Space and aerospace firms keep design files and test data that competitors or foreign states may want. Biotech spin-offs hold research results and clinical data. We test the paths to that data: VPN, cloud storage, collaboration tools and the accounts with the most rights.

Around Liège Airport, cargo handlers and forwarders connect to airlines, customs and customers through portals and APIs. These must stay available and must not leak shipment details. We test the exposed interfaces and the internal network behind them. Laboratory instruments and older industrial machines get careful handling, since many cannot tolerate aggressive scanning.

Liège is about one hour from our Brussels office by train. We run external tests remotely and plan internal tests on site in the Liège area, including the airport and science park zones. Test windows can follow your shift patterns. Reports and debriefs are delivered in French or English.

Liège combines Liège Airport, a major European cargo hub, with a space and aerospace cluster, university spin-offs in biotech and a long industrial tradition. These organisations handle sensitive data, regulated products and operational technology that customers and authorities expect to be secured.

Liège is about one hour from our Brussels office by train. We work on site in the Liège area, including the airport and science park zones, or remotely.

  • RegionProvince of Liège, Wallonia
  • Working languagesFrench, English
  • Getting there1 h · from our Brussels office
  • 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 Liège

Penetration testing: what changes for key sectors in Liège

Logistics and transport

Tracking platforms and partner interfaces expose many entry points, and testing shows which ones lead to operations.

Aerospace and space

Suppliers holding sensitive design data need proof that access controls hold under a realistic attack.

Health and life sciences

Patient portals and connected medical systems must be tested to show that health data cannot be reached by an outsider.

Manufacturing and industry

Manufacturers learn from internal testing how far ransomware could spread from an office laptop to production.

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 Liège 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

Our aerospace customer requires a pentest of our supplier portal. What do you need?

We need the target list, test accounts for each role and any testing rules from your customer contract. We then agree the rules of engagement and a test window. The report can go to your customer in full or as a summary.

We are a small spin-off. What should we test first?

Usually the internet-facing side: your web application, cloud storage and email accounts. That is where most early attacks start. An internal network test can follow once the team and infrastructure grow.

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.

What is the difference with a vulnerability scan?

A scan is automated and lists known weaknesses. A penetration test is led by a person who confirms, chains and exploits weaknesses to show real impact.

Can we share the report with customers?

Yes. The executive summary is written so you can share it. Technical details stay with your teams.

Do you work on site in Liège?

Liège is about one hour from our Brussels office by train. We work on site in the Liège area, including the airport and science park zones, 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.