[ Tailored social engineering tests ]

Find out what your people will do under pressure. Before an attacker does.

One convincing email, phone call or text message can bypass technical security and established processes. We prepare a realistic attack based on your operations and safely test where it could succeed.

[ Publicly documented cases ]

When an attacker convinces a person, the impact goes beyond email.

Money, sensitive data or operations. Three different organisations show where the right pretext at the right moment can lead.

01 / FINANCE

CZK 46 million

Správa nemovitostí Hradec Králové

Attackers posing as police officers and bank employees persuaded an employee to make repeated transfers totalling approximately CZK 46 million.

VishingAuthorityTime pressure
Read the public source (opens in a new tab)
02 / DATA

Data breach

Partners financial group

The attack affected the group's non-banking operations. Its public statement cited human error and inconsistent enforcement of rules. Banking systems were not affected.

The human factorRulesData
Read the statement (opens in a new tab)
03 / OPERATIONS

Weeks of disruption

Nemocnice Rudolfa a Stefanie Benešov

A ransomware attack crippled the hospital's information systems and severely disrupted its operations. The case was linked to a large-scale phishing campaign.

PhishingRansomwareOperations
Read the case (Czech PDF) (opens in a new tab)

These cases are based on publicly available sources. BOIT was neither a supplier nor an investigator in these incidents.

[ There is no one-size-fits-all test ]

The same attack does not make sense on the factory floor and in accounts.

Different people, processes and habits, and so different routes an attacker will try to get in. First, we find out what you need to test. Only then do we choose a suitable scenario.

01

Manufacturing and operations

Planted flash drives, QR codes or documents with seemingly sensitive content. We check whether people connect, open, report or properly hand them in.

USB baitingQR codesPhysical drops
02

Management and key roles

A fake invitation, a colleague's request, a technical support call or targeted communication exploiting authority, trust and time pressure.

Spear phishingVishingPersonalisation
03

Finance and administration

Fake invoices, changed bank details, service logins, urgent management requests or fraudulent text messages targeting a specific process.

PhishingSmishingBEC scenarios

These are not fixed packages. We combine individual methods according to your organisation's risks.

[ Anatomy of an incident ]

A major incident usually does not start as a major incident.

Public attention comes only when money is stolen, data leaks or operations stop. Yet it often begins with a single seemingly ordinary situation.

  1. 01

    A convincing pretext

    A message or caller fits into an ordinary working day.

  2. 02

    Pressure to decide

    Authority, urgency, curiosity or fear of the consequences.

  3. 03

    One routine action

    Clicking, signing in, opening a file or passing on information.

  4. 04

    A process is bypassed

    A check is skipped, a warning does not arrive or a rule is ignored.

  5. 05

    Real impact

    Money, data, system access or disrupted operations.

[ Try it yourself ]

Would you notice something was wrong?

The public demo lets you try spotting several typical signals. A real test is more complex: it uses your environment, brand, roles and situations your employees find believable.

This is a demonstration. Your test is not based on a one-size-fits-all template.

[ Exactly what you receive ]

From scenarios to decisions. More than a list of clicks.

The value of a test lies not just in the campaign, but in what you can change based on its results.

01

Test design

Objectives, target groups, scenarios, channels, safe delivery rules and a timeline.

02

Simulation delivery

Technical preparation and execution of phishing, smishing, vishing or physical tests.

03

Measurable results

Relevant responses: clicking through, submitting information, taking an action, reporting and responding correctly.

04

Report and recommendations

Results in context, identified weaknesses and specific next steps for management and IT.

[ How we work together ]

The test is meant to assess the organisation, not shame employees.

We agree the scope, data collection and evaluation method in advance. The aim is to identify weaknesses and improve behaviour, not create a public ranking of people to blame.

  1. 01

    Initial consultation

    We clarify the objectives, environment, at-risk groups and technical constraints.

  2. 02

    Scenario design

    We choose suitable channels and prepare a tailored attack pretext.

  3. 03

    Safe preparation

    We define the scope, contact people, escalation rules and necessary exceptions.

  4. 04

    Execution and measurement

    We run the test and record the responses agreed in advance.

  5. 05

    Evaluation

    We deliver the report, explain our findings and recommend the next steps.

[ Scope of cooperation ]

Test once. Or improve over time.

[ Targeted resilience test ]

One specific question

A one-off simulation for a selected group, operation or risk, or for verification after training. Suitable as a baseline assessment or a test of a specific process.

  • Tailored scenario
  • Agreed target group
  • Report and recommendations
[ Ongoing assessment ]

Change you can measure

A combination of different scenarios throughout the year, comparing results and gradually increasing difficulty as the organisation learns.

  • Multiple channels and scenarios
  • Comparing results over time
  • Ongoing recommendations
[ Frequently asked questions ]

What you need to know before testing.

01

How do you choose the right type of test?

Based on the objective, job roles, environment and actual risks. USB baiting may be more valuable in manufacturing, targeted vishing for management, and phishing or smishing linked to financial processes for accounting teams.

02

Can you combine the different methods?

Yes. A single scenario can start with an email, continue with a phone call and end on a fraudulent website. We always configure the combination to match the agreed scope.

03

What data do you collect during a test?

Only the data needed for the agreed evaluation. We define the scope of measurement, access to results and how they are retained before launching the test.

04

Should employees know about the test in advance?

That depends on the test objective and the organisation's internal rules. Together, we choose an approach that delivers meaningful results while respecting your legal and HR requirements.

05

What happens after the evaluation?

We review the results with you and recommend specific changes: training for selected groups, process adjustments, technical measures or a follow-up test with a different scenario.

What a phishing simulation tells you

A phishing simulation is an agreed test that safely assesses how employees respond to fraudulent emails. BOIT also runs telephone simulations (vishing), SMS scenarios (smishing) and physical baiting tests. Deliverables include agreed metrics, a report and recommendations for improvement.