Compliance guides

Logging requirements, rule by rule.

What each regulation asks of your security logs, in plain English, with links to the primary sources. You run nano in your own environment, so your logs never reach us. These guides are not legal advice, and using nano does not make you compliant.

What your install sends to nano
Australia

Essential Eight event logging

ML2 and ML3 logging requirements, ISM retention, PSPF, and the move to ASD's Essentials.

Read
Australia · ASD

ISM event logging controls

The ISM security monitoring controls, control by control, including 12-month searchable retention.

Read
Australia · Commonwealth

PSPF and the Essential Eight

What the Protective Security Policy Framework asks of Commonwealth entities' cyber security and logs.

Read
Australia · ASD

IRAP and PROTECTED environments

What an IRAP assessment is, why there is no IRAP certification, and where self-run software fits.

Read
Australia · Critical infrastructure

SOCI Act logging and reporting

12-hour and 72-hour incident reporting, CIRMP, Systems of National Significance and ransomware payment reporting.

Read
Australia · APRA

APRA CPS 234 security monitoring

Detection and response, 72-hour notification to APRA, third parties, and how CPS 230 relates.

Read
Australia

Data sovereignty for security logs

Why a SIEM you run in your own environment keeps Australian logs under your control, and what it exchanges with nano.

Read
European Union

NIS2 logging requirements

The Annex 3.2 logging checklist, Article 23 reporting and national transposition status.

Read
European Union

DORA logging requirements

RTS 2024/1774 Article 12 line by line, the 4h/72h/1-month incident clock and third-party concentration risk.

Read
European Union

Cyber Resilience Act

SIEMs are Class I important products. The timeline, SBOMs, the 24-hour reporting clock and what to ask your vendor.

Read
Europe

Digital sovereignty and the CLOUD Act

Why logs that never reach a US vendor change the sovereignty and GDPR questions.

Read
European Union · GDPR

GDPR and security logs

Logs are personal data. Minimization, retention, Article 32 security, 72-hour breach notice and transfers to a SIEM vendor.

Read
India · CERT-In

CERT-In Directions: logs and 6-hour reporting

180-day log retention within the Indian jurisdiction, NIC/NPL time sync, 6-hour reporting and producing logs on demand.

Read
India · DPDP

DPDP Rules: logging and one-year retention

Access logs, one-year retention and 72-hour breach reporting under the DPDP Rules 2025, from 13 May 2027.

Read
India · SEBI

SEBI CSCRF: SOC and log retention

A SOC for regulated entities, two years of user access logs for critical systems, and where the localization clause stands.

Read
India · RBI and IRDAI

RBI and IRDAI: banking and insurance logging

Payment data stored in India, audit-trail monitoring and the SOC under RBI, and IRDAI's guidelines for insurers.

Read
India

Security logs that stay in India

CERT-In, DPDP, RBI, SEBI and IRDAI, and why a SIEM you run in your own Indian environment keeps the logs there.

Read
United States · CMMC

CMMC Level 2 and NIST SP 800-171 audit logging

The 3.3 audit family, DFARS 7012, and why a SIEM inside your enclave leaves no third-party SIEM provider in your assessment scope.

Read
United States · CJIS

CJIS Security Policy v6.1 audit logging

Weekly review, one-year retention, the zero-cycle to 30 September 2027, and vendor personnel screening.

Read
United States · HIPAA

HIPAA audit controls and log retention

164.312(b), activity review, why six years is not a log rule, and keeping PHI-bearing logs out of a vendor's hands.

Read
United States · NYDFS

NYDFS Part 500 and financial services

Audit trails kept three years, centralized logging and alerting for Class A companies, and 72-hour notice.

Read
United States

Security logs inside your own boundary

CMMC, CJIS, HIPAA, NYDFS, the FTC Safeguards Rule, SEC, M-26-14 and PCI DSS, and where a SIEM you run yourself changes the picture.

Read
United Kingdom

Control and evidence for UK security logs

NCSC CAF objective C, the Cyber Security and Resilience Bill, the NHS DSPT and UK GDPR transfers, for a SIEM you run yourself.

Read
United Kingdom · NCSC CAF

NCSC CAF objective C: security monitoring

C1.a to C1.f outcome by outcome, C2 threat hunting, and where the Cyber Security and Resilience Bill stands.

Read
Canada

Canadian security logs, under Canadian control

Bill C-8 and the CCSPA, OSFI B-13, Quebec Law 25 and Protected B, and why a US vendor that never receives your logs has nothing to hand over.

Read
Global · PCI DSS

PCI DSS Requirement 10 logging

Audit logs, automated daily review, 12 months kept with three immediately available, time sync and control-failure alerts.

Read
Global · SOC 2

SOC 2 monitoring and incident evidence

CC7.2 to CC7.4, CC4.1 and CC6: where a SIEM you run supplies the evidence your auditor tests.

Read
Global · ISO/IEC 27001

ISO 27001 logging and monitoring controls

Annex A 8.15 logging, 8.16 monitoring, 8.17 clock sync, and the incident and evidence controls in 5.25 to 5.28.

Read