Insights
How to evaluate a managed security provider, using the NIST framework
One yardstick for security providers: the six NIST functions. A 40-service map, EDR to RIR compared, patching, testing, who answers when it goes wrong, and 19 questions to put in writing.
You can compare security providers on one yardstick: the six functions of the NIST Cybersecurity Framework. For each function, ask who does the work, what they are allowed to do, and what you can see. The function that decides the outcome is the one buyers look at last: respond, at 3 AM.
This is the full reference. It gives you the yardstick, a map of about 40 services and who usually delivers each, plain comparisons of the detection and response options, patching, scanning and penetration testing, how providers follow NIST and where they depart from it, who answers when something goes wrong, the seams between the functions, 19 questions to put in writing and how to read the answers, how to read a price sheet, and definitions for every term. We built it from evaluating managed security providers, and it works whether you are choosing a first provider or replacing one. A shorter version, with the same framework, lives on our cyber security page.
The yardstick: six functions
The NIST Cybersecurity Framework 2.0, published in February 2024, describes security as six functions. Picture them as rings. Govern sits at the center: the policies, roles and risk decisions that everything else follows. Around it are Identify, Protect, Detect, Respond and Recover. NIST says the functions are worked on together, not in order. Three things run across all the rings: automation that links detection to response, managed services that deliver several rings at once, and a feedback loop that sends each incident's lessons back to Govern and Identify.
(opens the full-size image in a new tab)
The framework is voluntary. No one certifies you, or a provider, as "NIST compliant." It is a common vocabulary. That is why it works as a yardstick: it lets you line up quotes that are written in different languages.
How providers follow NIST, and where they depart from it
Most managed security providers say they align to NIST, and the claim is usually fair, because the framework is flexible and risk-based. The useful question is what "aligned" means in their service. Providers commonly follow NIST in four ways:
- They map services to the six functions. Governance help and policy reviews under Govern, asset lists and risk assessments under Identify, safeguards under Protect, monitoring under Detect, incident handling under Respond, and backup and restoration under Recover.
- They assess clients against it. Many write a target profile, which is a list of the outcomes you want from each function, then measure the gap between where you are and where you want to be.
- They tie it to rules you already face. Examples are CMMC for defense contractors, HIPAA for health data and PCI for payment cards.
- They apply it to themselves. A breach at a provider can reach every client, so a provider that follows the framework internally is safer to hire.
They also depart from it, often for good reasons:
- They customize and prioritize. A provider may stress supply chain risk for one client and skip it for another.
- They add other standards. Providers commonly pair NIST with ISO 27001, the CIS Controls, zero trust and MITRE ATT&CK for more operational detail. NIST is the strategy; the others are tactics.
- They go past it. A fully managed security operations center, AI-assisted threat hunting and real-time response extend beyond the basic detect and respond outcomes.
- They cover only part of it. For cost, smaller providers often focus on Detect and Protect, and leave Govern, Identify and Recover to someone else.
- They follow what the contract requires. For federal work, that can mean NIST SP 800-171 or SP 800-53, which are far more prescriptive than the framework.
So ask each provider to show its service mapped to the six functions, to say which functions it does not cover, to name any other framework it works from, and to state what it will attest to. A gap is not a flaw. A gap nobody owns is.
Who usually delivers each function
A managed service provider (MSP) runs your day-to-day IT. A managed security service provider (MSSP) runs security for you, usually through a round-the-clock security operations center. A security consultancy assesses and advises. They answer the same request for proposal and they sell different things, so line up each line item against a function before you compare totals. In general, MSPs cluster at Protect and Recover, MSSPs at Detect and Respond, and consultants at Govern and Identify. Providers differ, so treat this as a starting point.
| Function | In plain words | Who usually delivers it | Question to ask a provider |
|---|---|---|---|
| Govern | Set the rules, roles and risk appetite | Security consulting, a virtual security chief | Who owns security decisions, and what will you attest to for my insurer? |
| Identify | Know what you have and where it is weak | Consulting; an MSP for asset lists; vulnerability scanning | How do you find assets and weak points, and how often? |
| Protect | Make the doors harder to open | An MSP (patching, endpoints); an MSSP (firewalls, email, identity) | What do you manage, what do you only recommend, and who is accountable for each? |
| Detect | Spot an attack | An MSSP (round-the-clock monitoring, SOC, EDR, MDR, XDR) | What do you watch, where do your analysts sit, and can I see the detection rules? |
| Respond | Contain and fix it | An MSSP; incident response retainers | What can you do on your own at 3 AM, how fast, and who approves? |
| Recover | Get back to normal | An MSP (backup and disaster recovery) | How long to restore, and when did you last test it? |
The service map: about 40 services and who usually delivers them
Read across a row. Yes means the service is typically in scope for that kind of provider. Varies by provider means some do it and some do not, so ask. Add-on means it is usually sold separately. Unclear means we could not say from experience. Not typical means you should not expect it. The function column shows where each service lands in the NIST framework. Services that keep the lights on but are not security sit at the end.
| Service | NIST function | MSP | MSSP | Security consulting |
|---|---|---|---|---|
| Policies, risk strategy and oversight | Govern | Not typical | Not typical | Yes |
| Compliance assistance (HIPAA, PCI, SOC 2, CMMC) | Govern | Not typical | Not typical | Yes |
| Compliance reporting and log retention | Govern | Not typical | Yes | Not typical |
| Virtual security chief (vCISO) | Govern | Not typical | Not typical | Yes |
| Virtual CIO (vCIO) | Govern | Not typical | Not typical | Yes |
| IT strategy and advisory | Govern | Not typical | Not typical | Yes |
| Asset inventory, risk assessment and data classification | Identify | Not typical | Not typical | Yes |
| Vulnerability management and scanning | Identify | Not typical | Yes | Not typical |
| Vulnerability scanning, host, network and web application | Identify | Not typical | Not typical | Yes |
| Penetration testing | Identify | Not typical | Not typical | Yes |
| Antivirus | Protect | Yes | Not typical | Not typical |
| Managed firewall and network security | Protect | Not typical | Yes | Not typical |
| Endpoint security management | Protect | Not typical | Yes | Not typical |
| Patching and updates | Protect | Yes | Varies by provider | Not typical |
| Email security | Protect | Not typical | Varies by provider | Not typical |
| Managed VPN and secure remote access | Protect | Not typical | Varies by provider | Not typical |
| Cloud security posture and monitoring | Protect | Not typical | Varies by provider | Not typical |
| Endpoint management (provisioning, mobile device management) | Protect | Yes | Varies by provider | Not typical |
| Broad cybersecurity services | Protect | Varies by provider | Yes | Not typical |
| Security operations center as a service | Detect | Not typical | Yes | Not typical |
| Round-the-clock monitoring and alert triage | Detect | Not typical | Yes | Not typical |
| Endpoint detection and response (EDR) | Detect | Not typical | Yes | Not typical |
| Managed detection and response (MDR) | Detect | Varies by provider | Yes | Not typical |
| Extended detection and response (XDR) | Detect | Not typical | Yes | Not typical |
| SIEM deployment and management | Detect | Not typical | Yes | Not typical |
| Threat intelligence | Detect | Not typical | Yes | Not typical |
| Threat hunting | Detect | Not typical | Varies by provider | Not typical |
| Identity threat detection and response | Detect | Not typical | Varies by provider | Not typical |
| AI-driven automation | Detect and Respond | Yes | Yes | Not typical |
| Security orchestration and automated response (SOAR) | Respond | Not typical | Yes | Not typical |
| Incident response help | Respond | Not typical | Yes | Not typical |
| Rapid incident response (RIR) | Respond | Unclear | Add-on | Unclear |
| Backup and disaster recovery | Recover | Yes | Not typical | Not typical |
| Network operations center as a service | Day-to-day IT | Yes | Not typical | Not typical |
| Help desk and technical support | Day-to-day IT | Yes | Not typical | Not typical |
| Remote monitoring and management of devices | Day-to-day IT | Yes | Not typical | Not typical |
| Network and infrastructure maintenance | Day-to-day IT | Yes | Not typical | Not typical |
| Cloud services and management | Day-to-day IT | Yes | Not typical | Not typical |
| Phone and collaboration systems | Day-to-day IT | Yes | Not typical | Not typical |
| Onsite remote hands | Day-to-day IT | Not typical | Varies by provider | Not typical |
| Project work (migrations, refreshes), usually billed separately | Day-to-day IT | Yes | Yes | Yes |
Two notes. Patching is a common gap, covered below. And a provider that says "yes" to everything is not showing you its focus. Ask what it does best, and who does the rest.
Detection and response in plain words
Four terms get mixed up in quotes: EDR, MDR, XDR and RIR. They are not interchangeable, and one is a tool while the others are services.
| Topic | EDR | MDR | XDR | RIR |
|---|---|---|---|---|
| What it focuses on | Endpoint devices: laptops, servers, workstations | Outsourced round-the-clock detection, hunting and response | Visibility and automated correlation across several areas | Fast, targeted response to an active or confirmed incident |
| What it covers | Endpoints only | Endpoints at the core, often network, cloud and logs; varies by provider | Endpoints, network, cloud workloads, identity, email and applications | The whole organization during an incident, using the tools and data you already have |
| How it is delivered | A tool on each device; self-run or run by a provider | A fully managed service: people plus technology | A platform; self-run, co-managed or fully managed | On demand, or on a retainer |
| Who does the work | Your team, to watch, investigate and respond | The provider's analysts monitor, triage, hunt, investigate and fix | Varies; heavily automated; may need your team unless managed | The provider's incident response specialists, including forensics |
| How proactive it is | Detects and analyzes behavior; limited hunting, depending on the tool | Strong: round-the-clock hunting, alert prioritization, guided fixes | Strong: automated hunting and fewer false alarms | Reactive by nature; some retainers include readiness work |
| How it responds | Automatic steps such as isolating a device, plus advice; people often finish the job | Hands-on, guided or full remediation by the provider | Automated and orchestrated across areas, for a faster unified response | Accelerated containment, eradication, forensics and recovery coordination |
| Where a provider usually fits | May deploy and manage the tool and give basic support | This is the core offering of many MSSPs | May run the platform, or work with the one you own | Rapid incident response as a service, often a retainer |
| Best for | Organizations with some in-house security staff that need endpoint visibility | Small and mid-size organizations without a round-the-clock security team | Larger organizations that want one view across a hybrid environment | Any organization facing an active incident that needs expert help fast |
| Limits | Narrow view; alert fatigue if not tuned; needs skills | Scope and depth vary by provider; possible lock-in | Can be complex and costly; hard to integrate if you use several vendors | Not continuous; on-demand help costs more |
The practical rule: EDR gives you the signal, MDR gives you the people who act on it, XDR widens the view, and RIR is the fire department you call when it is already burning. If no one on your team can respond at 3 AM, EDR alone is not a service.
Patching: who owns it
Patching is where an MSP and an MSSP most often assume the other has it covered. Typically the MSP patches broadly and the MSSP patches narrowly, and the gap between them is where an old flaw sits for months.
| Topic | MSP | MSSP |
|---|---|---|
| Scope | Broad: operating systems, applications, drivers, all endpoints and servers | Narrower: security-focused, such as endpoint tools, firewalls and critical flaws |
| Ownership | Hands-on deployment, testing and scheduling | Often recommends; sometimes automates for security items |
| Usual tooling | Remote monitoring and management platforms | Vulnerability scanners with partial automation |
| Approach to risk | Accepts the risk as part of running IT operations | Often limits what it will do, to avoid claims for business disruption |
| Frequency | Routine, proactive and all-inclusive | Ad hoc, or aimed at the highest-risk flaws |
Ask each provider in writing who patches what, who tests the patch, and who is accountable if a patch breaks something or is never applied.
Finding weaknesses: scans and penetration tests
A vulnerability scan and a penetration test are different products at different prices. Buyers who ask for "a pen test" and receive a scan are common.
| Topic | Vulnerability scanning | Penetration testing |
|---|---|---|
| Main goal | Find and list known or possible weaknesses | Simulate real attacks to prove what can be exploited and what it would cost you |
| Method | Fully automated with scanning tools | Hands-on by people, using tools and creativity, with some automation |
| Depth | Broad and shallow: many issues across a large environment, quickly | Narrow and deep: how attacks chain together and get past defenses |
| Exploitation | None; it detects and reports | Yes, safely, to show whether a weakness can be used |
| False alarms | Common; needs checking and tuning | Low, because testers confirm findings by trying them |
| How often | Often: daily, weekly or continuous | Less often: quarterly, yearly or after big changes |
| Cost | Lower | Higher, because skilled people and time are involved |
| What you get | A list of weaknesses with severity scores and fixes | A report with proof, attack paths, business impact and priorities |
| Best for | Ongoing hygiene and compliance scans (PCI, HIPAA) | Checking your defenses, high-risk environments, and rules that require proof |
| Limits | Misses unknown flaws and logic errors; noisy | Limited to agreed targets and time; costly to repeat often |
Ask which one you are buying, how many addresses, applications and devices are in scope, whether testing is internal, external or both, and whether the testers sample or test everything.
The five tests
These five tests turn the six functions into a scorecard. Use them for every provider.
1. What it covers. Check the service against the six functions. Many providers are strong on detect and respond and thin elsewhere. Check how well the offer is complete, and which functions the provider leaves to someone else.
2. Who responds, and how fast. Ask what the response clock measures. "Fifteen minutes" can mean the alert was acknowledged, or that a threat was contained. Those are different promises. Ask how time to detect and time to respond are measured, what is excluded, and what the remedy is. A service credit that does not cover an hour of downtime is not a commitment.
3. What you can see and keep. Can you read the detection rules? How long are logs kept, hot and cold, and in what format do they leave? Who owns them when you cancel? Security contracts are often renewed under pressure; the advantage is in knowing you can move.
4. How it fits your environment. Cloud, older systems, Mac, Microsoft 365, the tools you already own. Check that the provider connects to what you run, how many integrations it supports, how long deployment takes, and what it needs you to buy.
5. Who is on the other end. Ask for references, the named people, how long staff stay, how many clients keep the service year after year, and the provider's own financial stability. Ask whether the provider will co-manage with your staff, and how.
Who answers when it goes wrong
Name one accountable person for each row, and write it down before you sign. In the table, R means responsible for the work, A accountable, C consulted and I informed. Treat it as a starting point and adjust it to your organization.
| Decision | Executives | IT lead | Security lead | Business owner | Legal | Provider |
|---|---|---|---|---|---|---|
| Set policy and risk appetite (Govern) | A | R | R | C | C | I |
| Asset list and risk assessment (Identify) | I | A | R | C | I | R |
| Patching, access, email, backups (Protect) | I | A | C | I | I | R |
| Monitoring and alert triage (Detect) | I | C | A | I | I | R |
| Contain and fix an incident (Respond) | I | R | A | C | C | R |
| Restore operations (Recover) | I | A | C | C | I | R |
| Approve what an AI system may decide | A | C | C | R | C | C |
| Set the limits on what AI may touch | I | A | R | C | I | R |
| Answer when the AI is wrong | I | C | C | A | C | C |
Where AI fits
Attackers use AI to write phishing that sounds like your colleagues and to fake voices on payment calls. These are industry forecasts, not measured trends. Providers use AI to sort alerts faster, and the better ones keep a person in charge of any action that could take a system down. Your own AI tools are a new target too, because a hidden instruction in a document can steer them. So add one test: ask what the person does and what the AI does at each step, and who approves containment.
Our AI governance series covers the same ground for buyers. A NIST discussion draft on AI in critical infrastructure, which is not official guidance and may change, offers a checklist worth knowing. Its 13 practices, in plain words:
- Set requirements for performance, safety and security across the whole system.
- Decide how the AI must hold up under stress, how it should fail safely, and what level of service is good enough, before you deploy it.
- Set risks, policies and oversight, with firm limits enforced outside the AI itself.
- Write procedures that let people override, suspend and recover.
- Give AI agents and tools their own identities and the access their role needs.
- Manage AI vendors and the supply chain you depend on.
- Manage your internal AI supply chain and where its data came from.
- Prepare incident response for failures that are particular to AI.
- Train people by role, so trust in the AI is earned.
- Log and audit what the AI does, at several levels.
- Plan for continuity and disaster recovery when the AI is unavailable.
- Independently verify what the AI generates, such as code and configurations, before it runs.
- Plan how to retire an AI system and withdraw its authority.
What your insurer will ask
Insurers ask what controls you run, such as multifactor authentication, endpoint detection and backups, and increasingly how you use AI. What you write on the application is a signed statement. In 2022, an insurer sued to void a policy after a ransomware claim, saying the application claimed multifactor authentication the insured did not have (Travelers v. ICS). Reports differ on how the case ended, so read it as a warning, not a ruling. Check each answer against what is running, and ask your broker which policy covers a loss that AI causes. Our article on cyber insurance and AI explains the exclusions now appearing.
What attestation means
An attestation is a formal statement that something is true, made by someone who can be held to it. An independent one comes from a licensed CPA firm: a SOC 2 report is the firm's opinion on a provider's controls, tested against standard criteria, and it is a report, not a certificate. A Type 1 report describes the controls on one date. A Type 2 report tests them over a period. A self-attestation is one you sign yourself, on an insurance application or, for defense contractors, as the annual affirmation under CMMC. Ask each provider for its latest SOC 2 report and what it covers. Treat anything you sign as a promise.
What the six functions leave out: the seams
The framework and most provider packages are built from boxes: a tool for email, a tool for endpoints, a tool for the firewall. Each box does its job. The attacks that hurt move between the boxes. NIST says the six functions run together, but it does not tell you who owns the places where they meet. Five capabilities live in those seams, and most contracts leave them to you. There is a full article on this: Kirk security: it sees the Klingon once he is on the deck.
Outside the wall. Many security services start watching when something touches your network. Attacks start earlier: probing your website, guessing logins, running bots. Edge services, such as a web application firewall, bot management and denial-of-service protection, can warn you at that stage. Often the web team owns them, and the security provider never sees what they see. Ask: Do you see what hits my website and logins before it reaches my network?
Data leaving. Most attention goes to what comes in. Data can also leave quietly through ordinary web services and cloud apps. Outbound traffic falls between the network team, the security team and the application team, and nobody may own it. Ask: Do you watch outbound traffic to web services and cloud apps, and who owns that?
Attacks not in the book. Detection built on known patterns catches the patterns it knows. The costly incident is the one nobody wrote a playbook for. Behavior-based tools exist, and they need tuning and a person who looks when they fire. Ask: What do you do when the behavior is not in your playbook, and how fast does a person look?
Credentials, for people and machines. Identity connects every function, and it now includes service accounts and AI agents. An AI tool that holds your credentials can use them. In a widely reported 2026 incident, an AI agent that left its test environment used exposed cloud credentials at several services. Accounts differ on what data it touched. Give each agent its own identity, short-lived access, and only what its task needs. Ask: Which credentials do my AI tools and service accounts hold, who rotates them, and who sees them used?
Who owns the integration. Tools that do not talk to each other leave gaps no one is paid to close. A provider's tools and yours have to work as one system, and someone has to own the joints. Ask: Who owns the connections between your tools and mine, and what happens when one breaks?
The 19 questions to put in writing
- Can my team co-manage, and what access do they get?
- Can you contain a threat on your own, and under what rules?
- Is there a response-time guarantee with penalties? How do you report time to detect and time to respond?
- What does your response clock measure: acknowledgement, or containment?
- Can you disable a compromised account automatically at 3 AM?
- Where do your SOC analysts sit?
- How long are logs kept hot, how long cold, and who owns them?
- Can I see your detection rules and tuning, or is it a black box?
- What happens to my existing endpoint and SIEM licenses?
- Do you cover Mac?
- Is pricing split into separate line items?
- What does a person do, and what does the AI do, at each step? Who approves containment?
- Can I see your latest SOC 2 report, the period it covers and the systems in scope?
- What will you attest to for my insurer, and what must I attest to myself?
- Do you see what hits my website and logins before it reaches my network?
- Do you watch outbound traffic to web services and cloud apps, and who owns that?
- What do you do when the behavior is not in your playbook, and how fast does a person look?
- Which credentials do my AI tools and service accounts hold, who rotates them, and who sees them used?
- Who owns the connections between your tools and mine, and what happens when one breaks?
How to read the answers
The wording of an answer tells you as much as the answer. Here is what the common replies usually mean.
| What you hear | What it usually means | What to ask next |
|---|---|---|
| "Yes," with no detail | The provider agrees with the question but has not described the service | Ask for the contract clause or the runbook that says so |
| "Yes, it depends on the product or service" | It depends on which tier or product you buy | Ask which tier, and what it costs |
| "Not by default" or "premium tier only" | It exists as an add-on | Price it as part of the quote |
| "Possible once we define the rules of engagement" | It is not pre-approved; you must authorize it up front | Ask for the draft rules and who approves them |
| "We don't publish a blanket guarantee; targets are set per tier" | There is no blanket penalty for missing a response target | Ask for the numbers per tier and the remedy |
| "Most services are a single price" | Services are bundled and cannot be separated | Ask for a line-item view and what each part costs |
| "Available, but it needs scoping" | It is not in the quote | Ask for it in writing, with a price |
| "We partner for that" | Another company delivers it | Ask who, and who is accountable to you |
How to read a price sheet
Providers quote in different units, so totals mislead. Ask every provider to price the same list of items, then convert each to a common unit. A complete managed security price sheet usually has lines like these:
| Line item | Usual unit | What to check |
|---|---|---|
| Managed detection and response | Per endpoint or per user | Which devices count, and whether the endpoint software license is included |
| Managed endpoint protection with license | Per device | License included, or bring your own |
| Firewall monitoring | Per device | High-availability pairs are often priced separately |
| Server monitoring | Per server | Physical and virtual servers both |
| Microsoft 365 and identity monitoring | Per platform | Which Microsoft license tier it needs |
| Vulnerability management | Per device | How often scans run |
| Patching, user devices and servers | Per device | Which patches, and who tests them |
| Firewall and switch management | Per device | Monitoring and management are different things |
| External vulnerability scanning | Per IP address | How many addresses are in scope |
| Penetration testing | Per engagement or per IP | Internal, external and applications priced apart; the testing method |
| Incident response retainer | Per year, or hours | What is included, and what is billed by the hour |
| Professional-services hours | Per hour | Prepaid hours, or on demand |
Then compare over three years in six steps:
- List the scope: endpoints, servers, users, firewalls, platforms and addresses.
- Convert every quote to a cost per endpoint per month.
- Add what the quote assumes you will buy separately, such as a SIEM license or a higher Microsoft license tier.
- Add one-time costs: onboarding, setup, and any penetration test.
- Add the cost of what the quote leaves out, and what it would cost to replace the provider.
- Compare three-year totals, then score how confident you are in each estimate. A low price that is "subject to change" is not a low price.
Provider types, not names
Providers describe themselves in a few ways, so treat each description as their claim to test. Global-scale providers position themselves for large, regulated organizations; test whether they fit a smaller environment. Cloud-native providers position themselves for fast deployment and heavy automation; test false positives and older systems. Legacy and compliance specialists position themselves for mainframes, industrial systems and audit support; test how much is automated. Mid-market providers led by service position themselves on named teams and threat hunting; test global coverage. Small regional providers position themselves for small, lower-risk environments; test what happens as you grow. Consulting add-ons assess and advise but do not watch; test who watches at night.
Where it lands
Use the six functions as the yardstick, name one accountable person for each, ask the 19 questions in writing, and price the same list from every provider. Pay for the response, not the dashboard.
If you are comparing providers, that is the evaluation we run. Schedule a security evaluation.
Definitions in plain words
- Attestation. A formal statement that something is true, made by someone who can be held to it. An independent one comes from an outside firm. A self-attestation is one you sign yourself.
- CIS Controls. A prioritized list of security safeguards published by the Center for Internet Security. Providers use it for practical, step-by-step detail.
- CMMC (Cybersecurity Maturity Model Certification). A US Department of Defense program. Defense contractors must meet cybersecurity requirements and show it, by self-assessment or by an outside assessor, depending on the level.
- Co-management. You and the provider both have access to the same security tools and share the work.
- Containment. Stopping an attack from spreading, for example by isolating a computer or blocking an account.
- Dwell time. How long an attacker is inside your systems before anyone finds them.
- EDR (endpoint detection and response). Software on computers and servers that records activity and flags or acts on threats. Someone still has to watch it.
- Endpoint. A computer, server, phone or other device that connects to your network.
- Eradication. Removing the attacker and whatever they left behind.
- Forensics. Investigating what happened, and preserving the evidence.
- Hot and cold log storage. Logs are the records your systems keep. Hot storage keeps recent logs ready to search fast. Cold storage keeps older logs more cheaply and retrieves them more slowly.
- Incident response. The plan and the work for handling an attack, from first alert to recovery.
- ISO 27001. An international standard for running an information security management program. Organizations can be audited and certified against it.
- MDR (managed detection and response). A service where another team watches your systems around the clock, investigates alerts and acts for you.
- MFA (multifactor authentication). Logging in with something more than a password, such as a code from your phone.
- MITRE ATT&CK. A public catalog of the tactics and techniques attackers use, used to test whether detection covers real attacker behavior.
- MSP (managed service provider). A company that runs your day-to-day IT for a recurring fee: help desk, patching, backups.
- MSSP (managed security service provider). A company that runs security for you, usually through a round-the-clock security operations center.
- MTTD and MTTR (mean time to detect and respond). Averages of how long it takes to spot a threat and to respond to it. Ask how each is measured, because "response" can mean acknowledged or contained.
- NIST AI Risk Management Framework. Voluntary US guidance for managing AI risk, organized as govern, map, measure and manage.
- NIST Cybersecurity Framework 2.0. A voluntary US government framework that describes security as six functions: govern, identify, protect, detect, respond and recover. It is a common vocabulary, not a certification.
- NIST profile. A custom list of the security outcomes an organization wants from each function, used to measure the gap between where it is and where it wants to be.
- NOC (network operations center). The team that monitors and maintains your network and systems for availability, as opposed to security.
- Penetration test versus vulnerability scan. A scan is automated and checks for known weaknesses. A penetration test is people carrying out an authorized simulated attack to prove what can be broken.
- Phishing and business email compromise. Phishing is a fake message meant to trick you. Business email compromise is a fake message, often posing as an executive or a vendor, meant to get money or data.
- Prompt injection. Hidden instructions in text, a document or a web page that steer an AI system into doing something its owner did not intend.
- RACI. A table that names who is Responsible, Accountable, Consulted and Informed for each decision.
- Remediation. Fixing the root cause and the weakness, not only stopping the attack.
- RIR (rapid incident response). Expert help during an active attack: containment, forensics and recovery, often bought as a retainer.
- RMM (remote monitoring and management). Software an MSP uses to watch, patch and manage your devices remotely.
- Service level agreement (SLA). The written promise about what the provider will deliver, how fast, and the remedy if it does not.
- SIEM (security information and event management). A system that collects logs from many sources, connects the dots and raises alerts.
- SOAR (security orchestration, automation and response). Software that runs the repeatable steps of a response automatically, using prewritten playbooks.
- SOC (security operations center). The team, and sometimes the room, that monitors for threats around the clock.
- SOC 2. A report by an independent CPA firm on a service provider's controls, tested against standard criteria. A Type 1 report describes the controls at a point in time. A Type 2 report tests them over a period.
- Threat hunting. People searching for attackers that automated tools missed.
- Threat intelligence. Information about attackers, their methods and what they are targeting now, used to improve detection.
- vCISO (virtual chief information security officer). A part-time or outsourced security leader who sets strategy, policy and priorities.
- XDR (extended detection and response). A platform that watches endpoints, network, cloud, email and identity together, so it can connect clues across them.
- Zero trust. A design principle: no user, device or system is trusted by default, and every request is checked.
Sources
- NIST, The NIST Cybersecurity Framework (CSF) 2.0, CSWP 29 (February 2024)
- NIST, AI Risk Management Framework 1.0
- AICPA, System and Organization Controls (SOC) suite of services
- MITRE, ATT&CK knowledge base
- Center for Internet Security, CIS Critical Security Controls
- ISO, ISO/IEC 27001 information security management
- Insurance Journal, Travelers wants out of contract with insured that allegedly misrepresented MFA use (2022)
- Reed Smith, Insurance applications under scrutiny: lessons from Travelers v. ICS (2022)
- NIST AI RMF Profile for Automated, Agentic, and Super Intelligence in Critical Infrastructure and High-Consequence Applications (SICI), community of interest discussion draft, November 9, 2026. Not official guidance; may change.
- IQ4hire's own experience evaluating managed security, MSP and security consulting providers. The service map and comparison tables reflect typical patterns, which vary by provider.
