Be Market Be Market Be Digital Be Online Be Online Be Cloud Be Cloud Be Secure Be Secure Be Connect Be Connect Bea Bea Be AI Be AI Be Watch Be Watch Be Screen Be Screen Pay Now

// Cyber Security

NIST CSF 2.0 for a 20-person company: the version that fits on one page

The security framework the big end of town uses, cut down to the six questions a small NZ business needs to answer — Govern, Identify, Protect, Detect, Respond, Recover — with the plain-English control for each.

By the Be Digital team 2 min read

The short version

  • NIST CSF 2.0 is six functions: Govern, Identify, Protect, Detect, Respond, Recover. That is the whole structure.
  • For a 20-person company each function is one question and three to four controls. The page below is the framework at that size.
  • Its value is evidence: insurers, large customers and the Privacy Commissioner all recognise it.
  • A managed plan does Protect and Detect every day; the rest is decisions and documents you make once.

Security frameworks have a reputation for being for banks. NIST CSF 2.0 earned that reputation and then, in its 2.0 update, added explicit guidance for small organisations. We use it as the spine of Be Secure because it scales: the same six headings work for a two-person firm and a two-thousand-person one. Here is the two-person-firm version.

The six functions, as six questions

Function The question The controls at 20 people
Govern Who owns security, and what have we decided? A named owner (usually the managing director); a one-page policy; security on the agenda quarterly; the Privacy Act obligations written down
Identify What do we have, and what matters most? An asset register of devices, accounts and systems; a list of the data that would hurt most; the suppliers who hold it
Protect What stops the common attacks? MFA everywhere; patching on supported systems; least-privilege access; endpoint protection; email security; encryption on laptops; staff training
Detect Would we know if something was wrong? Monitored endpoint detection; alerts that reach a person; login anomaly alerts in Microsoft 365
Respond What do we do in the first hour? A one-page incident plan; who calls whom; the Privacy Act 72-hour notification path
Recover How do we get back to work? Separate, immutable, tested backups; recovery times per system; the one-page continuity plan

Why the structure matters more than the controls

Most small businesses already have some of the controls — antivirus here, a backup there. What they lack is the map that shows the gaps. Put the same controls under the six headings and the gaps are obvious: everything in Protect, nothing in Detect, Respond is “we’d call someone”. That is the typical picture, and it is why ransomware is found at encryption time rather than at entry time.

What “good” looks like at each size

  • Five people: Govern and Identify on one page; Protect done by a managed plan; Detect via monitored endpoints; Respond and Recover as two paragraphs and a tested backup.
  • Twenty people: the table above, with the asset register kept current and a quarterly review.
  • Fifty people: add a security report to the board pack, an annual external test, and a named deputy for the security owner.

How it maps to a managed plan

DigitalShield Essential delivers most of Protect. Business adds the Detect and Govern layers — security reporting, reviews, hardening. Complete adds 24/7 managed detection and response and the advanced Recover capability. Be Secure runs the framework itself: the assessment, the gap list, the evidence pack an insurer or a tender asks for.

A framework is only useful if someone owns it. The first step is not a tool; it is a name next to the word “Govern”. If that name is yours and you would like the one-page version filled in for your business, ask — it is the first thing a Be Secure engagement produces.

// More insights

Keep reading.

// Ready when you are

Want this done, not just explained?

Tell us what your business runs on today. We will map what DigitalShield would cover, what it would cost per user, and what we would fix first — free, and in plain language.

  • Free, no obligation
  • You keep the findings
  • A real engineer, not a call centre