ISO/IEC 27001 · Global

ISO 27001 logging and monitoring, control by control.

What the ISO/IEC 27001:2022 Annex A controls for logging, monitoring, clock synchronization, incidents and evidence ask of you, in plain English, and where a SIEM you run in your own environment fits. Your logs never reach nano.

Buy nano
Talk to sales
Annex A, control by control

The controls a SIEM supports.

Each control's intent in plain English, what it means in practice, and where nano fits.

ISO/IEC 27001:2022, Annex A: technological controls for logging and monitoring

Annex A controls apply as selected in your Statement of Applicability. Control intent is summarized; ISO/IEC 27002:2022 gives the guidance for each control.

Ref Control intent In plain English How nano helps
A 8.15 Logging Produce logs that record activities, exceptions, faults and other relevant events, and store, protect and analyze them. iso.org · ISO/IEC 27001:2022 Decide what to log, keep it safe from tampering, and actually look at it.
Collects the sources you onboard into one store in your environment, normalized to OCSF. Roles and source visibility limit who can read which logs, and changes to retention or settings go to nano's own audit log.
A 8.16 Monitoring activities Monitor networks, systems and applications for anomalous behavior, and act to evaluate potential information security incidents. iso.org · ISO/IEC 27001:2022 Watch for what looks wrong, and follow up on it.
Detection rules run on events as they arrive and raise alerts; risk-based alerting rolls weak signals for one user, host or IP into a single alert.
A 8.17 Clock synchronization Synchronize the clocks of information processing systems to approved time sources. iso.org · ISO/IEC 27001:2022 All clocks agree, so events from different systems line up.
Clock sync is a host setting you control: point nano's hosts and your sources at your approved time servers. Events keep their original timestamps in consistent OCSF time fields, so sources line up on one timeline.

ISO/IEC 27001:2022, Annex A: organizational controls for incidents and evidence

Ref Control intent In plain English How nano helps
A 5.25 Assess information security events and decide whether to categorize them as information security incidents. iso.org · ISO/IEC 27001:2022 Triage: which events are incidents?
Related alerts group into cases with severity, entities, evidence and timeline, and the decision is recorded on the case.
A 5.26 Respond to information security incidents in line with documented procedures. iso.org · ISO/IEC 27001:2022 Follow your incident procedure, every time.
Playbooks attached to a case lay out the documented investigation and response steps. Case actions go to the audit log with actor and time.
A 5.27 Use knowledge gained from information security incidents to strengthen and improve controls. iso.org · ISO/IEC 27001:2022 Learn from each incident.
Closed cases keep the record of what happened. Turn what you learned into new detection rules, and a useful adaptive playbook can be promoted into your library.
A 5.28 Establish procedures to identify, collect, acquire and preserve evidence related to information security events. iso.org · ISO/IEC 27001:2022 Keep evidence in a way you can rely on later, for discipline or legal action.
Logs stay on storage you own for the retention you set, under your access controls. Platform audit records can be exported as CSV or JSON, and every export is itself recorded.
For your certification audit

Evidence on storage you own.

Auditors ask to see that logging and monitoring operate, not just that a policy exists. With nano in your environment, that evidence is a search away.

8.15 · protected logs

Who can read and change logs.

Roles, SSO group mapping and source visibility limit access inside nano. Sign-ins, role changes and retention changes go to the audit log, exportable as CSV or JSON. Platform audit log

8.16 · monitoring operates

Alerts that fired, and what happened next.

Alerts and the cases they became, with who worked them and when, for any period your auditor samples. nano's optional monitoring stack alerts if ingest stalls. Monitoring

Supplier controls

No SIEM vendor holding your logs.

nano never receives your log data and has no standing access to your install, so your SIEM vendor is not another supplier holding your security logs. What your install sends to nano

Inside your environment

Inside your ISMS scope, on your infrastructure.

nano installs with Docker Compose or with Helm on Kubernetes, on your servers or in your own cloud account. Sources send logs to it over your network, and it parses, stores, searches and runs detections on them there.

Your environment

Your data center, your own AWS, Azure or Google Cloud account, or an air-gapped network

01 · Sources
  • identity provider
  • endpoint
  • firewall
  • cloud audit
  • servers
  • SaaS apps
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 ISO/IEC 27001?

ISO/IEC 27001 is the international standard for information security management systems (ISMS). The current edition is ISO/IEC 27001:2022. It sets requirements for establishing, running and improving an ISMS, and its Annex A lists the information security controls you consider, with ISO/IEC 27002:2022 giving guidance for each.

Which ISO 27001 controls cover logging and monitoring?

In the 2022 Annex A: 8.15 Logging, 8.16 Monitoring activities and 8.17 Clock synchronization. The incident controls 5.25 (assessment and decision on information security events), 5.26 (response to information security incidents), 5.27 (learning from incidents) and 5.28 (collection of evidence) depend on the same logs.

Is 8.16 Monitoring activities a new control?

Yes. Monitoring activities is one of the controls added in the 2022 edition. The older logging controls were consolidated into 8.15 Logging, and clock synchronization continues as 8.17.

How long does ISO 27001 require logs to be kept?

The standard sets no fixed retention period. You decide it from your risk assessment, legal and contractual obligations, and record it in your policies. In nano you set the event retention window yourself (365 days by default) and can tier older data to object storage you own.

Does ISO 27001 require a SIEM?

No. ISO/IEC 27001 does not name tools. A SIEM is a common way to implement 8.15 and 8.16 across many systems and to support 5.25 to 5.28, but you choose the controls and how to implement them.

Is nano ISO 27001 certified?

No. nano, LLC holds no ISO/IEC 27001 certificate. Certification applies to an organization's ISMS, audited by a certification body; ISO itself does not certify. nano is software you run in your own environment, inside the scope of your ISMS.

Does using a SIEM make us ISO 27001 compliant?

No. Conformity covers your whole ISMS: scope, risk assessment, Statement of Applicability, policies, internal audit and management review. A SIEM supplies the logging, monitoring and evidence for some Annex A controls. nano helps with that part.

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