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 nanoML2 and ML3 logging requirements, ISM retention, PSPF, and the move to ASD's Essentials.
Read Australia · ASDThe ISM security monitoring controls, control by control, including 12-month searchable retention.
Read Australia · CommonwealthWhat the Protective Security Policy Framework asks of Commonwealth entities' cyber security and logs.
Read Australia · ASDWhat an IRAP assessment is, why there is no IRAP certification, and where self-run software fits.
Read Australia · Critical infrastructure12-hour and 72-hour incident reporting, CIRMP, Systems of National Significance and ransomware payment reporting.
Read Australia · APRADetection and response, 72-hour notification to APRA, third parties, and how CPS 230 relates.
Read AustraliaWhy a SIEM you run in your own environment keeps Australian logs under your control, and what it exchanges with nano.
Read European UnionThe Annex 3.2 logging checklist, Article 23 reporting and national transposition status.
Read European UnionRTS 2024/1774 Article 12 line by line, the 4h/72h/1-month incident clock and third-party concentration risk.
Read European UnionSIEMs are Class I important products. The timeline, SBOMs, the 24-hour reporting clock and what to ask your vendor.
Read EuropeWhy logs that never reach a US vendor change the sovereignty and GDPR questions.
Read European Union · GDPRLogs are personal data. Minimization, retention, Article 32 security, 72-hour breach notice and transfers to a SIEM vendor.
Read India · CERT-In180-day log retention within the Indian jurisdiction, NIC/NPL time sync, 6-hour reporting and producing logs on demand.
Read India · DPDPAccess logs, one-year retention and 72-hour breach reporting under the DPDP Rules 2025, from 13 May 2027.
Read India · SEBIA SOC for regulated entities, two years of user access logs for critical systems, and where the localization clause stands.
Read India · RBI and IRDAIPayment data stored in India, audit-trail monitoring and the SOC under RBI, and IRDAI's guidelines for insurers.
Read IndiaCERT-In, DPDP, RBI, SEBI and IRDAI, and why a SIEM you run in your own Indian environment keeps the logs there.
Read United States · CMMCThe 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 · CJISWeekly review, one-year retention, the zero-cycle to 30 September 2027, and vendor personnel screening.
Read United States · HIPAA164.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 · NYDFSAudit trails kept three years, centralized logging and alerting for Class A companies, and 72-hour notice.
Read United StatesCMMC, 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 KingdomNCSC 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 CAFC1.a to C1.f outcome by outcome, C2 threat hunting, and where the Cyber Security and Resilience Bill stands.
Read CanadaBill 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 DSSAudit logs, automated daily review, 12 months kept with three immediately available, time sync and control-failure alerts.
Read Global · SOC 2CC7.2 to CC7.4, CC4.1 and CC6: where a SIEM you run supplies the evidence your auditor tests.
Read Global · ISO/IEC 27001Annex A 8.15 logging, 8.16 monitoring, 8.17 clock sync, and the incident and evidence controls in 5.25 to 5.28.
Read