Technical illustration of penetration testing
Penetration testing

Before an attacker tries it,
we will.

Every system has a weak point. The difference is who finds it first. We act as a hired attacker, but we are on your side. We simulate a real attack, uncover specific routes in and give you a precise plan of what to fix.

80+
Completed
penetration tests
1 200+
Discovered
vulnerabilities
100 %
Clients received
concrete deliverables
5+
Years of testing
Czech companies
[ What we test ]

Six areas where attackers look for weaknesses

Web applications

The shortest route in is through a form, login or API.

Click to learn more →

Your web application is often the shortest route in. A single flaw in a login, form or API can give an attacker access to data, accounts and internal systems.

Potential impactData breach • Service outage • Fines and compliance • Loss of trust
OWASP Top 10SQL injectionXSSAuth bypassAPI security

Network infrastructure

Old rules, forgotten access rights and paths for moving further in unnoticed.

Click to learn more →

Networks often contain old rules, forgotten access rights and points from which an attacker can move further in unnoticed. The test shows how easily an attacker could reach important systems.

Potential impactSystem downtime • Attack spread • Ransomware • Costly recovery
Active DirectoryNetwork segmentationLateral movementPriv escalationMITM

Cloud (AWS / Azure / GCP)

The cloud is not secure simply because it runs with a major provider.

Click to learn more →

The cloud is not secure simply because it runs with a major provider. The most common problems arise when something is misconfigured, accessible to too many people or more exposed than it should be.

Potential impactData exposure • Account abuse • Customer incidents • Unnecessary costs
IAM misconfigurationExposed bucketsSecrets in codeCloud permissions

Mobile applications

Poorly protected communications or storage can give an attacker more access than they should have.

Click to learn more →

Mobile applications often handle accounts, sensitive data and client information. Weak protection of communications, storage or application logic can give an attacker more access than they should have.

Potential impactAccount takeover • Data breach • Fraud • Brand damage
Insecure storageTraffic interceptionReverse engineeringAPI communication

OT / SCADA systems

Here, it is about more than data, operations themselves are at stake.

Click to learn more →

Here, it is about more than data: operations themselves are at stake. The test checks whether operational systems are truly separated and how easily they could be reached from the general IT environment.

Potential impactProduction downtime • Delivery delays • Penalties • Operational damage
IT/OT boundaryRemote accessSCADA securityPLCNetwork segregation

Social engineering

All it takes is a convincing email, phone call or someone who looks trustworthy.

Click to learn more →

Not every attack starts with a technical flaw. Often, a well-targeted email, phone call or visit from someone who looks trustworthy is enough.

Potential impactCredential theft • Financial fraud • Data breach • Unauthorized entry into the company
Phishing simulationVishingPhysical accessAwarenessHuman factor
[ How it works ]

A pentest, step by step

  1. 01

    Preparation

    Test objectives and ground rules

    We begin by agreeing on the scope, objectives and rules of the test. We focus on what has a real impact on your data, operations and business.

  2. 02

    Reconnaissance and mapping

    Recon & OSINT

    We identify what is visible about your system from the outside: exactly what an attacker can learn about you before the first intrusion attempt.

  3. 03

    Attempting an intrusion

    Exploitation

    We simulate a real attack and verify possible routes in. We combine manual testing with tools to catch even less obvious flaws.

  4. 04

    Verifying the impact

    Post-exploitation

    We investigate what an attacker could do after gaining an initial foothold: whether they could move further, reach sensitive data, gain higher privileges or access important systems.

  5. 05

    Report and recommendations

    Findings, priorities and remediation

    You receive a clear deliverable with findings, priorities and remediation recommendations, so IT knows what to fix and management understands the business implications.

[ References ]

Companies that have entrusted us with their security

We have performed penetration tests for banks, manufacturers, hospitals and startups. Attackers do not care about size, and neither do we.

Pavel's cybersecurity training has the pace of an ice hockey game: fast, practical and full of involvement. Participants aren't spectators: they're active players. No boredom, just clear insights they can use straight away.

Tereza SíkorováSecurity Architecture, Česká Spořitelna

Accolade has worked with Pavel for several years. His proactive approach makes his training one of our most popular and best-attended sessions, engaging people across generations.

František LokvencSenior IT Manager, Accolade

We've worked with BOIT on information security talks for a long time. Pavel combines excellent expertise with an entertaining style. In over 10 years of organising specialist events, BOIT has been one of our best partners. Highly recommended.

Peter StrážnickýKB Security Governance, Komerční Banka
[ Cost and time required ]

How much does it cost, and how long does it take?

We will give you a price within 24 hours of the first consultation. It depends on the scope, but you never pay for extra time.

Time required
Web application
2–4 days of testing + 2 days for the report
Network infrastructure
3–5 days of testing + 2–3 days for the report
Cloud environment
2–4 days of testing + 2 days for the report
OT / SCADA
4–7 days of testing + 3 days for the report
Social engineering
1–3 days + report within a week
What affects the price
Scope and type of testA web application versus the entire infrastructure.
Environment complexityNumber of applications, systems, networks and cloud accounts.
Black box vs. white boxThe less information we receive, the longer reconnaissance takes.
UrgencyNeed results within a week? An EXPRESS surcharge applies.
[ Who we test for ]

The issues we encounter most often in each sector

These are recurring real-world scenarios, rather than theoretical examples. See what we typically address in your sector.

Manufacturing & Automotive

Production has stopped. The attacker found the weakness before you did.

In manufacturing, the same problem keeps recurring: office IT and operational technology communicate more than they should. Once an attacker gets into the corporate network, the route to production is often shorter than companies think.

01
Day 1
Reconnaissance
We found an old subcontractor VPN account. It was still active.
02
Day 2
Initial intrusion
A default password in Jenkins. From there, a path to CI/CD and repositories.
03
Day 3
Critical finding
The office network provided direct RDP access to an industrial PC. We called immediately.
04
Day 5
Report
14 findings. 2 critical, 4 high. A prioritized remediation plan and cost estimate.
Typical risks
IT and OT without meaningful separation
Suppliers' remote access without MFA
Outdated workstations in production
Default passwords on PLC and SCADA interfaces
Findings from practice
Access from the office network to production through unsecured RDP
Old subcontractor VPN accounts that nobody disabled
SCADA interfaces accessible from the internet or without strong authentication
Ransomware capable of spreading from one workstation across the entire operation
[ Case study ]

From an email to the production line in 72 hours.

The client approached us to meet a compliance requirement. Within three days, we went from a phishing email sent to reception to direct access to the production line's control system. Nobody in IT knew.

72h
From phishing to the production line
18
Vulnerabilities found
3
Critical findings

"We thought our IT and OT were separated. They showed us three ways around it. One went through reception's email. We have fixed it now and know what to focus on next."

IT Security Manager, automotive supplier
[ What you receive ]

Deliverables you can put to work immediately

You receive clearly described findings, their business impact and a recommended remediation approach.

Precise technical documentation

Each finding is documented so your IT team or supplier can act on it immediately: CVSS score, PoC, impact description and specific remediation recommendations.

Executive summary

A clear summary for management: what we found, its impact and what to address first.

Consultation at no extra charge

We walk you through the results and put them in context. With no additional invoice.

Retesting findings

After key findings are fixed, we verify that they are truly resolved. Included in the price.

[ Why BOIT ]

Testing by people, with more than tools

Certified ethical hackers

Our team tests manually with an understanding of the context. We do more than run tools.

CEH MasterCEH PracticalCompTIA Security+

We call when we find a critical issue

We do not leave it for the report a week later. If we find a serious problem, we call immediately. Every hour of delay has a cost.

We test Czech companies in Czech

We understand the local environment: Czech legislation, NIS2 and Czech supply chains. Your report is written in Czech, rather than translated from English.

[ FAQ ]

Frequently asked questions

01

Do you also perform black box tests?

Yes. But first, we always discuss what they should achieve. Black box testing makes sense in specific situations, it is not always the most cost-effective way to uncover the most issues.

02

How long does a pentest take?

Usually 2–5 days of testing + 2–3 days to prepare the report. It depends on the scope. Web application tests tend to be shorter; infrastructure tests take longer.

03

How much does it cost?

It depends on the scope. We do not sell fixed-price "packages". We provide a price after the first consultation, usually within 24 hours. Call or email us.

04

We need ISO 27001 / NIS2. Will this help?

Yes. A pentest is one of the required forms of evidence for both standards. You can use the test deliverables directly as supporting documentation for your auditor.

05

Do you test cloud environments too?

Yes: AWS, Azure and Google Cloud. Real testing, not following a blog tutorial. We understand the shared responsibility model and the boundaries for testing.

06

Will you disrupt our operations?

That depends on our agreement. Our standard approach is to test without affecting operations. If you also want load-testing scenarios, we agree on a maintenance window.