Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Cybersecurity & Risk 6 min read

Phishing prevention for employees: a working checklist

A copy-ready phishing prevention checklist with owners, evidence, review frequency and sign-off for each control.

E
EncryptTechBD · 0 comments
Person working on a laptop
Photo: Burst / StockSnap

A phishing programme fails quietly. The training is completed, the slides are stored, and six months later an accounts assistant approves a supplier bank change because the email looked exactly like the last twenty. The difference between a programme and a certificate is a set of controls that someone owns, checks and signs.

This checklist is designed to be copied into an operations manual. Every line has an owner, the evidence it should produce, how often it is reviewed and who signs it off. Replace the role names with your own, but do not leave a field blank. A checklist with no evidence is a wish list.

1. Map the people and the money

Phishing prevention is not evenly distributed. A junior designer and a finance manager do not face the same consequences. Start by identifying where a successful message would cause the most damage.

  • Role and access map. List every role that can approve a payment, change a supplier bank account, release payroll, issue a refund or export customer data. Owner: operations lead. Evidence: role register with approval limits. Frequency: every six months and on promotion. Sign-off: finance director.
  • Supplier and payment list. Record which suppliers are paid by bank transfer, which staff can amend those details and which channel confirms a change. Owner: finance manager. Evidence: supplier master with change history. Frequency: quarterly. Sign-off: finance director.
  • High-risk scenarios. Write the five messages most likely to reach your team: fake invoice, bank-detail change, executive request, delivery failure, payroll or tax notice. Use real wording from your industry, not generic examples. Owner: security lead. Evidence: scenario list used in simulations. Frequency: annual refresh. Sign-off: business owner.

2. Give every employee a reporting path they trust

The fastest control is a report button that reaches a person, not a void. If reporting is difficult or embarrassing, people delete the message and hope.

  • One reporting address. Publish a single mailbox or button for suspicious messages, reachable from desktop and mobile. Owner: IT lead. Evidence: published address and screenshot of the button. Frequency: tested monthly. Sign-off: operations lead.
  • Triage routine. Define who reviews reports, how quickly, and what they do with a confirmed phish: block the sender, search for other recipients, reset credentials if needed. Owner: IT lead. Evidence: triage log with timestamps and actions. Frequency: every report. Sign-off: monthly review.
  • Feedback to the reporter. Tell the person what happened. A short confirmation that the message was blocked keeps the habit alive. Owner: IT lead. Evidence: response template and sample replies. Frequency: every report. Sign-off: quarterly.
  • No-blame rule. State in writing that reporting a mistake is protected and that punishment is reserved for concealment. Owner: HR lead. Evidence: policy clause acknowledged by staff. Frequency: annual acknowledgement. Sign-off: business owner.

3. Run a baseline before you train

Training without a baseline becomes a completion exercise. A short simulation and a knowledge check show where the team actually starts.

  • Baseline simulation. Send a realistic message to all staff or a representative group. Record report rate, click rate and time to first report; do not publish individual results. Owner: security lead. Evidence: aggregate baseline report. Frequency: once, then quarterly. Sign-off: operations lead.
  • Knowledge check. Five to ten questions on reporting, payment verification, attachments and urgent requests. Owner: HR or learning lead. Evidence: scores by team, not by name. Frequency: at induction and annually. Sign-off: operations lead.
  • Role-based modules. Finance, admin, sales, support and technical staff need different examples. A generic module for everyone wastes the finance team’s attention and misses the risks that matter. Owner: security lead. Evidence: module map by role. Frequency: annual review. Sign-off: business owner.

4. Put payment changes behind a second channel

Most damaging phishing in small businesses is not a password theft. It is an invoice or bank-detail change that redirects a legitimate payment. Awareness helps, but a callback rule is stronger.

  • Callback verification. Any change to supplier bank details requires a call to a known number, not the number in the email. Owner: finance manager. Evidence: signed verification note on the supplier record. Frequency: every change. Sign-off: finance director.
  • Dual approval. Payments above an agreed threshold need two named approvers, with the approval recorded in the finance system. Owner: finance director. Evidence: approval log. Frequency: every payment. Sign-off: monthly reconciliation.
  • Callback test. Once a quarter, test whether the rule is followed by asking a supplier to confirm details through the published process. Owner: internal audit or finance manager. Evidence: test result and corrective action. Frequency: quarterly. Sign-off: finance director.

5. Keep the technical floor in place

Training cannot compensate for a domain that allows anyone to send as you. These controls reduce the volume of phishing that reaches an inbox, which makes the human control easier to sustain.

  • Email authentication. Publish SPF, DKIM and a DMARC policy and review aggregate reports. Owner: IT lead. Evidence: DNS records and DMARC report review. Frequency: quarterly. Sign-off: operations lead.
  • Multi-factor authentication. Require MFA on email, finance, payroll and remote access, with phishing-resistant methods where supported. Owner: IT lead. Evidence: coverage report by system. Frequency: monthly. Sign-off: operations lead.
  • Filtering and attachment controls. Block or isolate risky file types and links, and log what was blocked. Owner: IT lead. Evidence: rule list and blocked-item summary. Frequency: quarterly. Sign-off: operations lead.

6. Review the programme, not just the completion rate

Once a quarter, sit down with the evidence pack and ask four questions: did reports reach the right person, did the team improve on the scenarios that matter, did any payment-change rule fail, and what changed in the threat landscape or the business?

Record the answers and the actions. A review that produces no change is a meeting, not a control. The sign-off should sit with the business owner because the decisions that follow — releasing staff time, approving a payment rule, funding a technical control — are management decisions, not IT preferences.

First 30 days

  1. Name one owner for the programme and one backup.
  2. Complete the role and supplier maps.
  3. Publish the reporting address and test it from a phone.
  4. Run a small baseline simulation and share aggregate results.
  5. Put the callback rule in writing and brief every approver.
  6. Book the quarterly review with a named sign-off.

If you need help turning this into an operating routine, start with Managed Technology & Cybersecurity. The pricing page explains how assessments and ongoing support are scoped. For the budget side of the same programme, read what a phishing prevention programme actually costs.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes