CMMC · United States

CMMC audit logging, with the SIEM inside your enclave.

What CMMC Level 2 and NIST SP 800-171 ask of your audit logs, what DFARS 7012 adds, and why where your SIEM runs decides whether a SIEM vendor joins your assessment scope. nano runs inside your enclave, and your logs never reach nano.

Buy nano
Talk to sales
Your SIEM and your assessment scope

Log files are Security Protection Data.

The CMMC rule never names a SIEM. But it defines the data a SIEM holds, and it says what happens when an outside provider stores that data.

32 CFR 170.4 · Security Protection Data

"…includes but is not limited to: configuration data required to operate an SPA, log files generated by or ingested by an SPA…"

32 CFR 170.4 · External Service Provider

"In the CMMC Program, CUI or Security Protection Data (e.g., log data, configuration data), must be processed, stored, or transmitted on the ESP assets to be considered an ESP."

32 CFR 170.19(c)(2)(i), Table 4 · ESP with SPD

A cloud provider's services "are in the OSA's assessment scope and shall be assessed as Security Protection Assets". An ESP handling "Neither CUI nor SPD" "does not meet the CMMC definition of an ESP."

SaaS SIEM

The vendor stores your log data.

  • Your SIEM is a Security Protection Asset, and is assessed
  • The vendor stores Security Protection Data, so it is an External Service Provider
  • Its service comes into your assessment scope
  • If the logs carry CUI, its cloud must meet FedRAMP Moderate equivalency (DFARS 7012)
nano, run inside your enclave

The log data never leaves your boundary.

  • Your SIEM is a Security Protection Asset, and is assessed
  • No third-party SIEM provider stores your log data
  • No SIEM vendor in your assessment scope as an ESP
  • Air-gapped option: zero connectivity to nano
What the requirements say

Key 800-171 audit requirements, in their own words.

The requirements' own words, what they mean in practice, and where nano fits.

NIST SP 800-171 Rev. 2, 3.3 Audit and Accountability

Binding on contractors through DFARS 252.204-7012 and CMMC Level 2. Rev. 2 is the revision CMMC assesses today.

Ref What the text says In plain English How nano helps
3.3.1 "Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity." nist.gov · SP 800-171 Rev. 2 Log enough, and keep it long enough, to investigate and report misuse. The requirement sets no fixed number of days.
Collects logs from the sources you choose from the catalog into one store in your enclave. Retention defaults to 365 days and is yours to set, with older data tiered to your own object storage.
3.3.2 "Ensure that the actions of individual system users can be uniquely traced to those users, so they can be held accountable for their actions." nist.gov · SP 800-171 Rev. 2 Every action in the logs should lead back to one named person.
Search across sources by user, host or IP to follow one person's activity from sign-in to action, in one timeline.
3.3.4 "Alert in the event of an audit logging process failure." nist.gov · SP 800-171 Rev. 2 Know when logging stops working.
nano's optional monitoring stack, once turned on and routed to your alerting, warns when ingest stalls, drops events or fills its buffer.
3.3.5 "Correlate audit record review, analysis, and reporting processes for investigation and response to indications of unlawful, unauthorized, suspicious, or unusual activity." nist.gov · SP 800-171 Rev. 2 Review logs together, not system by system, and feed what you find into incident response.
Detections run across every source as events arrive; related alerts group into cases that hold the evidence and the timeline.
3.3.8 "Protect audit information and audit logging tools from unauthorized access, modification, and deletion." nist.gov · SP 800-171 Rev. 2 The logs, and the SIEM itself, are things to protect.
The log store sits on infrastructure you control, under your own access controls. Inside nano, roles and source visibility limit who can see and change what, and administrative actions are written to nano's own audit log.

DFARS 252.204-7012 (MAY 2024)

Binding contract clause for DoD contractors with covered defense information.

Ref What the text says In plain English How nano helps
(a) "'Rapidly report' means within 72 hours of discovery". acquisition.gov · DFARS 7012 When the clause requires you to report a cyber incident, the 72 hours run from discovery.
Detections raise alerts as events arrive, and cases hold the evidence you report from. Reporting to DoD stays with you.
(e) Contractors must "preserve and protect images of all known affected information systems… for at least 90 days" and keep "monitoring/packet capture data for at least 90 days". acquisition.gov · DFARS 7012 Keep images of affected systems, and monitoring or packet capture data, for at least 90 days.
Logs stay in your enclave for the retention you set. System images and packet capture are kept by your own tooling; nano holds the logs alongside them.
(b)(2)(ii)(D) "If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information… the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline…" acquisition.gov · DFARS 7012 If your logs carry CUI and a cloud provider stores them, that provider needs FedRAMP Moderate equivalency.
nano is software you run, not a cloud service that stores your logs. Your logs stay on infrastructure you already control.
DFARS 252.204-7012 · rapid reporting

72 hours to report. 90 days to preserve.

The clock starts at discovery. What you report, and what you keep afterward, comes from the logs you already hold.

  1. 0 h

    Discover a cyber incident

    One the clause requires you to report.

  2. 72 h

    Report to DoD

    "'Rapidly report' means within 72 hours of discovery".

  3. 90 days

    Preserve evidence

    Images of affected systems and monitoring or packet capture data, for at least 90 days.

DFARS 252.204-7012 (MAY 2024), paragraphs (a) and (e).
CMMC phases

Phase 2 is in effect. Each solicitation sets the level.

Phases come from 32 CFR 170.3(e) and the date the acquisition rule took effect. Each solicitation states the CMMC level and assessment it requires.

  1. 16 Dec 2024 In effect

    CMMC program rule effective

    32 CFR Part 170 takes effect, including the ESP and Security Protection Asset rules.

    ecfr.gov · 32 CFR 170 ↗
  2. 10 Nov 2025 In effect

    Phase 1 begins

    The CMMC acquisition rule (DFARS Case 2019-D041) takes effect, which starts Phase 1.

    federalregister.gov · 2025-17359 ↗
  3. 10 Nov 2026 In effect

    Phase 2 begins

    32 CFR 170.3(e)(2): one calendar year after Phase 1. CMMC Status of Level 2 (C3PAO) is added for applicable solicitations and contracts as a condition of award; DoD may apply it at an option period instead. Each solicitation states what it requires.

    ecfr.gov · 32 CFR 170 ↗
  4. 10 Nov 2027 Next

    Phase 3 begins

    32 CFR 170.3(e)(3): one calendar year after Phase 2. Level 2 (C3PAO) for all applicable solicitations and contracts, and Level 3 (DIBCAC) where it applies.

    ecfr.gov · 32 CFR 170 ↗
  5. 10 Nov 2028 Next

    Phase 4, full implementation

    32 CFR 170.3(e)(4): one calendar year after Phase 3. CMMC requirements apply in all applicable solicitations and contracts.

    ecfr.gov · 32 CFR 170 ↗
Inside the enclave

Run it where your CUI already lives.

nano installs with Docker Compose or with Helm on Kubernetes, on infrastructure inside your boundary. Sources send logs to it over your network, and it parses, stores, searches and runs detections on them there.

Your environment

Your CMMC enclave: your servers, your AWS GovCloud (US) or Azure Government account, or an air-gapped network

01 · Sources
  • firewall
  • VPN
  • identity provider
  • Windows
  • Linux / SSH
  • file server
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 enclave. Log data is never sent to nano.
Your servers

On hardware in your enclave.

Single node, or multi-node with high availability. Logs and backups stay on storage you own, for as long as your retention policy says. Storage and retention

Your cloud account

Commercial or government regions.

Run nano in your own AWS, Azure or Google Cloud account, including AWS GovCloud (US) or Azure Government if that is where your enclave is. Your existing cloud controls apply to the log store.

Air-gapped

Zero connectivity to nano.

Included with every license: a signed image bundle, content packs you import by hand and an offline license. See air-gapped deployment, and the United States guide for the other US rules.

FAQ

Questions we get asked.

What is CMMC?

The Cybersecurity Maturity Model Certification (CMMC) program, set out in 32 CFR Part 170, is how the Department of Defense checks that contractors protect Federal Contract Information (FCI) and Controlled Unclassified Information (CUI). Level 2 is built on the security requirements of NIST SP 800-171, which DFARS 252.204-7012 already requires contractors with covered defense information to implement.

What does NIST SP 800-171 require for audit logging?

The 3.3 Audit and Accountability family of Rev. 2. Among them: create and retain audit logs to the extent needed to investigate and report unauthorized activity (3.3.1), trace actions to individual users (3.3.2), alert on audit logging process failure (3.3.4), correlate review, analysis and reporting (3.3.5), and protect audit information and logging tools from unauthorized access, modification and deletion (3.3.8).

How long must audit logs be kept for CMMC Level 2?

NIST SP 800-171 sets no fixed period. Rev. 2 asks you to keep logs "to the extent needed" for monitoring, investigation and reporting, and Rev. 3 says to retain audit records for a time period consistent with your records retention policy. DFARS 252.204-7012 separately requires images of affected systems and monitoring or packet capture data to be kept for at least 90 days. Set your period in policy and size storage for it.

Is CMMC Level 2 certification required now?

Phase 1 began on 10 November 2025, when the CMMC acquisition rule took effect. Phase 2 began on 10 November 2026, one calendar year later under 32 CFR 170.3(e)(2): it adds CMMC Status of Level 2 (C3PAO) for applicable solicitations and contracts as a condition of award. Phase 3 begins on 10 November 2027 and Phase 4, full implementation, on 10 November 2028. Which level and which kind of assessment a contract needs is set in each solicitation, so check yours and the current DoD guidance.

Is my SIEM in CMMC scope?

Yes. Under 32 CFR 170.4, Security Protection Assets are "assets providing security functions or capabilities for the OSA's CMMC Assessment Scope", and Security Protection Data includes "log files generated by or ingested by an SPA". A SIEM is a Security Protection Asset and is assessed against the Level 2 requirements relevant to what it does, whether you run it yourself or buy it as a service.

Is a SaaS SIEM an External Service Provider under CMMC?

On a plain reading of the rule text, yes. 32 CFR 170.4 says an outside party is an ESP when CUI or Security Protection Data (for example, log data) is processed, stored or transmitted on its assets, and 170.19 puts an ESP's services in your assessment scope. A SaaS SIEM stores your log data, so its service comes into your scope; if the logs carry CUI, its cloud must also meet FedRAMP Moderate equivalency under DFARS 7012. The rule does not name SIEMs, so confirm your scoping with your C3PAO or assessor.

Where should the SIEM sit in a CMMC enclave?

Inside it, if you want no third-party SIEM provider in your scope. nano runs on your own servers in the enclave, in your own cloud account (including AWS GovCloud (US) or Azure Government if your enclave is there), on Kubernetes, or fully air-gapped. A connected install sends nano only a daily license check-in and one GB/day number, and downloads content; air-gapped installs have zero connectivity to nano.

Does CMMC require NIST SP 800-171 Rev. 3?

No. 32 CFR 170.16 incorporates NIST SP 800-171A of June 2018, the Rev. 2 assessment guide, so Rev. 2 is the working baseline for CMMC today. Rev. 3 (May 2024) restructures the requirements, for example 03.03.03 on generating and retaining audit records and 03.03.05 on correlating records across repositories.

Is nano CMMC certified or FedRAMP authorized?

No. Tools are not CMMC certified: your organization is assessed, and your SIEM is assessed as part of it. nano, LLC holds no CMMC certification and no FedRAMP authorization. FedRAMP authorizes cloud services; nano is software you operate in your own environment.

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