A security gap analysis compares what an organization has against what a standard says it should have. Done from a checklist, it produces a long list of missing controls with no order and no argument. Done from an incident, it produces a short list where every recommendation points at a specific failure. The second kind is the one leadership funds.

The method is to reconstruct the attack as an ordered chain of steps, ask at each step which control would have prevented, detected, or contained it, then scope the answer to the organization’s size. This article walks through that method using the Center for Internet Security’s CIS Controls v8, with a worked example at the end.

Why start from an attack chain

Frameworks are organized by control, not by attack. CIS Controls v8.1 has 18 controls and 153 safeguards. Assessing all of them against an environment is a real exercise, but it answers “what do we lack” rather than “what would have stopped this”. An attack chain reverses the direction. You start from what happened, or from a realistic scenario, and work out which safeguards sat at each step.

Two public models give you the vocabulary. Lockheed Martin’s Cyber Kill Chain describes an intrusion in seven steps from reconnaissance to actions on objectives. MITRE ATT&CK is more granular: its enterprise matrix currently lists 15 tactics, from reconnaissance and initial access through lateral movement, exfiltration, and impact. You do not need to use either formally. What you need is the habit of writing the incident as a sequence in which each step depended on the one before it.

The method in five steps

  1. Write the chain. Turn the incident narrative, or the scenario, into numbered steps. Each step is one thing the attacker did or one thing the defenders failed to do. Keep the human steps in: a ticket handled as routine, a device left on over a weekend. Those are gaps too.
  2. Name the failure at each step. For every step, state in one sentence what allowed it. “The wireless network issued an address to a device that was not in the inventory.” That sentence is the gap.
  3. Map each failure to a control and its safeguards. Use the CIS Controls Navigator to find the control that addresses the failure, then the specific safeguards under it. A failure usually maps to one control and two or three safeguards.
  4. Scope to the Implementation Group. CIS sorts safeguards into IG1, IG2, and IG3 by organizational size and risk. Decide which group the organization is in before recommending, then limit the list to that group plus any higher-group safeguards the facts of the case justify.
  5. Sort into prevent, detect, respond. Each recommendation does one of three jobs. Grouping them that way shows whether the analysis has balance, and it makes the case for response controls, which are the ones most often skipped.

A worked example

The case study linked below reconstructs a scenario in which an employee connected an infected personal laptop to corporate Wi-Fi. The chain ran to 12 steps. The laptop was issued an internal address without checks, scanned the network, found an FTP server that allowed anonymous access, compressed proprietary files, and pushed them out through an encrypted VPN. The network operations center saw the large transfer and logged it as a help desk ticket. The employee noticed the laptop was slow on Friday and left it running through a three-day weekend.

Mapping each step produced 10 controls and 27 safeguards. The table shows a sample of how the mapping reads when it is done from the evidence.

Sample attack-chain steps mapped to CIS Controls v8 safeguards
Step in the chainGapCIS Control and safeguards
Unmanaged laptop joins corporate Wi-FiNo authoritative asset inventory; no process to deny unknown devices01 Inventory and Control of Enterprise Assets: 1.1, 1.2 (IG1), 1.3 (IG2)
Laptop reaches an anonymous FTP serverUnnecessary service enabled; no access control list on sensitive data04 Secure Configuration: 4.1 (IG1), 4.8 (IG2). 03 Data Protection: 3.3 (IG1)
Command-and-control connection succeedsMalicious-site reputation list four months old09 Email and Web Browser Protections: 9.2 (IG1), 9.3 (IG2)
Large encrypted transfer handled as a routine ticketNo central alerting, no designated incident handler, no reporting path13 Network Monitoring and Defense: 13.1 (IG2). 17 Incident Response Management: 17.1, 17.3 (IG1)

The organization sat between IG1 and IG2, so the recommendations used all relevant IG1 safeguards plus the IG2 safeguards the facts justified. Of the 27, 11 were IG1 and 16 were IG2. That split is itself a finding: the basics were mostly missing, and the next tier was needed for detection.

What the attack-chain method catches that a checklist misses

  • Response gaps. In the example the transfer was detected. The failure was that nobody had authority to isolate a device on a weekend. A checklist marks “monitoring: yes” and moves on. The chain shows detection without response is worth little.
  • Compounding failures. Stale reputation data, open FTP, and flat network segments were each minor on their own. In sequence they turned a slow laptop into data theft. The chain shows how small gaps multiply.
  • Human steps. Awareness training (CIS Control 14) rarely tops a checklist. In the chain, two people saw warning signs and did not escalate. Training recommendations become specific: role-based training for help desk staff on what unusual traffic means.
  • Priority. A recommendation that would have broken the chain at step one outranks one that would have helped at step nine. The order falls out of the analysis instead of being argued afterwards.

Common mistakes

  • Recommending every safeguard in a control. If the failure was anonymous FTP, the fix is 4.8 (uninstall or disable unnecessary services), not all of Control 04.
  • Ignoring the Implementation Group. Recommending IG3 safeguards to a 40-person company guarantees the report is shelved.
  • Stopping at prevention. Every chain should produce at least one detection and one response recommendation, because the next attack will take a path you did not model.
  • Writing the rationale last. Each safeguard should carry the sentence from step two of the method, the one that names the failure. If you cannot write that sentence, the safeguard does not belong in the report.

Frequently asked questions

What is a security gap analysis?
A comparison of the controls an organization has in place against the controls a chosen standard or framework expects, producing a list of missing or weak controls and a plan to close them.
What is the difference between a gap analysis and a risk assessment?
A gap analysis measures distance from a standard. A risk assessment estimates the likelihood and impact of specific threats. A good gap analysis uses risk to order its findings, which is why starting from an attack chain helps.
Which framework should I use for a gap analysis?
Use the one your organization is measured against. For a small or mid-sized organization with no mandate, CIS Controls v8 is a practical choice because its Implementation Groups scale the list to your size.
How many steps should an attack chain have?
As many as the evidence supports. The example in this article has 12. Shorter chains are fine for simple incidents. What matters is that each step names one action or one failure.

Sources