NCSC CAF · United Kingdom

NCSC CAF objective C, outcome by outcome.

What the NCSC Cyber Assessment Framework v4.0 asks for security monitoring and threat hunting, in the framework's own words, and how a SIEM you run inside your own boundary supplies the evidence for each outcome. Your logs never reach nano.

Buy nano
Talk to sales
Objective C, outcome by outcome

Seven contributing outcomes, in the CAF's words.

Each outcome as the NCSC states it, what the indicators of good practice ask in practice, and where nano fits.

Principle C1 Security monitoring

"The organisation monitors the security status of network and information systems supporting the operation of essential function(s) in order to detect security events indicative of a security incident."

Ref What the CAF says In plain English How nano helps
C1.a Sources and tools for logging and monitoring: "The data sources that you include in your logging and monitoring allow for timely identification of events which might adversely affect the resiliency of network and information system(s) supporting the operation of your essential function(s)." ncsc.gov.uk · CAF C1 Log the systems behind your essential functions, keep the logs queryable, and make sure new systems get added.
Every install starts with zero log sources: you onboard what your essential functions depend on from the catalog, over HEC, HTTP, OTLP, cloud pull or Vector agents. Every source is searchable with nPL, and a stats search by source and host shows what reported in any period.
C1.b Securing logs: "You hold log data securely and grant appropriate user and system access only to accounts with a business need. Log data is held for a suitable retention period, after which it is deleted." ncsc.gov.uk · CAF C1 Limit who can reach the logs, watch that access, set a retention period and delete after it.
The log store sits on infrastructure you control. Roles and source visibility limit access inside nano; sign-ins, permission changes and Audit Log exports go to nano's own audit log. Retention is a setting, and expired events are deleted automatically.
C1.c Generating alerts: "Evidence of potential security incidents contained in your monitoring data is reliably identified and where appropriate triggers alerts." ncsc.gov.uk · CAF C1 Detections fire reliably, alerts are enriched and prioritized, and the rules are tuned over time.
Detection rules run on events as they arrive. Events are enriched from threat and IP feeds, so alerts carry that context, and risk-based alerting rolls weak signals for one entity into a single prioritized alert. Rules are yours to customize and tune.
C1.d Triage of security alerts: "You contextualise alerts with knowledge of the threat and your systems, to identify those security incidents as well as responding to all alerts appropriately." ncsc.gov.uk · CAF C1 Triage every alert, categorize by type and severity, follow playbooks, and keep records of what you did.
Related alerts group into cases with severity, entities, evidence and timeline. Playbooks attached to a case give analysts the same steps every time, and each case action is recorded with actor and time.
C1.e Personnel skills for monitoring tools and detection: "Monitoring and detection personnel skills and roles, including those outsourced, reflect governance and reporting requirements, expected threats and the complexities of the network or system data they need to use." ncsc.gov.uk · CAF C1 The people, in-house or outsourced, know the tools, the data and the essential functions.
Your team, or your MSP, operates nano. OCSF normalization means one set of field names across every source, and nPL is one pipe-based language for search, detections and dashboards.
C1.f Understanding user's and system's behaviour, and threat intelligence: "Threats to the operation of network and information systems, and corresponding user and system behaviour, are sufficiently understood. These are used to detect cyber security incidents." ncsc.gov.uk · CAF C1 Know what normal looks like, use threat intelligence that fits your sector, and act on it promptly.
Search one user, host or IP across sources in one timeline to see normal and abnormal behavior. Threat feeds such as ThreatFox and Tor exit nodes enrich events, and you can add your own indicators or turn any feed off.

Principle C2 Threat Hunting

"The organisation proactively seeks to detect, within networks and information systems, adverse activity affecting, or with the potential to affect, the operation of essential functions even when the activity evades standard security prevent/detect solutions (or when standard solutions are not deployable)."

Ref What the CAF says In plain English How nano helps
C2.a At Achieved, among others: "Your threat hunts follow pre-determined and documented methods (e.g. hypothesis driven, data driven, entity driven) designed to identify adverse activity not detected by automated detections." and "You turn threat hunts into automated detections and alerting where appropriate." ncsc.gov.uk · CAF C2 Hunt on a schedule that matches your risk, with documented methods, record what you did, and turn good hunts into detections.
nPL searches across all retained sources make hypothesis, data and entity-driven hunts practical. Notebooks record the hunt; a query that finds something becomes a detection rule; retro hunt checks new indicators against past events.
Indicators of good practice

What an assessor looks for, and where it shows.

Selected indicators from C1, quoted from CAF v4.0, with the nano evidence that speaks to each.

C1.a · Achieved
"Log datasets are synchronised including using an accurate common time source so that separate datasets can be correlated in appropriate ways."

Point nano's hosts and your sources at the same time servers. Events keep their original timestamps in consistent OCSF time fields, so sources line up on one timeline.

C1.b · Achieved
"All actions involving log data (e.g. copying, deleting, modification, or even viewing) can be traced back to a unique user or system."

SSO with named accounts, roles and source visibility, and nano's own audit log of sign-ins, permission changes and exports. Platform audit log

C1.b · Partially achieved
"You have defined and implemented retention periods for log data."

Event retention is a setting on your own store (365 days by default), with older data tiered to your own object storage and still searchable. Storage and retention

C1.c · Achieved
"Logs are monitored continuously in near real time."

Detections run on events as they arrive, not on a nightly batch, and alerts reach your team through notifications. Detections

C1.d · Achieved
"You document all triage related activities performed by monitoring and detection personnel and these are used to drive improvements"

Cases keep the evidence, notes, decisions and timeline; case actions go to the audit log. Case management

C1.a · Not achieved
"You have no way of ensuring log data is being captured as expected and available when needed."

nano's optional monitoring stack alerts when ingest stalls or drops events, so a gap in collection is noticed. Monitoring

Cyber Security and Resilience Bill

Not yet law. The clock it proposes.

The Bill would update the NIS Regulations 2018. As of November 2026 it is back in the Commons for consideration of Lords amendments; it is not an Act.

  1. 0 h

    Aware of an incident

    As proposed in the Bill; details may change before it becomes law.

  2. 24 h

    Initial notification

    "A light touch, initial notification" to the regulator, with the NCSC informed at the same time.

  3. 72 h

    Full report

    A full incident report. MSPs, data centers and digital service providers also tell affected customers.

GOV.UK, Cyber Security and Resilience Bill factsheet: incident reporting. Bill stages on parliament.uk (bill 4035).
Inside your boundary

Monitoring that you operate and evidence that you hold.

nano installs with Docker Compose or with Helm on Kubernetes, in your UK data center, your own UK cloud account or an air-gapped network. Sources send logs to it over your network, and it parses, stores, searches and runs detections on them there.

Your environment

Your UK data center, your own UK cloud account, or an air-gapped network

01 · Sources
  • OT / SCADA
  • firewall
  • identity provider
  • endpoint
  • email gateway
  • web proxy
02 · nano
  • Collect and parse
  • Detections and alerts
  • Search and cases
03 · Your storage
  • Disks you own
  • Optional object storage tier
  • Retention you set
Optional · AI pivt AI calls your model endpoint directly: any OpenAI-compatible API (including self-hosted models) or the Anthropic Messages API. Off by default; model calls never go through nano.
nano, the vendor

Never receives your logs.

Connected
  • Daily license check-in: deployment ID, install ID, version
  • Hourly content and enrichment-feed updates (no data sent; can be turned off)
  • One number per day: total GB ingested
  • Downloads: log-source catalog, detection rules and SOAR content, enrichment feeds, releases
Air-gapped
  • No connection to nano at all
  • Offline license file, renewed by hand
fig 01 · nano runs inside your environment. Log data is never sent to nano.
FAQ

Questions we get asked.

What is the NCSC Cyber Assessment Framework?

The Cyber Assessment Framework (CAF) is the National Cyber Security Centre's framework for assessing how well an organization manages cyber risk to its essential functions. It has four objectives (A managing risk, B protecting against attack, C detecting cyber security events, D minimizing impact), each split into principles and contributing outcomes, with indicators of good practice at Not achieved, Partially achieved and Achieved. Version 4.0 was released on 6 August 2025.

Who has to use the CAF?

It is used by the UK's NIS regulators to assess operators of essential services under the NIS Regulations 2018, by NHS bodies through the CAF-aligned Data Security and Protection Toolkit, and across government. It is guidance rather than law, but it is the standard those regulators assess against.

What does CAF objective C cover?

Detecting cyber security events. Principle C1 Security monitoring has six contributing outcomes: C1.a sources and tools for logging and monitoring, C1.b securing logs, C1.c generating alerts, C1.d triage of security alerts, C1.e personnel skills, and C1.f understanding user and system behavior and threat intelligence. Principle C2 Threat Hunting covers proactively finding adverse activity that evades automated detection.

What changed in CAF v4.0 for monitoring?

The NCSC's release note for v4.0 lists updates to the section on security monitoring and threat hunting to improve detection of cyber threats, and better coverage of AI-related cyber risks throughout the CAF. In v4.0, Principle C2 is titled Threat Hunting, with one contributing outcome, C2.a.

How long does the CAF say logs should be kept?

It sets no fixed period. The C1 guidance says "Duration and level of logging is a business decision", balancing risk, impact and regulatory requirements against the ability to detect and investigate. C1.b asks that log data is "held for a suitable retention period, after which it is deleted", and Partially achieved includes having defined and implemented retention periods.

Is the Cyber Security and Resilience Bill law?

No. As of November 2026 the Cyber Security and Resilience (Network and Information Systems) Bill is still a Bill: it completed its House of Lords stages on 2 November 2026 and is back in the Commons for consideration of Lords amendments. As proposed, it requires an initial notification within 24 hours of becoming aware of an incident and a full report within 72 hours, and brings managed service providers and data centers into scope.

Is nano approved by the NCSC?

No. nano, LLC holds no NCSC assurance, NHS approval or other UK certification, and using nano does not by itself achieve any CAF outcome. It is the SIEM you run; your assessor looks at your environment and how you use it.

Primary sources

Read the rules yourself.

Start with nano.

From US$149/month at 5 GB/day, US$279/month at 10 GB/day (list price, billed monthly; 10% off billed annually). Every feature in one license, and one license covers two installs.

Buy nano
Talk to sales