Skip to content
All articles
September 4, 2026 12 min read

The Control Matrix: Four Categories, Six Types, and the Security+ Question You Will See Five Times

Chris Rees

Chris Rees

25+ years in IT · Pluralsight author, 4.6/5 across 2,000+ ratings

The Control Matrix: Four Categories, Six Types, and the Security+ Question You Will See Five Times
www.skillthropic.com

Objective 1.1 is the first thing on the Security+ outline and the source of more silly lost marks than any other. The question shows you a control in one sentence: a guard, a backup, a policy, a warning sign. The answers are four real terms. Candidates who studied the definitions still get it wrong, because the outline hides two separate questions inside one: who implements the control, and what it does. Split them, and the whole objective turns into a grid you can draw from memory.

Two axes, one grid

Security+ classifies every control twice. The category is about the nature of the control and who owns it. The type is about its function, what it does to a threat and when. Every control has exactly one category and at least one type, and the exam will happily ask about either axis using the same example.

The categories are four:

Category What it is Owned by Examples
Technical implemented by systems and software engineers, administrators firewall, encryption, MFA, IDS
Managerial administrative oversight of the program leadership, risk, compliance policy, risk assessment, awareness program
Operational carried out by people in day-to-day work staff, operations teams guard patrols, backup rotation, log review
Physical protects the tangible world facilities, physical security fence, lock, badge reader, bollard

The line candidates blur is technical versus operational. A tool is technical. A person using a tool as part of a routine is operational. An intrusion detection system is a technical control; the analyst reviewing its alerts every morning is an operational one. Physical is the easiest to spot and the one the exam uses least, precisely because it is easy.

Types: what the control does, and when

The types are six, and the tidiest way to hold them is by their relationship to the moment of attack.

A timeline of an attack showing which control types act before it, during it and after it: directive and deterrent shape behavior in advance, preventive blocks the attempt, detective identifies it in progress, corrective restores afterwards, and compensating substitutes when the primary control is unavailable SIX TYPES ON ONE TIMELINE the attack BEFORE DURING AFTER Directive tells people what to do policy, AUP, signage Deterrent discourages the attempt warning sign, visible camera Preventive stops it from succeeding at all firewall, lock, MFA, encryption Detective identifies it in progress IDS, logs, motion sensor Corrective restores after damage restore, patch, reimage Compensating substitutes when the primary control is not possible segmentation for an unpatchable system Compensating is not a point on the timeline. It is a replacement for any other type, and it exists because the primary control could not be applied.
Directive and deterrent work on people before the attempt; preventive blocks the attempt; detective sees it happening; corrective cleans up. Compensating sits outside the timeline as a stand-in.

Two pairs cause nearly all the errors on this axis.

Deterrent versus preventive. A deterrent works on the attacker's decision. A preventive control works on the attacker's ability. A sign that says "premises under surveillance" is deterrent; the lock on the door is preventive. If the attacker ignores the deterrent nothing stops them; if they ignore the preventive control they still cannot get in. On the exam, anything that reduces willingness rather than capability is deterrent.

Corrective versus compensating. Corrective controls fix damage after an incident: restore the backup, reimage the host, apply the patch that was missing. Compensating controls replace a control you cannot implement at all. The medical device that cannot be patched gets network isolation instead; the small team that cannot separate duties gets extra logging and review. The word that signals compensating in a stem is some version of "cannot": the system cannot be patched, the vendor does not support MFA, the budget does not allow a second administrator.

The grid

Put the axes together and every control lands in one cell. The exam does not require you to memorize the grid, but drawing it once makes the classification questions mechanical, because you stop searching for a single right word and start answering two easy questions instead.

A grid of control categories across the top, technical, managerial, operational and physical, against control types down the side, preventive, deterrent, detective, corrective, compensating and directive, with one example control in each cell ONE EXAMPLE PER CELL Technical Managerial Operational Physical Preventive firewall, MFA hiring screening guard at the door lock, bollard Deterrent login warning banner sanctions policy visible patrols warning signs Detective IDS, SIEM alerts audit, access review daily log review motion sensor Corrective backup restore, patch incident response plan reimaging a host fire suppression Compensating isolating a legacy host extra review, no SoD manual checks, no tool guard, broken lock Directive config that enforces policy acceptable use policy training, procedures exit-only signage Rows answer "what does it do." Columns answer "who implements it." Every scenario is a cell.
Twenty-four cells, and the exam only ever asks about one at a time. Once you can place a control on both axes, the answer is whichever axis the question is actually asking about.

Notice that a single control can be more than one type. A visible camera is deterrent (it discourages) and detective (it records). A backup is corrective when restored and preventive of data loss when taken. The exam handles this by asking for the best or primary classification given the scenario, which brings us to the method.

Reading the stem: the verb decides

Most objective 1.1 questions can be answered by finding one verb in the stem and ignoring the noun.

  • Stops, blocks, prevents, denies point to preventive.
  • Discourages, warns, makes less attractive point to deterrent.
  • Identifies, alerts, logs, discovers, notices point to detective.
  • Restores, repairs, recovers, returns to normal point to corrective.
  • Instead of, because it cannot, as an alternative point to compensating.
  • Requires, mandates, instructs, tells employees to point to directive.

Then ask who implements it. Software or hardware doing it automatically is technical. Leadership deciding it is managerial. Staff doing it as a routine is operational. Anything you could kick is physical.

Worked example: "An organization cannot apply vendor patches to a manufacturing controller, so it places the controller on an isolated VLAN with a monitored gateway." Verb: cannot, so this is compensating. Who: the isolation is implemented by network equipment, so technical. Answer: technical compensating. Notice that the VLAN is also preventive in function; the question wants compensating because the stem is built around what could not be done.

Which type protects which property

The grid also connects to the triad. Objective 1.2 gives you confidentiality, integrity and availability, and the control types map onto them in a way that helps with selection questions. Confidentiality is mostly protected by preventive controls (encryption, access control) and checked by detective ones (access logs, DLP alerts). Integrity leans on detective controls to notice change (hashing, file integrity monitoring) and corrective ones to reverse it (restore from a known-good copy). Availability is where corrective controls do most of the work (failover, backups, redundant power) and where preventive controls look like capacity planning. Non-repudiation is almost purely detective: digital signatures and audit trails exist to prove after the fact who did what.

When a question asks you to pick a control for a stated property, this mapping narrows the answers before you read them. A stem about proving a transaction happened wants a detective control for non-repudiation, not a preventive one for confidentiality, however strong the encryption in the distractor sounds.

Five scenarios, answered in two steps

Practice the method on the shapes the exam actually uses.

  1. A bank posts a notice that all transactions are logged and reviewed. Verb: discourages. Owner: management wrote the notice. Managerial deterrent. (The logging itself would be technical detective, but the stem is about the notice.)
  2. A hospital installs badge readers on every ward door. Verb: blocks. Owner: hardware on a door. Physical preventive.
  3. After a breach, the team restores a database from the previous night's backup. Verb: restores. Owner: staff performing a procedure. Operational corrective.
  4. A firm cannot enforce separation of duties in a two-person finance team, so every payment is reviewed by the CFO. Verb: cannot, therefore instead of. Owner: a management-imposed review. Managerial compensating.
  5. A new hire is required to complete security training before receiving credentials. Verb: requires. Owner: policy and HR process. Managerial directive, delivered operationally.

Notice how often the category is the harder half. Candidates find the type in the verb quickly and then guess the category from the noun, which is why example five trips people: training feels operational, but the requirement that creates it is managerial.

Why the grid is the foundation of the exam

The rest of Security+ is, in a sense, a long list of controls, and every later objective assumes you can place them. Zero Trust is a set of preventive and detective technical controls arranged around identity. A PKI is a preventive technical control for confidentiality and a detective one for integrity. An incident response plan is a corrective managerial control until the moment it is executed, when it becomes corrective operational. When a Domain 4 or Domain 5 question asks what kind of control something is, it is testing objective 1.1 again with a harder example.

That is also why the outline lists the categories and types first. Everything after them is about selecting the right control for a risk, and you cannot select what you cannot classify.

Key takeaways

  • Two axes, two questions. Category says who implements (technical, managerial, operational, physical); type says what it does (preventive, deterrent, detective, corrective, compensating, directive).
  • Deterrent works on willingness; preventive works on ability. If ignoring it still lets the attacker in, it was a deterrent.
  • Corrective fixes damage; compensating replaces a control you cannot have. The word "cannot" in a stem is the compensating signal.
  • Technical is the tool; operational is the person using it. An IDS is technical, the analyst reading it is operational.
  • Find the verb, then find the owner. Most 1.1 questions resolve in two steps and ten seconds.

Control categories and types are objective 1.1 of Security+ Domain 1, General Security Concepts, the foundation every later domain assumes. Work all 22 Domain 1 topics, from the CIA triad and change management through every cryptographic solution on the exam, with our free Security+ Domain 1 study guide.

#SecurityPlus #SY0701 #SecurityControls #ControlTypes #CompensatingControls #DefenseInDepth #ExamPrep #CompTIA #InfoSec #CyberSecurity

Share this article

Keep reading

Security+ deep dives

Reflected or Amplified, Spraying or Brute Force: The Non-Malware Attacks Security+ Asks You to Name From the Indicators

Objective 2.4 is the biggest objective in Domain 2 and it runs in reverse: the stem hands you an indicator and asks for the attack. Beyond malware, that means five families sorted by target: physical, network, application, cryptographic and password. Each family taken to the discriminator the exam tests, reflected versus amplified, replay versus credential replay versus forgery, spraying versus brute force, collision versus birthday, then the nine indicators reversed into the attacks they point to.

Read
Security+ deep dives

Approval, Backout, Maintenance Window: Why Security+ Calls Change Management a Security Control

Change management reads like an IT operations topic until you notice where CompTIA put it: Domain 1, beside the control types and the CIA triad. Objective 1.3 in full: the business process from request to documentation, who owns a change versus who is affected by it, the seven technical implications and the question each one forces, why a patch is not a fix until the service restarts, and the version control habit that turns every change into evidence.

Read
Security+ deep dives

Secure Network Architecture: Zones, Device Placement, Firewalls vs. IDS/IPS, and Secure Protocols

Where you put a control decides what it can do. A Security+ deep dive on network design: security zones and the screened subnet, inline vs. tap and active vs. passive placement, fail-open and fail-closed, the four firewall generations, IDS vs. IPS, and the secure protocol and port swaps the exam expects on sight.

Read

Enjoyed this? Get the AI security news that matters.

Join The AI Security Brief for the top AI security news, plus what's important to the C-suite. Free, straight to your inbox.

No spam. Unsubscribe anytime.

Security+ Domain 1 · general security concepts

Build the foundation first

Zero Trust is one of 22 topics in Security+ Domain 1, the foundation the rest of the exam builds on. Master all 4 objectives, from control categories through cryptography, with our objective-mapped guide and 60 practice questions.

Get the Domain 1 guide