Skip to main content
BilgeQor

Penetration Testing Services

Penetration testing identifies vulnerabilities in a defined technical scope. BilgeQor tests agreed applications, networks and other environments under written authorisation, then delivers written, severity-graded findings with prioritised remediation guidance. You get clear, evidence-based findings and a prioritised plan, so your team knows exactly what to fix first.

With CyberFundamentals and NIS2-oriented readiness as the local reference point in Belgium, BilgeQor scopes Penetration Testing around the assets, access method and test windows you approve. The team checks how exposed services, sessions and permissions could be misused by an attacker; where a retest is included, the report confirms which agreed findings have been resolved. The report describes the agreed scope at the time of testing.

What a penetration test covers

A penetration test is an authorised, scoped attempt to find and validate security weaknesses in agreed systems before someone else does. It goes beyond automated scanning: findings are examined and evidenced, not just listed.

  • It is different from a View the Red Team Exercise service page, which is objective-driven and examines how an authorised adversary path progresses and how detection and response perform.
  • It is different from Threat Hunting, which searches agreed telemetry for evidence of suspicious activity.
  • If you are dealing with an active or suspected incident, Incident Recovery is the right starting point.

What we test

Every engagement is tailored to your environment: targets, environments and conditions are agreed with you in advance.

Applications

  • Web application testing. Examines customer-facing web applications for weaknesses in authentication, sessions, forms, access controls, data handling and common application attack paths.
  • API testing. Examines REST, GraphQL, WebSocket and service-to-service interfaces where present, including authentication, authorisation, business-logic abuse paths, rate limiting, token and session boundaries, tenant isolation, data exposure and integration risk.
  • Mobile application testing. Examines agreed iOS or Android application surfaces, application data handling, authentication flows, API interaction and security-relevant app behaviour.
  • Desktop application testing. Reviews how an agreed desktop application handles user inputs, stores data on the device, communicates with backend services and protects sensitive workflows once installed.

Networks and infrastructure

  • External network testing. Reviews internet-facing systems from an outside perspective to identify exposed services, weak configurations and pathways an external party could attempt to use.
  • Internal network testing. Reviews the internal environment from an authorised position inside the organisation, looking at how systems, accounts and services could be misused if an attacker reached the internal network.
  • Wireless network testing. Reviews agreed wireless networks and access points: how users connect, how the wireless environment is segmented from sensitive systems, and where weak configurations could be misused.
  • VoIP testing. Reviews agreed voice-over-IP components: call routing, authentication, exposed services and abuse paths that could affect communications integrity or call costs.

Specialist environments

  • OT / SCADA / ICS testing. Planned with specialist care: technical acceptance, safety constraints and authorisation are agreed with you in advance.

Related specialist services

  • For controlled availability testing, see DDoS Resilience Testing.
  • For AI-specific risks such as prompt injection, retrieval exposure and tool permissions, see the LLM & AI Agent Security Review.

How an engagement works

1

Scope.

Together we agree targets, environments, test windows, access method and contacts, and document them so everyone works from the same plan.

2

Written authorisation.

Signed authorisation and written rules of engagement, including blackout windows and stop conditions, are agreed with you in advance. Where a hosting provider or supplier operates in-scope systems, their permission is included in the plan.

3

Testing.

Testing runs within the agreed window and rules of engagement. Named contacts, pause options and escalation routes are agreed in advance, so you stay in control throughout.

4

Reporting and debrief.

You receive written findings and remediation priorities, and we walk your team through them. Evidence is shared securely with your named contacts.

5

Retest.

After your team has fixed the agreed findings, we retest them and confirm what has been resolved.

What you receive

Executive summary for non-technical stakeholders
Scope and rules-of-engagement summary
Severity-graded findings register with evidence references
Technical detail for each finding so your team can understand and reproduce it
Prioritised remediation roadmap
Retest outcome for agreed findings, where a retest is included

Reports and evidence are handled under a confidentiality-first process.

Penetration test or application review?

  • If you need a focused review of one web, API or mobile application with fixed package options, App Security Review & Pentest Scopes — BilgeQor Belgium may fit better.
  • If you need several environments tested together, network or infrastructure testing, or a scope that does not fit a package, choose Penetration Testing.
  • If you want to know how an attacker could reach a business objective and how your detection responds, consider a Red Team Exercise.

Pricing and scope

Penetration testing is quoted per engagement. You receive a written proposal setting out the agreed scope and commercial terms.

FAQ

Discuss a penetration testing scope

Tell us what you need tested. We agree scope, authorisation and conditions with you in a clear written proposal.