Answer a security review question with the email count, filtering results, staff reports, clicks, device update status, and response findings.
Key takeaways
- Ask security for counts over a defined period.
- Separate messages stopped by filtering from reports and clicks.
- Check device update status and response findings before offering reassurance.
- Name an owner and a time for the next update.
Sooner or later, a security or IT leader may ask for five minutes on a forecast or deal-review call. The question is usually some version of this: "Have we seen suspicious email that could affect this quarter?" It tends to arrive when the agenda is already crowded with pipeline, close dates, and discount requests. You do not need to be a security engineer to answer it well. You need a few facts, a plain sense of what they mean, and a clear statement of what happens next.
This post uses one public reference point: a case study from the UK National Cyber Security Centre (NCSC). Its numbers make a useful script, because each one answers a question a revenue leader is likely to hear: how much arrived, how much got through, and what it took to fix.
Treat the case study as a guide to what to ask, not as a description of your own risk. Your company's numbers will be different, and one campaign tells you little about your organisation as a whole. Use the six figures below to know which questions to put to your security team before the call.
Why does this land on a revenue leader? Because security incidents rarely stay inside the security team. A suspicious email that reaches a sales rep can touch a customer thread, a pricing document, or a signature request. A customer's procurement team may ask about it during their own review. The question on your call is often the first sign that someone wants a straight answer before the forecast is locked.
Figure 1: 1,800 emails
The NCSC describes a company which has around 4,000 employees that received 1,800 emails containing a number of variants of Dridex malware. Scale is the first thing to pin down. How many suspicious messages arrived, and over what period?
Ask for a count, not an example. One phishing email forwarded to someone on the team is an anecdote. A count over a defined period is a picture. With a count, you can say whether the message in question was one of a handful or part of a wave, and that changes how seriously the room should take it.
Be precise about what the number covers. The case study counts emails containing malware. That is a specific kind of attack, not every phishing message your company receives. On the call, say "emails that carried malware" and let security define the category. Do not round it up to "our phishing problem" unless the count supports that description.
Figure 2: 1,750 stopped by a filter
The second figure is the one that usually reassures a room. The case study reports that 1,750 were stopped by an email filtering service that identified that malware was present. Most of the emails were stopped by that service.
That matters for the call because it shows the first line of defence is technical. People are not expected to catch every message on their own. A filter that identifies malware is one layer among several, and it is worth knowing whether your company has one and whether it works.
Ask your security team two things. First, did our email filtering catch this, and what did it identify? Second, what share of suspicious messages was stopped before delivery? Do not promise a percentage you have not been given. If the answer is a range or "we don't know yet," say exactly that. An honest gap reported on the call is far better than a comfortable guess that a customer later disproves.
Figure 3: 36 ignored or reported
This figure combines two user responses. The case study says that of these, 36 were either ignored by users, or reported using a button in their email client. It does not give a separate count for each response.
For a revenue leader, this is the number to bring up if the call turns to whether people are being careful. Ask whether your email client has a report button and whether people use it. If they do, say so with the detail. If you don't know, say that instead. "We have a report button and our team uses it" is only worth saying if it is true.
Reporting also helps the security team more than it might seem. A reported message gives them something to check across the whole company, not just in one inbox. Ignoring a message does not alert colleagues to check for other copies. Ask whether reports are reviewed and how quickly. That is a question you can ask without sounding like a technical expert.
There is also a cultural point in this number. Make it clear on the call that a report is a good outcome, even when the message turns out to be harmless. Ask whether the company has said that in writing.
Figure 4: 14 clicked
Here the case study gets harder. The NCSC says that this left 14 emails that were clicked-on, which launched the malware. Fourteen clicks is the number that makes a call uncomfortable, and it is the one most likely to start a conversation about blame.
Keep the response free of blame while checking business risk and possible training or process gaps. Did the company find out quickly? Did anyone know who to tell?
Think about the practical version. A rep receives a message that looks like a note from a long-standing customer, with a link to updated terms. They click before they think. If they report it right away, the company has a chance to check the other copies in other inboxes and to warn colleagues. If they say nothing for a week because they are embarrassed, the same message can keep working on people who have not yet seen it.
So when you bring up this figure, shift the question from "who clicked" to "how fast did we know, and who was told?" Ask whether the company has a single place to report a click, and what happens after someone reports one. If the answer is unclear, that is the finding to take into the next planning cycle. It is not a personal failing to name on the call.
Figure 5: 13 failed to launch
The reassuring figure in the case study is this one. The NCSC notes that 13 instances of the malware failed to launch as intended due to devices being up-to-date.
This is the point to make about patching. Updates are not exciting, and they are easy to defer. A revenue leader can ask a simple question on the call: are the laptops and phones that our sales and finance teams use kept up to date?
Be careful with the logic. This figure does not say updates stop every attack, and it does not say every click will fail. Use it to make the case for checking patch status, not to claim that patching is a guarantee.
Figure 6: 1 device seized and cleaned
The last figure is about response. The case study records that 1 device was seized, investigated and cleaned in a few hours.
When a security question comes up on a deal call, the instinct is to ask "were we breached?" Also ask "what do we know about the scope and impact, and what did we learn?" If the company has a clear incident process, a named owner, and a record of past responses, those are facts you can share. If it doesn't, that is the gap to raise.
Ask when the response process was last tested, and who owns it. Ask whether the sales and customer teams know who to contact if a customer asks about a suspicious email. Those are concrete questions, and each one has an answer your security team can give in a sentence or two.
Prepare in ten minutes
Before the call, send one message to your security lead. Ask for six things, one for each figure above: the total number of suspicious emails in the period you are discussing, how many were stopped by filtering, how many were reported by staff, whether any were clicked, whether the affected devices were up to date, and how the response was handled and when it closed.
You do not need the technical detail. You need the shape of the story. If your security team cannot answer in a day, say so on the call and agree on a date for the answer. A date you can keep is more useful than a precise number you cannot defend.
Also check your own team's exposure. Sales and finance teams receive many messages that look like deal paperwork, invoice requests, or shared documents. Ask whether anyone in those teams has reported a message that matched that pattern in the last few weeks. If the answer is yes, the security team already has a lead. If the answer is no, that is useful information too, because it may mean people are not reporting what they see.
Where a security question hits the forecast
An incident does not have to be large to affect a deal. The practical effects tend to show up in the commercial process rather than in the security report. A customer may send a security questionnaire that now needs a careful answer. A procurement team may ask for more time before they sign, while they check what they have been told. Legal may ask that certain email threads be kept unchanged while a review is open, which can slow down how quickly your team moves documents around.
Internal changes can also affect timing. Security may ask to restrict access to a shared folder, pause a particular workflow, or require a fresh check before an approval goes out. Each of those steps is reasonable, but none of them is free. A revenue leader should ask, on the call, which deals or workflows might be affected and when the security team expects to know more.
Treat each of these as a forecast input, not a surprise. Note which deals involve the teams that handled the suspicious email, which ones are close to signature, and which customers have asked about security in the last few months. Use a close date change log to record why timing moved.
What to say on the call
Keep your part short. You are not expected to explain the malware. You are expected to answer four things: what happened, what is known, what is not known, and what happens next. Here is a structure you can use:
- What we saw. "We received a number of suspicious emails in that period. Security has the count and the actions taken." Use the real count if you have it, or say you will send it.
- What got stopped. "Our filtering stopped most of them before anyone opened them." Say this only if your filter data supports it.
- What we don't know. "We are still checking whether any devices were affected." Saying this is more credible than saying nothing is wrong.
- What happens next. "Security will update us by a date we agree on, with the findings and any impact on customer data or timelines."
Then connect the incident to the business. Ask whether the issue touches customer data, the systems the deal depends on, or the timing of a close. If it does, those are risks to log, not to wave away. Ask for a short written summary after the call so that the forecast and the security notes match. Keep that summary with your deal review context.
Illustrative example: counts and unanswered questions
The difference is 0 emails outside that filtering count. On the call, report those figures as illustrative filtering results, then ask about incident scope, device findings and customer impact. Do not turn the arithmetic into a claim that the company is unaffected.
What not to do
Do not present a case study number as your company's own data. And do not forward a suspicious email to the call, to a customer, or to a colleague who might click it. If you need to show an example, ask security for a version with the links removed.
Keep the response proportionate
Close with the balance the NCSC itself strikes. Its guidance is framed around improving resilience against phishing while minimising disruption to user productivity. That is the right test for a revenue leader too.
When the security question arrives on a forecast or deal-review call, you do not need to have every answer. You need the right questions, the numbers that exist, and a plan to get the rest.
Today, draft the request to your security lead using the six questions above, and leave any unanswered item clearly marked as unknown.
The question you will get
Can these figures describe our company's risk?
No; they describe one organisation's experience, so use your own security findings when discussing company risk.
Does a filtering count prove we are unaffected?
No; reassurance also requires evidence about incident scope and impact.
What should I say when findings are incomplete?
State what remains unknown and agree who will provide the next update and when.