The problem: A large client sends a security questionnaire before signing a contract. One question asks: “Is a second sign-in step required for all staff?” The governance, risk and compliance team (GRC) reads the policy, which says yes, and ticks Yes. The IT operations team knows that about 40 contractors have not been moved over yet. Nobody asked them.
Words used here: GRC is the team that handles governance, risk and compliance. A questionnaire is a long list of security questions a client sends to a supplier. A second sign-in step (also called multi-factor authentication) means a password plus something else, like a code on a phone. A contractor is someone who works for the company but is not an employee.
Think of a menu that says “fresh daily”
A restaurant menu says the fish is fresh every day. The waiter, who has only read the menu, tells a customer, “Yes, always fresh.” The cook knows that on Mondays the fish comes out of the freezer. The waiter is not lying. He is repeating what is written. The cook knows the truth and was never asked.
The GRC team is the waiter. IT operations is the cook. The questionnaire is a menu the client will hold the company to.
What it looks like at work
The policy was approved a year ago and says the second sign-in is required for all staff. Since then, most employees have been moved over, but 40 contractors on a different system have not. These are example numbers. The GRC analyst has forty questions to answer by Friday, and answers each one from the policy because it is the quickest source.
The client signs. Eight months later, the client’s own auditor tests a contractor account. It has no second step. The client says the answer on the form was wrong, and points to a clause in the contract about accurate information.
- 11. Policy says yesSecond sign-in for all staff
- 22. Gap in practice40 contractors not yet moved over
- 33. Form due FridayAnswered from the policy, not the system
- 44. Client signsTrusting the ticked Yes
- 55. Audit finds itContract clause on accurate answers
Both teams have a fair point. GRC has hundreds of questions and a deadline, and the policy is the only approved source. Operations knows the real state but is rarely consulted and, honestly, has its own pile of work. Neither side set out to mislead the client. The process has no step where the person who runs the control sees the answer.
You will notice it when:
- Answers are written from the policy and not from the system.
- The people who run the controls never see the questionnaire.
- A “Yes” comes with no date, no scope, and no evidence.
- The same question is answered differently on two forms.
- Operations learns what was promised only when the client asks for proof.
What exactly needs fixing
The fix is not to answer “No” more often. It is to let the person who runs the control read the answer before it goes, and to give GRC an honest middle answer: “Partly, with a plan and a date.” This card shows the whole problem on one page:
The questionnaire says a second sign-in step is required for all staff, but about 40 contractors do not have it.
The client questionnaire, answered from the policy and not from IT operations.
A breach linked to a gap the company said did not exist.
- Possible contract breach
- Lost client
- Sales loses trust
- Weeks of rework
- 11. Ask the ownerSend each answer to the person who runs the control first
- 22. Answer honestly“Partly. Staff done, contractors by 30 June.” Keep the date
- 33. Keep an answer bankChecked answers with owner and date, re-checked every 6 months
Who fixes it: GRC lead and IT operations lead
By when: before the next questionnaire
A blank copy of this card is in the Tools section.
Why it happens
- Policy and practice drift apart. The policy says what should be true. The system says what is true.
- The deadline is short. The client wants the form in days.
- “Yes” is the answer that closes the deal. There is quiet pressure from sales.
- GRC does not know who owns each control. So it does not know whom to ask.
- There is no honest middle answer. The form offers Yes or No, and Yes feels safer than No.
What happens if you ignore it
A small gap on a form becomes a contract problem.
- The client can say the supplier gave false information.
- A later incident, linked to the gap, looks like a broken promise.
- The sales team loses trust in the security team’s answers.
- Every future form takes longer, because each answer has to be re-checked.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Likely, wherever answers come from policy and not from practice. |
| Worst case? | A breach linked to a gap the company said did not exist. |
| What does it cost? | A possible contract breach, a lost client, and weeks of rework. |
| What if we wait? | The next form repeats the same Yes. |
| What does the fix cost? | A named owner per control and a sign-off step. |
How to fix it, step by step
Ask the owner, answer honestly, then keep a bank of checked answers.
- List the controls clients ask about most. Second sign-in, backups, patching, logging, staff training.
- Name one owner for each. The person who actually runs it, not the person who wrote the policy.
- Send each answer to its owner before the form goes. A short message: “Is this true today? Yes, partly, or no?”
- Offer an honest middle answer. “Partly. Done for staff. Contractors by 30 June.”
- Attach a date to every partial answer. And then keep the date.
- Build an answer bank. One checked set of answers, with the owner’s name and the date they last confirmed it.
- Re-check the bank every six months. Or whenever a control changes.
The picture shows the order: ask the owner, answer honestly, then keep a bank. The bank saves time on every later form, which is how the habit sticks.
Who to bring in: The GRC lead (runs the process), each control owner (confirms the answer), the sales lead (agrees that “Partly” is acceptable to say), and legal (reviews wording on high-value contracts).
Tools and templates
Answer bank
| Question | Today’s honest answer | Owner | Last confirmed | Next check |
|---|---|---|---|---|
| Second sign-in for all staff? | Partly. Employees yes, contractors by 30 June | IT operations lead | This month | In 6 months |
| Backups tested? | Yes, quarterly | IT operations lead | This month | In 6 months |
| Staff security training? | Yes, yearly, 96% done | HR lead | This month | In 6 months |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a failed audit, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to the control owner
Subject: Checking a questionnaire answer before it goes
Hi. We have a client questionnaire due Friday, and one question is whether the second sign-in is required for all staff. Our policy says yes, but I want to check with you first. Is that true today, partly true, or not yet? If it is partly, I would like to say so with a date. Can you reply by Wednesday? I would rather be accurate with the client than tidy.
Field tip
Before you tick Yes, ask yourself: “Who would know if this is not true?” Then ask that person.
Words used in this chapter
- GRC: the team that handles governance, risk and compliance.
- Questionnaire: a list of security questions a client sends to a supplier.
- Second sign-in step: a password plus something else, like a phone code.
- Control owner: the person who actually runs a safeguard.
- Answer bank: a checked set of answers that can be reused.
- Contractor: someone who works for the company but is not an employee.