Aventura, Florida · serving clients across the United States (305) 404-9404Toll-free (800) 767-8566Emergency? Get a call within 1 hour

Security Awareness Training

Train your people to stop the phish, the fake voice and the wire request before money moves.

Buy online

Fixed prices and a written scope. Add what you need to your cart, then check out.

Phishing simulation

A realistic, authorized phishing campaign with short training for anyone who clicks. Priced per person.

$12 per user, per campaign

Security awareness training

Annual online training for every user: phishing, passwords, safe browsing, data handling and what to do when something looks wrong. Priced per user.

$45 per user, per year

Executive and finance team fraud-prevention workshop

A live session for the people who approve payments and handle sensitive requests: callback verification, wire fraud and deepfake voice and video drills.

$2,400 per session, up to 15 people

After you purchase, we contact you within 1 hour, any time of day or night, to start onboarding.

Demo shop: no payment is taken.

Security awareness training is part of how a cybersecurity company protects a business. Email filters, multi-factor sign-in and mail authentication stop most attacks, and the rest reach a person: an assistant who gets an urgent request from the CEO, an accounts payable clerk with a changed bank account, a help desk technician asked to reset a password. We train those people to recognize the attack, and, more importantly, to follow a procedure that works even when they cannot tell.

The program combines phishing simulation, role-based lessons, callback and wire-fraud drills, and deepfake awareness, and it measures click rate and report rate so you can see whether behavior is changing. Packages with pricing are in our shop at /shop/; we scope anything tailored with you.

At a glance

Phishing simulation and role-based security training run by a cybersecurity company: finance, executives, help desk and new hires each learn the attacks aimed at them, practice callback verification and wire-fraud drills, and learn to report. We measure click rate and report rate and show you the trend.

The problem

Most fraud does not break in; it asks. A convincing email, a cloned voice or a fake invoice reaches a person who has seconds to decide. Technology stops a great deal, but the last decision is human, and a once-a-year slideshow does not change it. We train people the way attackers approach them: by role, with realistic simulations, short lessons and a written rule that does not depend on spotting a fake, such as verifying every payment change by a callback to a known number. Because we are a security company that tests these same attacks under written authorization, the scenarios come from real tradecraft rather than a stock library.

Social engineering works because it targets the one control that cannot be patched. Business email compromise, vendor-impersonation invoices and, increasingly, cloned voices and faked video calls all aim at a person who is busy, polite and trying to help. The FBI's Internet Crime Complaint Center reports business email compromise as one of the costliest categories of internet crime year after year, and a single successful wire request can be larger than a company's annual security budget.

Annual compliance videos do not change that. People forget, the attacks change, and nobody practices the moment that matters. We make that moment routine: short lessons, realistic simulations, and a drill in which the finance team handles a staged request exactly as they would a real one.

What we deliver

  • A phishing simulation program with a calendar, scenarios and a safe-sender configuration for your mail platform
  • Role-based training tracks for finance, executives, help desk and new hires
  • A written payment-change and callback verification procedure, and a drill script for it
  • Deepfake voice and video awareness sessions with a staged-call exercise
  • A reporting button or process and a no-blame reporting policy
  • A metrics report: click rate, report rate, time to report and repeat-clicker trend, by team
  • An onboarding module for new hires, and a refresher cadence for everyone
  • Evidence for your insurer, client or examiner that training took place
  • Recommendations that link findings to technical controls: mail authentication, multi-factor sign-in and approval limits

Training is built by role. Finance and accounts payable learn payment-change fraud and the callback rule. Executives and their assistants learn impersonation, urgency and how attackers use public information. The help desk learns to resist password-reset and MFA-reset pretexts. New hires get a first-week module, because attackers target them within days of a public announcement.

Simulations are realistic and fair. We send authorized simulated phishing, attachment, QR-code and credential-harvest messages tuned to your business, and anyone who clicks sees a short lesson at that moment. Simulations are not a trap for individuals: results are reported by team and role, and a no-blame policy keeps people reporting.

Deepfake voice and video are covered directly. We explain how a voice can be cloned from a few seconds of audio and how a video call can be faked, then teach the control that does not depend on detection: verify any new or changed payment instruction by calling a number you already hold, and require a second approver above a set limit. Our article "Deepfake-Proof Payments" sets out the callback method in detail, and the track record page includes an illustrative case of the same controls in a title company.

Technical controls and training work together. For Microsoft 365 tenants we use the platform's attack simulation tooling where licensing allows, and we tie lessons to the defenses we build: SPF, DKIM and DMARC at enforcement, phishing-resistant sign-in, and payment approvals the person who enters a wire cannot release. See "Business Email Compromise and Wire Fraud" for the closing-fraud pattern, and our Cybersecurity and Managed IT services for the controls themselves.

Results are measured. The two numbers we watch are click rate and report rate. Click rate should fall; report rate should rise faster, because a reporting culture catches attacks that filters miss. Quarterly reports show both by team, with the trend, and give your insurer, client or examiner evidence that training happens.

Packages

Phishing simulation

Realistic, authorized simulated phishing, link, attachment, credential-harvest and QR-code scenarios, sent on a schedule and tuned to each group. Staff who click get a short lesson at that moment, not a penalty.

Role-based training

Separate tracks for finance and accounts payable, executives and their assistants, the help desk, and new hires, because each group faces a different attack.

Callback verification and wire-fraud drills

We write the payment-change rule and then rehearse it: a staged request arrives, and the team practices the callback, the second approver and the escalation.

Deepfake voice and video awareness

What cloned voices and faked video calls look like in practice, why a familiar face is not proof, and the one control that still works when the fake is perfect.

A reporting culture

A one-click report button, fast feedback to every reporter and a no-blame policy, so the first person to see an attack becomes your early warning.

Metrics and reporting

Click rate, report rate, time to report and repeat-clicker trends by team and role, in a report your leadership, insurer or examiner can read.

Microsoft 365 integration

For Microsoft 365 tenants we use the platform's attack simulation tooling where your licensing includes it, so simulations, reporting and training sit with the tools your staff already use.

Payment-change callback flow

A request to change bank details is never acted on from the request itself. Someone rings the number already on file, a second person approves, the outcome is written down, and only then is the payment released or held. If any step fails, the old details stay in use.

Payment-change callback flowFlow chart in five steps: a payment-change request arrives; someone calls back on the number already on file; a second approver confirms; the change is recorded with who, when and which number; the payment is paid or held. A failure at any step leads to holding the payment, keeping the old details and escalating to the named owner.From request to payment1Change requestArrives by email,call or portal.2CallbackRing the numberalready on file,never the one inthe request.32nd approverA different personconfirms thechange.4RecordedWho, when andwhich numberwas called.5Pay or holdPay on new detailsonly if everystep has passed.Any step fails, or nobody can be reached: hold the paymentKeep the old details in use and escalate to the named owner.Illustrative control. The callback number comes from existing records, never from the request.

A wire change is never approved on the request alone

An email or a phone call can be forged, and a cloned voice or face can pass for a colleague. The request is held, the requester is called back on the number already on file, and a second approver signs off before the payment is released or rejected. Every step is logged.

A wire change is never approved on the request aloneA wire-change request arrives by email or voice call and may be a deepfake. The payment is placed on hold. A person calls back the requester on the number on file, not the one in the message. A second approver reviews the request. The payment is then released or rejected, and both outcomes are written to an audit log. Wire requestemail or voiceHoldno release yetCall backnumber on file2nd approverseparate personReleasepayment sentRejectescalate to securityAudit logwho, when, outcomeUrgent · new account detailsVoice can be cloned1 · request arrives; the sender is not trusted2 · hold: no payment on a message alone3 · call back the number on file, not the one in the message4 · second approver, then release or rejectOut-of-band verificationDual approvalEverything logged

Mail that keeps flowing

Incoming mail is authenticated and scanned before it reaches anyone, mailboxes are copied across three regions so a server failure goes unnoticed, and outgoing mail leaves signed and encrypted.

Mail that keeps flowingDiagram of enterprise email flow. Inbound mail from an internet sender reaches the MX edge server running Postfix, where SPF, DKIM and DMARC checks light up in sequence, then passes a spam and malware filter; a spam message is diverted to quarantine. Clean mail is delivered to a mailbox cluster, a database availability group with copies in three regions. On a loop the active server in region A fails and the copy in region B activates automatically, so the next message is still delivered. Outbound mail from the user's mailbox is DKIM-signed and sent over an encrypted TLS connection to the recipient. INBOUNDOUTBOUNDSenderInternetMX edgePostfixSPFDKIMDMARCThreat filterSpam · malwareQuarantineMAILBOX CLUSTER · DAGRegion ARegion BRegion CActiveCopyActiveCopyMailboxUser inboxDKIM signingTLS encryptedRecipientSPFDKIMDMARCSPFDKIMDMARCOffline

DMARC: from watching to rejecting

Share of mail claiming the domain that passes DMARC (SPF or DKIM aligned), week by week. In the monitoring phase (p=none) reports reveal forgotten senders; each one gets SPF and DKIM fixed. Quarantine sends failures to spam, reject refuses them at the receiving server. Illustrative figures.

DMARC: from watching to rejectingLine chart over 12 weeks. DMARC pass rate climbs from 61 percent in week 1 to 78 percent at the end of the p=none phase, 94 percent at the end of p=quarantine, and 99.1 percent in week 12 under p=reject.DMARC pass rate, 12 weeksp=nonemonitor onlyp=quarantinefailures to spamp=rejectfailures refused50%60%70%80%90%100%W1W2W3W4W5W6W7W8W9W10W11W1261%78%94%99.1%Week number on the x axis. Pass rate is measured on aggregate (rua) reports.

Our process

  1. 1

    Baseline

    A first simulation and a short review of your payment and access procedures, so every later number has a starting point.

  2. 2

    Train

    Short, role-based sessions and lessons, live or recorded, written around the attacks each group will actually see.

  3. 3

    Simulate

    Scheduled phishing and phone or video scenarios, with immediate coaching for anyone who falls for one.

  4. 4

    Drill

    Callback and wire-fraud exercises with the finance team and approvers, timed and written up.

  5. 5

    Measure

    Click rate and report rate by team, reviewed with you, with the next quarter's scenarios adjusted to the results.

We begin with a baseline simulation, train by role, simulate on a schedule, drill the payment process with finance, and review the numbers each quarter. Training packages are listed in our shop at /shop/, and a tailored program is scoped with you during a short call.

Frequently asked questions

Direct answers to the questions we hear most. Something else on your mind?

Send us a message
What is security awareness training?

It is training that teaches staff to recognize and report phishing, payment fraud, fake voices and other social engineering, and to follow procedures that stop the attack even when it looks real. Ours combines short lessons, simulated attacks and drills, and measures the result.

Will employees be punished for clicking a simulation?

No. A click triggers a short lesson, not a penalty. We encourage a no-blame culture because people who fear punishment hide mistakes, and a hidden click is the one that becomes an incident.

What do you train finance staff to do about wire fraud?

We give them a written rule: any new or changed payment instruction is verified by a callback to a number already on file, and large payments need a second approver. Then we rehearse it with staged requests so it is a habit by the time a real one arrives.

Do you cover deepfake voice and video?

Yes. We show how cloned voices and faked video calls are used in payment fraud and why you cannot rely on spotting them. The defense is a procedure, a callback and a second approver, which still holds when the fake is perfect.

Which metrics do you report?

Click rate, report rate, time to report and repeat-clicker trends by team and role. The report rate matters most: a rising report rate means staff are acting as your early warning.

Does it work with Microsoft 365?

Yes. Where your Microsoft 365 licensing includes attack simulation training, we configure and run it, so simulations, reporting and lessons live in the tools your staff already use. Otherwise we use a separate platform that fits your mail setup.

How do I buy it, and what does it cost?

Training packages are in our shop at /shop/, where pricing is shown. If you need something tailored to your industry or team size, contact us and we will scope it.

Talk to an engineer about Security Awareness Training

  1. 1

    Tell us what worries you

    Send the form, or call us if it is urgent.

  2. 2

    A senior engineer replies

    Usually the same business day.

  3. 3

    A confidential 30‑minute call

    With a security engineer, at no cost and with no obligation.

  4. 4

    Your written summary

    Your external exposure and the first three things we would fix.

Prefer to talk now? (305) 404-9404

Request your free assessment

A senior engineer replies, usually the same business day. Please do not put passwords or client data in the form.

Required

We use your details only to respond to you. See our privacy notice.

Do you know if your company is safe?

Speak with a security engineer today. The first assessment call is free and confidential.

CallFree assessment