Detections that ran
Alerts with the rule, the events that matched and the time, for any sample period your auditor picks. Alerts
What the AICPA Trust Services Criteria ask of security monitoring and incident response, and the evidence a SIEM supplies for each. nano runs in your own environment, so the evidence sits on storage you control and your logs never reach nano.
Each criterion in brief, what it means in practice, and where nano supplies the control or the evidence.
The common criteria make up the security category, which every SOC 2 examination covers. Criteria are summarized; the AICPA document has the full text and points of focus.
| Ref | The criterion, in brief | In plain English | How nano helps |
|---|---|---|---|
| CC7.2 | The entity monitors system components and their operation for anomalies that indicate malicious acts, natural disasters or errors affecting its objectives, and analyzes anomalies to decide whether they are security events. AICPA · 2017 TSC (2022) | Watch your systems for things that look wrong, and decide which of them matter. | Detection rules run across every source as events arrive and raise alerts. Risk-based alerting adds up weak signals per user, host or IP, so one alert carries the pattern behind it. |
| CC7.3 | The entity evaluates security events to determine whether they could or did cause a failure to meet its objectives (security incidents) and, if so, acts to prevent or address the failure. AICPA · 2017 TSC (2022) | Triage: decide which security events are incidents, and act on those. | Related alerts group into cases with the evidence, entities and timeline. Analysts search across sources from the case, and each decision is recorded on it. |
| CC7.4 | The entity responds to identified security incidents through a defined incident response program to understand, contain, remediate and communicate them. AICPA · 2017 TSC (2022) | Have a response program, and follow it when an incident happens. | Playbooks attached to a case lay out the investigation and response steps, so every analyst follows the same plan. Case actions, such as assignment, status changes and merges, go to the audit log with the actor and time, which is the record of the response. |
| CC4.1 | The entity selects, develops and performs ongoing and/or separate evaluations to ascertain whether the components of internal control are present and functioning (COSO Principle 16). AICPA · 2017 TSC (2022) | Check, continuously or periodically, that your controls are actually working. | Searches and dashboards over your retained logs show controls working over the period, for example MFA on every sign-in or no direct admin logons. Scheduled reports rerun the same search each period and keep the results. |
| CC6.1 | The entity implements logical access security software, infrastructure and architectures over protected information assets to protect them from security events. AICPA · 2017 TSC (2022) | Control who can reach your systems and data, the SIEM included. | SSO through OIDC with group mapping and SCIM, roles, and source visibility that limits which logs each team can see. Sign-ins, role changes and API key activity go to nano's own audit log. |
| CC6.8 | The entity implements controls to prevent or detect and act upon the introduction of unauthorized or malicious software. AICPA · 2017 TSC (2022) | Stop malware where you can, and catch it where you can't. | Collect your endpoint and anti-malware logs and alert on detections, disabled protection or unexpected software across hosts, in one place. |
| CC9.2 | The entity assesses and manages risks associated with vendors and business partners. AICPA · 2017 TSC (2022) | Every vendor that holds your data is a risk to assess and manage. | nano is software you run. It never receives your log data, so your SIEM vendor is not another place your security logs live. |
Auditors test samples from across the period. With the logs, alerts, cases and audit trail in one place you control, each sample is a search, not a ticket to a vendor.
Alerts with the rule, the events that matched and the time, for any sample period your auditor picks. Alerts
Cases holding the alert, the evidence, who worked it, the decision and the timeline. Case management
Case actions in the audit log with actor and time, and the playbook the case followed. Case audit events
Roles, SSO group mapping and source visibility, plus the audit log of sign-ins and permission changes, exportable as CSV or JSON. Platform audit log
Searches over the whole audit period, kept on storage you own for as long as you set. Storage and retention
nano's optional monitoring stack alerts when ingest stalls or drops events, so a gap in monitoring is itself noticed. Monitoring
nano installs with Docker Compose or with Helm on Kubernetes, on your servers or in your own cloud account. Your logs are collected, stored, searched and analyzed there, under your own controls.
Your data center, your own AWS, Azure or Google Cloud account, or an air-gapped network
Never receives your logs.
nano never receives your log data and has no standing access to your install. Support sees only what you choose to share. What your install sends to nano
Event retention defaults to 365 days and is yours to set, with older data tiered to your own object storage and still searchable. Storage and retention
Every license includes cases, playbooks, risk-based alerting, SSO and SCIM, high availability and air-gapped operation. Only GB/day and support level change the price. Air-gapped deployment
A SOC 2 report is an independent CPA firm's examination of a service organization's controls relevant to the AICPA Trust Services Criteria: security, and optionally availability, processing integrity, confidentiality and privacy. The criteria in use are the 2017 Trust Services Criteria, with points of focus revised in 2022.
Mainly CC7.2 (monitoring system components for anomalies and analyzing them), CC7.3 (evaluating security events to decide whether they are incidents) and CC7.4 (responding through a defined incident response program). CC4.1 covers evaluating whether controls are working, and CC6.1 and CC6.8 cover logical access and malicious software, where logs are a common source of evidence.
No. The Trust Services Criteria do not name tools, and your organization designs its own controls. A SIEM is a common way to meet the monitoring and incident criteria, and to produce the evidence an auditor tests.
The criteria set no retention period. Keep logs long enough to cover your audit period and your own incident response needs, and write the period into your policy. A Type 2 examination tests controls over a period, so evidence from across that period has to be available.
No. nano, LLC does not hold a SOC 2 report. nano is software you install and run in your own environment, not a service that holds your data: nano never receives your logs and has no standing access to your install, so it is not a vendor holding your data.
No. A SOC 2 report covers your organization's controls, policies and processes, examined by a CPA firm. A SIEM supplies part of the evidence for the monitoring and incident criteria. nano helps with that part.
If it supports controls in your system description, such as security monitoring and incident response, your auditor will look at it as part of those controls, including who can access it. Running it yourself puts it under the same access, change and monitoring controls as your other systems.
Last reviewed 14 November 2026. Regulations and guidance change, so read the current version at the source.
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.