Your period, your storage.
Event retention defaults to 365 days and is yours to set: at least 180 days for CERT-In, longer if your policy says so. Older data tiers to your own object storage and stays searchable. Storage and retention
What RBI asks of banks and payment providers, and what IRDAI asks of insurers: audit trails and log monitoring, a SOC, payment data kept in India, and CERT-In's 180 days and 6 hours. And how a SIEM you run in your own Indian environment supports each one.
The regulators' own words, what they mean in practice, and where nano fits.
In effect since 1 April 2024 for commercial banks, NBFCs in the Top, Upper and Middle layers, Credit Information Companies and All India Financial Institutions. It sets no log retention period.
| Ref | What the regulator says | In plain English | How nano helps |
|---|---|---|---|
| Para 15(a) | "Every IT application which can access or affect critical or sensitive information, shall have necessary audit and system logging capability and should provide audit trails." rbi.org.in · IT governance MD | Applications that touch critical or sensitive information must log, and keep audit trails. | Collects audit and system logs from the applications and infrastructure you onboard into one store in your environment. |
| Para 15(b) | Audit trails "must be detailed enough to facilitate the conduct of audit, serve as forensic evidence when required and assist in dispute resolution, including for non-repudiation purposes." rbi.org.in · IT governance MD | Detailed enough for auditors, investigators and disputes. How long to keep them is left to your business, regulatory and legal requirements. | Retention is a setting on your own event store (365 days by default), so you set the period your policy requires and keep the logs on storage you own. |
| Para 15(c) | "REs shall put in place a system for regularly monitoring the audit trails and system logs to detect any unauthorised activity." rbi.org.in · IT governance MD | Someone, or something, has to watch the logs for unauthorized activity, regularly. | Detection rules run across every source as events arrive and raise alerts; related alerts group into cases with the evidence and timeline. |
| Para 24(d) | "The CISO's Office shall manage and monitor Security Operations Centre (SOC) and drive cyber security related projects." rbi.org.in · IT governance MD | The SOC sits with the CISO's office. | The SIEM your SOC works in, run in your own environment, under your own access controls. |
| Ref | What the regulator says | In plain English | How nano helps |
|---|---|---|---|
| RBI/2017-18/153 | "All system providers shall ensure that the entire data relating to payment systems operated by them are stored in a system only in India." This includes "the full end-to-end transaction details". rbi.org.in · payment data | Payment system providers keep payment data in India. For the foreign leg of a transaction, the data can also be stored abroad. | If your logs carry payment data, they stay where you run nano: your Indian cloud region or data center. nano never receives a copy. |
| RBI/2015-16/418 | "it is mandated that a SOC (Security Operations Centre) be set up at the earliest, if not yet been done." rbi.org.in · Cyber Security Framework | Scheduled commercial banks have been required to run a SOC since 2016. | Gives that SOC one place to collect, search and detect across its logs. |
Issued 6 April 2026 to all insurers, insurance intermediaries and the Insurance Information Bureau of India, revising the 2023 guidelines.
| Ref | What the regulator says | In plain English | How nano helps |
|---|---|---|---|
| Compliance | "Regulated Entities shall adhere to directions issued by Cert-In from time to time including relating to information security practices, procedures, prevention, response and reporting of cyber incidents". irdai.gov.in · Guidelines 2026 | Insurers follow the CERT-In Directions as well as IRDAI's own guidelines. | Run nano in an Indian cloud region or your own data center, with the retention and reporting below. |
| Log retention | "ICT infrastructure logs shall be maintained for a rolling period of 180 days and within the Indian jurisdiction". irdai.gov.in · Guidelines 2026 | Keep ICT logs for a rolling 180 days, in India. | Set retention to at least 180 days (the default is 365) and run nano in an Indian cloud region or your own data center, so the logs never leave India. |
| 3.4 Escalations | "Enterprise wide monitoring of Information security incidents shall be done by SOC team on 24X7 basis", and "Continuous monitoring of IT logs … shall be done through Security Information and Event Monitoring (SIEM) and monitored by Security Operations Centre (SOC)". irdai.gov.in · Guidelines 2026 | A 24x7 SOC, watching IT logs through a SIEM. | nano is that SIEM, run in your own environment: detections over every source you onboard, alerts for the SOC, and cases for each investigation. |
| 3.6 Notification | "Organization shall mandatorily report cyber incidents to Cert-In within 6 hours of noticing or being brought to notice about such incidents with a copy to IRDAI and other concerned regulators / authorities." irdai.gov.in · Guidelines 2026 | Six hours to CERT-In, with a copy to IRDAI. | Alerts as events arrive, and cases that hold what you report from. Reporting stays with you. |
The clock starts when you notice an incident, or are told about one. The logs need to be searchable before it starts.
Or have one brought to your notice.
With a copy to IRDAI and other concerned regulators or authorities.
IRDAI's guidelines say logs are made available to law enforcement, IRDAI, CERT-In and CSIRT-Fin as and when required.
nano runs in your own account in an Indian cloud region, in your data center, or air-gapped. Logs are collected, stored, searched and monitored 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 is yours to set: at least 180 days for CERT-In, longer if your policy says so. Older data tiers to your own object storage and stays searchable. Storage and retention
nano has no standing access to your install. Support sees only what you choose to share. A connected install sends a daily license check-in and one GB/day number, and downloads content and feeds. What your install sends 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 India guide for the other Indian rules.
RBI's circular of 2 June 2016, Cyber Security Framework in Banks (RBI/2015-16/418), told scheduled commercial banks to put in place a Board-approved cyber security policy and mandated a Security Operations Center. The Master Direction on IT Governance, Risk, Controls and Assurance Practices of 7 November 2023, in effect since 1 April 2024, consolidates and updates RBI's IT governance instructions for banks and other regulated entities.
Commercial banks, NBFCs in the Top, Upper and Middle layers under RBI's scale-based regulation, Credit Information Companies, and All India Financial Institutions, as listed in paragraph 2 of the Master Direction.
The 2023 Master Direction does not set a log retention period. Paragraph 15 requires audit trails detailed enough for audit, forensic evidence and dispute resolution, satisfying business, regulatory and legal requirements, and regular monitoring of audit trails and system logs. Many entities also fall under the CERT-In Directions, which require 180 days of ICT logs within the Indian jurisdiction.
RBI's circular of 6 April 2018 on storage of payment system data requires all payment system providers to store the entire data relating to the payment systems they operate in a system only in India, including full end-to-end transaction details. For the foreign leg of a transaction, the data can also be stored in the foreign country.
The IRDAI Information and Cyber Security Guidelines, 2026 require regulated entities to keep ICT infrastructure logs for a rolling 180 days within the Indian jurisdiction and to adhere to CERT-In's directions. They require enterprise-wide monitoring of security incidents by a SOC team on a 24x7 basis, continuous monitoring of IT logs through a SIEM by the SOC, and reporting cyber incidents within 6 hours to CERT-In, with a copy to IRDAI.
All insurers, insurance intermediaries such as brokers, corporate agents, web aggregators and TPAs, and the Insurance Information Bureau of India. The 2026 guidelines were issued on 6 April 2026 and apply from the current financial year.
For insurers, IRDAI's 2026 guidelines say ICT infrastructure logs shall be maintained for a rolling 180 days within the Indian jurisdiction, so keep them in India. For banks, RBI's 2018 circular requires payment system data to be stored only in India; for other logs, the CERT-In Directions say they shall be maintained within the Indian jurisdiction, while CERT-In's FAQ says they may be stored outside India if they can be produced in reasonable time. Running nano in your own Indian cloud region or data center keeps the logs in India either way.
No. Neither regulator approves SIEM software, and nano, LLC holds no RBI or IRDAI approval, empanelment or certification. It is the SIEM your SOC runs to collect, keep, monitor and search the logs these rules ask for.
Last reviewed 14 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.