Social engineering assessment

Controlled phishing, phone and messaging campaigns that measure how people and processes respond, with results by group and never by name.

Adversary simulation

Most intrusions still begin with a person: a convincing email, a call from someone who claims to be IT support, a message from a manager who is supposedly in a meeting. Technical controls filter a part of it. The rest depends on whether people recognise the attempt and whether the process gives them a way to report it.

We run campaigns built the way real attackers build them, with every scenario approved by you in advance, and measure what matters: not only who clicked, but who reported, how fast the report reached the security team and what the team did with it.

01Scope

What we test

  • Phishing by email: credential capture, attachments, links
  • Targeted campaigns against roles with elevated access
  • Phone calls to the help desk and to employees
  • Messengers and collaboration platforms
  • Multi-factor authentication: real-time phishing and push fatigue, where agreed
  • Help desk procedures: identity verification before a password or MFA reset
  • Reporting channel: whether a report reaches the security team, and how fast

02Approach

How the work is done

  1. Scenario design

    Scenarios are written and approved one by one. No scenario uses threats, personal hardship or health, and none targets private accounts or devices. No scenario involves physical access to premises, equipment or people: we offer no physical intrusion testing.

  2. Preparation

    Domains and infrastructure are prepared for the campaign. You decide whether the test measures the people alone or the people together with the mail filters.

  3. Campaign

    Messages and calls go out in waves. The control group in your organisation is informed of each wave.

  4. Analysis

    Results are aggregated by group and by scenario. The report contains no names and no data that identifies an individual.

Methodology

03

What you receive

  • Metrics by group and by scenario
  • Timeline of detection and response by the security team
  • Recommendations for process and technical controls
  • Material for an awareness session based on the scenarios used
  • Executive summary for management
  • Technical report: every finding with evidence, CVSS 4.0 vector, CWE class and fix
  • Debrief call with your engineers
  • One retest of every finding within 60 days of the report
  • Attestation letter after the retest

04

What we need from you

  • Written approval of every scenario by management
  • A confirmation that you are the controller of the employee personal data processed, that you have a legal basis for the campaign, and that any employee-representative consultation and data-protection impact assessment your law requires have been completed before it starts
  • A list of the groups in scope
  • An emergency contact for the duration of the campaign

05Standards

Standards behind the method

06Questions

Questions about this service

Will employees be named in the report?

No. Results are reported by group and scenario. The purpose is to improve the process, not to find someone to blame. Naming people destroys their willingness to report, and reporting is the most valuable control there is.

Is it lawful to send phishing emails to our own employees?

With the authorisation of the employer, on the employer’s legal basis as controller of the employee data, and within the employment and data-protection law that applies to you. Employees are informed after the exercise, results are reported only by group, and where your law requires it the employee representatives are consulted and a data-protection impact assessment is made before the campaign. We raise these points during scoping; the legal assessment is made by your lawyers.

Do you collect real passwords?

No. Submitted credentials are not stored and not used; the campaign records only that a submission took place. Where a bypass of MFA is in scope, it is demonstrated on test accounts created for the purpose.

08Request

Tell us what needs testing

  • Website check free of charge
  • Reply within 1 business day
  • NDA before any technical detail
  • Fixed price for paid engagements
  • No obligation

Request an assessment

Describe the systems and the goal. We reply within 1 business day with clarifying questions and the next step.

Who to reply to
We will reply to this address. We recommend using an email address listed in the contact details of your website or application: this will avoid further checks of your connection to the website.

Domain or URL of the website or of the main system to test, for example app.example.com.

Optional contact detail.

Preferred channel
What to assess
Services of interest

Choose all that apply.

Free check

We check your website free of charge

For businesses. If we find no problems, you receive the report free of charge as well. You pay for the report only when we find problems, and its price depends on their number and severity.

Terms of the free website security check

Application security

Infrastructure and cloud

Adversary simulation

AI, Web3 and cryptography

Programs and assurance

Application security

Free website security check

We look at your website from the outside, the way an attacker does, and check whether it can be broken into: weak settings, outdated software, exposed files, unsafe forms. The check is free of charge.

Application security

Web application penetration testing

We try to break into your web application the way a real attacker would: log in to the accounts of other people, read the data of other customers, change prices or orders. You learn what is possible before criminals do.

Application security

API security testing

An API is the channel through which your app, your website and your partners exchange data with your servers. We check that nobody can use it to read or change data that is not theirs.

Application security

Mobile application penetration testing

We examine your iOS or Android app and the servers behind it: what the app keeps on the phone, what can be extracted from it and whether its requests can be tampered with.

Application security

Secure code review

We read the source code of your product and find the mistakes that lead to a break-in, including those that cannot be seen from the outside.

Infrastructure and cloud

Cloud & Kubernetes security assessment

We check how your cloud is set up (AWS, Azure, Google Cloud, Kubernetes): who has access to what, which data is open to the internet and how far an attacker gets after the first mistake.

Infrastructure and cloud

Infrastructure penetration testing

We test your servers and your office network from the outside and from the inside: can an attacker get in, and once inside, reach the accounting system, the mail or the backups.

Infrastructure and cloud

External attack surface assessment

We find everything your company exposes to the internet, including what has been forgotten: old websites, test servers, leaked passwords. Then we show which of it can be attacked.

Infrastructure and cloud

CI/CD & supply chain security

We check the path your code takes from the developer to the customer: build servers, third-party libraries, access keys. Whoever controls that path controls your product.

Adversary simulation

Red team operations

A full-scale exercise. We play a real attacker with a goal, for example to reach customer data, and you see whether your defence notices and stops it.

Adversary simulation

Purple team exercises

We and your defenders work side by side: we execute an attack technique, your team checks whether it sees it, and the gaps in monitoring are closed on the spot.

Adversary simulation

Social engineering assessment

We test people, not machines: the phishing emails, calls and messages that attackers use to obtain passwords. You learn how many employees would be deceived and what to train.

AI, Web3 and cryptography

AI & LLM security testing

If your product has a chatbot or another AI model, we check whether it can be talked into revealing confidential data, breaking its own rules or acting on behalf of someone else.

AI, Web3 and cryptography

Smart contract audit

Before a smart contract holds money, we look for mistakes in its code that would let someone withdraw or freeze the funds. After deployment such mistakes cannot be corrected.

AI, Web3 and cryptography

Cryptography review

We check how your product encrypts data and protects keys: whether the right algorithms are chosen and whether they are applied correctly. A mistake here makes the encryption useless.

Programs and assurance

Bug bounty program management

A bug bounty is a program in which independent researchers look for vulnerabilities in your product and are paid for each one they find. We launch and run such a program for you.

Programs and assurance

Vulnerability disclosure program (VDP)

A public page and a procedure that tell researchers how to report a vulnerability to you safely. Without them reports get lost or arrive as threats. We set the process up and handle incoming reports.

Programs and assurance

Continuous penetration testing

Instead of one test a year, we test every significant change of your product throughout the year, so that a new vulnerability does not wait for months to be found.

Programs and assurance

Compliance-driven penetration testing

A penetration test scoped and documented to match what an auditor, a regulator or a large customer expects to see in a report: PCI DSS, DORA, NIS2, ISO/IEC 27001, SOC 2. Whether the report is accepted is decided by them.

Services of interest

Not sure yet

Choose this if you do not know which service you need. Describe the task in your own words, and we will suggest the service in the reply.

What needs testing, why now, and any deadline or compliance requirement. No passwords, keys or vulnerability details.

Confirmations

Do not send credentials, keys or details of a vulnerability through this form. Such material is exchanged later only as an encrypted archive, with the password sent separately.

Automated abuse check