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.
Penetration testing · 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.

Local context
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.
What is at stake
Automated scans list known flaws but miss logic errors and chained weaknesses. Manual testing shows what can really be reached and stolen.
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.
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
Tracking platforms and partner interfaces expose many entry points, and testing shows which ones lead to operations.
Suppliers holding sensitive design data need proof that access controls hold under a realistic attack.
Patient portals and connected medical systems must be tested to show that health data cannot be reached by an outsider.
Manufacturers learn from internal testing how far ransomware could spread from an office laptop to production.
What we do
We do not start everything at once. The scoping call shows which workstream matters most, and we start there.
We test authentication, access control, business logic and data exposure. The approach follows the OWASP testing guidance.
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.
We review cloud and identity settings for weaknesses that lead to data exposure or account takeover.
We choose the level of prior knowledge that matches your goal. Grey box often gives the best coverage for the time spent.
A 30-minute call is enough to define a test scope that matches your risks.
Regulators
Centre for Cybersecurity Belgium: national NIS 2 authority, registration and incident notification.
Belgian Data Protection Authority: GDPR supervision and complaints.
Financial supervisors for banks, insurers and investment firms, including DORA.
Belgian law of 26 April 2024, in force since 18 October 2024, with CyberFundamentals as the reference framework.
The method
Each step ends with a document you keep, even if the engagement stops.
A free 30-minute call to agree targets, test type and constraints.
Deliverable : Written scope and fixed price per lotWe fix test windows, contacts, exclusions and the legal authorisation to test.
Deliverable : Signed rules of engagementWe map the attack surface, then test manually with supporting tools.
Deliverable : Daily status notes and immediate alerts for critical findingsWe confirm each finding, remove false positives and rate impact on your business.
Deliverable : Findings list with severity and evidenceWe present the results to technical teams and to management separately.
Deliverable : Penetration test report with executive summaryOnce fixes are in place, we test again the findings you have corrected.
Deliverable : Retest report showing the status of each findingScope and budget
Questions
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.
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.
At least once a year is common practice. You should also test after major changes, such as a new application or a migration.
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.
Yes. The executive summary is written so you can share it. Technical details stay with your teams.
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
Tell us what you want tested and by when. You receive a written scope and a fixed price per lot after our call.