| CMMC and NIST SP 800-171 nist.gov · SP 800-171 Rev. 2 ↗acquisition.gov · DFARS 7012 ↗ecfr.gov · 32 CFR 170 ↗ | DoD contractors and subcontractors handling FCI or CUI, through DFARS 252.204-7012 and 32 CFR Part 170 | The 800-171 Rev. 2 audit family: create and retain audit logs, trace actions to individual users, alert on logging failures, correlate review, protect audit information. DFARS 7012: report within 72 hours, keep images and packet capture for at least 90 days. Under 32 CFR 170.4, log files ingested by a security tool are Security Protection Data. | Keeps a vendor out of scopeYour SIEM is still a Security Protection Asset and is assessed. But it runs inside your enclave, so no third-party SIEM provider stores your log data. Under 32 CFR 170.4, storing that data is what makes a SaaS SIEM provider an External Service Provider in your scope. |
| CJIS Security Policy v6.1 le.fbi.gov · CJIS v6.1 ↗ | Agencies with access to criminal justice information (CJI), and contractors through the CJIS Security Addendum | Review audit records weekly (AU-6) and retain them for at least one year (AU-11). Vendor staff with unescorted access to unencrypted CJI need fingerprint-based record checks (PS-3), and private contractors sign the Security Addendum (SA-9). | Keeps a vendor out of scopenano runs in your agency's environment. nano has no standing access to your install. Support sees only what you choose to share. nano staff are not in your CJI screening chain for log data. You don't need to send support any CJI, and nano will sign the CJIS Security Addendum. |
| HIPAA Security Rule, 45 CFR 164.312(b) ecfr.gov · 45 CFR 164 ↗ | Covered entities and business associates | Audit controls that "record and examine activity" in systems with electronic PHI, and regular review of activity records. The Security Rule sets no retention period for logs. | Keeps a vendor out of scopeLogs that carry PHI stay in your environment. nano never receives them and has no standing access to your install, so no SIEM vendor joins your business associate chain for log data. nano holds no HIPAA certification (there is none). If your support cases may include PHI, nano will sign a business associate agreement. |
| NYDFS, 23 NYCRR Part 500 dfs.ny.gov · 23 NYCRR 500 ↗ | DFS-licensed covered entities; 500.14(b) applies to Class A companies only | Audit trails designed to detect and respond to cybersecurity events, kept at least three years (500.6). Class A: "a solution that centralizes logging and security event alerting" since 1 May 2025, unless the CISO approves compensating controls in writing (500.14(b)). Notice within 72 hours (500.17). | One fewer service providerCentralizes logging and alerting in your own environment, with retention on storage you own. That leaves one fewer third-party service provider holding your security logs. |
| FTC Safeguards Rule, 16 CFR 314.4(c)(8) ecfr.gov · 16 CFR 314 ↗ | Non-bank financial institutions under FTC jurisdiction, such as auto dealers, mortgage brokers, tax preparers and fintechs | "monitor and log the activity of authorized users and detect unauthorized access or use of, or tampering with, customer information by such users." Notify the FTC within 30 days of a notification event involving at least 500 consumers (314.4(j)). | One fewer service providerCollects user activity from the systems that hold customer information and runs your detections on it. It removes one service provider to oversee; the rule itself does not prefer self-hosting. |
| SEC Form 8-K Item 1.05 and Regulation S-P sec.gov · Form 8-K ↗ecfr.gov · 17 CFR 248.30 ↗ | SEC registrants (8-K); broker-dealers, investment companies, registered advisers and transfer agents (Reg S-P) | File Item 1.05 within four business days after determining that a cybersecurity incident is material. Reg S-P: give notice as soon as practicable, and no later than 30 days after becoming aware of unauthorized access to or use of customer information. | No scope differenceWhere logs live makes no difference here. What helps is having the evidence for the materiality decision and the notice in one searchable place. |
| OMB M-26-14 (federal agencies) whitehouse.gov · M-26-14 ↗fedramp.gov · scope ↗ | Federal civilian executive agencies; national security systems are excluded | Replaces M-21-31, which it rescinds. Logs actively searchable for at least 6 months after creation and retrievable for a year. Agencies "may consider collecting logs in enterprise security information and event management software or equivalent". | Software you operateKeep recent logs searchable on fast disk and tier older ones to your own object storage. FedRAMP authorizes cloud services; nano is software you operate in your own environment. |
| PCI DSS v4.0.1, Requirement 10 (global) PCI DSS v4.0.1 ↗ | Entities that store, process or transmit cardholder data; binding by contract, not by law | Audit logs enabled for all system components (10.2.1), reviewed at least daily (10.4.1), with automated review required since 31 March 2025 (10.4.1.1). Keep 12 months, the most recent three immediately available (10.5.1). | No scope differenceSelf-hosting does not shrink PCI scope. What helps: 12 months on your own storage under a per-GB/day license, and detections that automate review. |
| CIRCIA (not yet in force) reginfo.gov · CIRCIA ↗federalregister.gov · 2024-06526 ↗ | Covered entities in critical infrastructure sectors, as the final rule will define | The 2024 proposal: report covered incidents within 72 hours and ransom payments within 24 hours, and preserve data for at least two years. The final rule has been at OIRA for review since 1 October 2026. | No scope differenceIf the proposal holds, long retention on storage you own is what helps. |