Skip to content
Solvex Space
Offensive / TestingFixed price — $1,499Signed authorization

Phishing Simulation Campaign

Most breaches start with an email. We run realistic, ethical phishing campaigns against your staff to measure real susceptibility and turn every click into a teachable moment — building a human firewall, not blame.

Try the free SPF/DKIM/DMARC Spoof Checker

Verified Solvex Specialist

Verified by Solvex

Direct specialist contact for Solvex engagements

What this means. An authorized Solvex administrator registered and approved this exact public identity. What it does not. Solvex has not inspected the account on the platform, and this is not the platform's own verification.

Solvex specialists never ask for your passwords, recovery phrases, one-time codes, or payments to a personal account. Work, scope and invoices are agreed in writing through the official channels on this site.

Signed authorization required. This engagement is performed only against systems you own or are contractually authorized to have tested, under an agreed scope. See the responsible testing policy.

What's covered

  • Tailored phishing scenarios matched to your industry and threats
  • Email, and optionally SMS or voice, pretext delivery
  • Click, credential-entry and reporting-rate measurement
  • Just-in-time training for staff who interact
  • Benchmarking against prior campaigns and industry norms
  • Coordination with awareness-training programmes

What you receive

  • Campaign results with click, submit and report metrics
  • Departmental and trend analysis
  • Executive summary with recommendations
  • Awareness-training follow-up materials
  • Attestation of ethical, authorised testing

Evidence and reporting

How the work is kept honest
  • Evidence, frozen at issuanceFindings tie to something observed. When the report is issued, the evidence behind it is frozen in the same transaction and cannot be edited afterwards.
  • A signed reportAn Ed25519 signature covers both the report content and the delivered file. Alter a byte of either and verification fails.
  • Signed scope firstTesting starts only after written scope and signed authorization for systems you own or are entitled to have tested.

Anyone holding a Solvex report can verify it publicly without seeing its contents.

Our boundaries

What this engagement does not do, stated before it starts.

  • Only your own employees, with management authorisation
  • No collection or retention of real passwords — captures are neutralised
  • No public shaming or disciplinary targeting of individuals
  • No use of scenarios that cause genuine distress (e.g. fake redundancies)

How this engagement runs

  1. 01

    Intake

    Tell us the system, the goal and the constraints. If the work is not a good fit, we say so before anyone is invoiced.

  2. 02

    Scope and authorization

    Written scope and signed authorization before anything is touched. Security testing runs only against systems you own or are contractually entitled to have tested.

  3. 03

    Investigation or build

    Specialists matched to the work. Findings are proven by hand — scanner output is a lead, never a finding.

  4. 04

    Evidence

    Every finding ties to something observed. When a report is issued, its evidence is frozen in the same transaction, so what backed the report cannot change afterwards.

  5. 05

    Delivery

    A signed report: an Ed25519 signature over both the content and the file, with a short verification reference you can read down a phone.

  6. 06

    Verification and retest

    Anyone holding the report can verify it publicly without seeing its contents. Fixes are retested as part of the engagement — “fixed” means we confirmed it.

Questions we are asked

Do you store the passwords people type in?
No. Any credential-entry is recorded as an event only — we never capture or retain the actual passwords. The goal is measurement and education, not collecting secrets.
How do you avoid embarrassing our staff?
Results are reported in aggregate, and anyone who interacts sees supportive just-in-time training rather than blame. Building a reporting culture matters more than catching individuals.
What do you need to run a campaign?
Management authorisation, a target list or group, allow-listing so our emails reach inboxes, and agreement on scenarios and timing.