Retention is your setting.
Event retention defaults to 365 days and you set it through the API. Size disk for your daily ingest over the window, and tier older data to your own object storage, where it stays searchable. Storage and retention
What CERT-In's 2022 Directions ask of your logs: 180 days of logs from every ICT system, kept in India, handed over on request, incidents reported within 6 hours and clocks synced to Indian time servers. And how a SIEM you run in your own Indian environment supports each one.
The clock starts when you notice an incident, or are told about one. Logs go to CERT-In with the report or whenever CERT-In directs, so they need to be ready when it starts.
Or have one brought to your notice. Decide whether it is an Annexure I incident.
Incidents listed in Annexure I of the Directions, within 6 hours of noticing them.
Logs go to CERT-In along with the incident report, or when CERT-In orders or directs.
The Directions' own words, what they mean in practice, and where nano fits.
Binding on "service providers, intermediaries, data centres, body corporate and Government organisations".
| Ref | What CERT-In says | In plain English | How nano helps |
|---|---|---|---|
| Direction (iv) | "shall mandatorily enable logs of all their ICT systems and maintain them securely for a rolling period of 180 days and the same shall be maintained within the Indian jurisdiction." cert-in.org.in · Directions 2022 | Log every ICT system, keep at least the last 180 days, keep them secure, and keep them in India. | Retention is a setting on your own event store (365 days by default), so set at least 180 and size the storage for it. The store runs in the Indian cloud region or data center you choose, and nano never holds a copy. |
| Direction (iv) | "These should be provided to CERT-In along with reporting of any incident or when ordered / directed by CERT-In." cert-in.org.in · Directions 2022 | Be ready to hand logs over with an incident report, or whenever CERT-In asks. | The logs are in your own instance: search them by time range and source, and download the results as CSV from a report. Nothing has to be requested from a vendor first. |
| Direction (ii) | "shall mandatorily report cyber incidents as mentioned in Annexure I to CERT-In within 6 hours of noticing such incidents or being brought to notice about such incidents." cert-in.org.in · Directions 2022 | Six hours from when you notice an incident, or are told about one. You have to know quickly. | Detection rules run as events arrive and raise alerts; related alerts group into cases holding the evidence and timeline your report draws on. Reporting to CERT-In stays with you. |
| Direction (i) | "shall connect to the Network Time Protocol (NTP) Server of National Informatics Centre (NIC) or National Physical Laboratory (NPL) or with NTP servers traceable to these NTP servers". Entities spanning several countries may use another source, but it "shall not deviate from NPL and NIC." cert-in.org.in · Directions 2022 | Every system's clock follows Indian reference time, so events from different systems line up. | Clock sync is a host setting. Because you run the servers, you point the hosts running nano, and your log sources, at NIC or NPL time servers yourself. |
Guidance. The FAQ document states that it is not a legal document.
| Ref | What CERT-In says | In plain English | How nano helps |
|---|---|---|---|
| FAQ Q35 | "The logs may be stored outside India also as long as the obligation to produce logs to CERT-In is adhered to by the entities in a reasonable time." cert-in.org.in · FAQs May 2022 | CERT-In's guidance accepts logs stored offshore, if you can still produce them in reasonable time. | With nano running in your own Indian environment, the logs are in India and producible by you, so the question does not arise. |
| FAQ Q36 | "Any service provider offering services to the users in the country needs to enable and maintain logs and records of financial transactions in Indian jurisdiction." cert-in.org.in · FAQs May 2022 | Next to Q35, a narrower rule: service providers keep financial-transaction logs in India. | Logs stay where you run nano. If that is an Indian region or data center, they are in India. |
| FAQ Q37 | Lists the logs in scope as "Firewall logs, Intrusion Prevention Systems logs, SIEM logs, web / database/ mail / FTP / Proxy server logs, Event logs of critical systems, Application logs, ATM switch logs, SSH logs, VPN logs etc." The list is "not exhaustive", and "both successful as well as unsuccessful events shall be recorded". cert-in.org.in · FAQs May 2022 | Think wide: network, server, application and access logs, failures as well as successes. | Every install starts with no log sources. You choose the sources you run from the catalog and onboard each one, and the SIEM's own logs stay in your environment too. |
| FAQ Q40 | Using IST on every clock is not mandatory, but "time zone information shall also be recorded". cert-in.org.in · FAQs May 2022 | Clocks can run in another time zone, as long as the time zone is recorded with the time. | Check that each source you onboard sends timestamps with a time zone or offset, and set the hosts you run accordingly. |
CERT-In issues Directions No. 20(3)/2022-CERT-In under section 70B(6) of the IT Act, 2000.
cert-in.org.in · Directions 2022 ↗They take effect 60 days after issue, at the end of June 2022.
cert-in.org.in · Directions 2022 ↗MSMEs, and the customer-validation duty for data centers, VPS, cloud and VPN providers, were given until this date.
pib.gov.in · extension ↗CERT-In's FAQ lists examples of the logs in scope, and says the list is not exhaustive.
Every nano install starts with zero log sources. You pick the sources you run from the catalog, onboard each one, and decide how long to keep them. Then raise alerts, work incidents in case management and export logs as CSV with reports.
nano runs in your own account in an Indian cloud region, in your data center, or air-gapped. Logs are collected, stored and searched there, for the retention you set.
Your account in an Indian cloud region, your data center, or an air-gapped network
Never receives your logs.
Event retention defaults to 365 days and you set it through the API. Size disk for your daily ingest over the window, and tier older data to your own object storage, where it stays searchable. Storage and retention
When CERT-In asks for logs, you search your own instance and export what is asked for. nano has no copy to produce and no standing access to your install.
Included with every license: a signed image bundle, content packs you import by hand and an offline license. See air-gapped deployment, and the India guide for what a connected install sends.
CERT-In, the Indian Computer Emergency Response Team, is India's national agency for responding to cyber security incidents under section 70B of the Information Technology Act, 2000. On 28 April 2022 it issued Directions under section 70B(6) on log retention, incident reporting and clock synchronization, usually called the CERT-In Directions or CERT-In guidelines.
The Directions are addressed to "service providers, intermediaries, data centres, body corporate and Government organisations". CERT-In's FAQ (Q26) says they apply to any entity whatsoever, in the matter of cyber incidents. In practice, most organizations running ICT systems in India should assume they are in scope.
Direction (iv) requires logs of all ICT systems to be maintained securely "for a rolling period of 180 days", within the Indian jurisdiction. That is a minimum; other rules can ask for more, such as the DPDP Rules' one year for logs of personal data processing from 13 May 2027.
The Directions say the logs "shall be maintained within the Indian jurisdiction". CERT-In's FAQ (Q35) says they "may be stored outside India also as long as the obligation to produce logs to CERT-In is adhered to by the entities in a reasonable time", while Q36 says service providers serving users in India keep logs of financial transactions in India. The FAQ says it is not a legal document. Running nano in your own Indian cloud region or data center keeps the logs in India and under your control, which removes the jurisdiction question.
Direction (ii) requires the incidents listed in Annexure I of the Directions to be reported to CERT-In "within 6 hours of noticing such incidents or being brought to notice about such incidents". Logs are provided to CERT-In along with the incident report or when CERT-In directs. Check Annexure I for the incident types in scope.
Logs of all ICT systems. CERT-In's FAQ (Q37) gives examples: firewall, intrusion prevention, SIEM, web, database, mail, FTP and proxy server logs, event logs of critical systems, application logs, ATM switch logs, SSH logs and VPN logs. The list is not exhaustive, and both successful and unsuccessful events are to be recorded.
Direction (i) requires connecting to the NTP servers of the National Informatics Centre (NIC) or the National Physical Laboratory (NPL), or to NTP servers traceable to them. Entities with infrastructure in several countries may use another source, but it "shall not deviate from NPL and NIC." The FAQ (Q40) says IST is not mandatory but time zone information must be recorded.
Non-compliance is punishable under section 70B(7) of the IT Act with imprisonment of up to one year, a fine of up to one crore rupees, or both. The Jan Vishwas (Amendment of Provisions) Act, 2023 raised the fine from one lakh rupees, effective 30 November 2023.
No. nano is software, not an audit firm, and is not on CERT-In's list of empanelled auditors. nano, LLC holds no CERT-In empanelment, approval or certification. It is the SIEM you run to collect, keep and search the logs they ask for.
Last reviewed 13 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.