Your SOC, your SIEM.
nano is built for this model: you run it in your own environment and your SOC works in it.
What SEBI's Cybersecurity and Cyber Resilience Framework asks of your logs: a SOC, two years of user access logs for critical systems with six months online, and a localization clause now in abeyance. And how a SIEM you run yourself supports each one.
The CSCRF requires a SOC for all regulated entities, except client-based stock brokers with fewer than 100 clients, and lets each entity choose how to run it.
nano is built for this model: you run it in your own environment and your SOC works in it.
Small-size and self-certification REs are onboarded to the Market SOC under the CSCRF.
Your provider's tooling applies. If its tools are SaaS hosted outside India, PR.DS.S2's exemption conditions are the ones to read.
The framework's own words, what they mean in practice, and where nano fits.
Binding on SEBI-regulated entities (REs).
| Ref | What SEBI says | In plain English | How nano helps |
|---|---|---|---|
| SOC | "CSCRF has mandated SOC for all REs (except client-based stock brokers having less than 100 clients)." REs may use their own or group SOC, the Market SOC run by NSE and BSE, or a third-party managed SOC. sebi.gov.in · CSCRF | Every regulated entity needs a Security Operations Center, except stock brokers with fewer than 100 clients. You choose the model. | Gives an own or group SOC the SIEM to run on: logs from the sources you choose, detections and alerts, and cases that hold the evidence. |
| PR.AA (e) | Records of user access to critical systems are logged, and "Such logs shall be maintained and stored in a secure location for a time period not less than two (2) years (atleast 6 months in online mode and rest in archival mode)." sebi.gov.in · CSCRF | Keep user access logs for critical systems at least two years: the first six months searchable, the rest archived. | Retention is a setting on your own event store (365 days by default). Keep recent months on fast disk and tier older data to your own object storage, where it stays searchable. |
| PR.AA.S8 | REs ensure "all logs sources are being identified and their respective logs are being collected", indicatively "system logs, application logs, network logs, database logs, security logs, performance logs, audit trail logs, and event logs." Retention follows government rules such as the IT Act, the DPDP Act and CERT-In, and "monitoring of all logs of events and incidents shall be done." sebi.gov.in · CSCRF | Find every log source, collect it, keep it as the wider law requires, and monitor it. | Every install starts with zero log sources. You choose the sources you run from the catalog and onboard each one, then detections monitor them as events arrive. |
| PR.DS.S2 | Regulatory data is kept "within the legal boundaries of India". IT and cybersecurity data sent to a global or international SOC or to "SaaS based cybersecurity solutions" is exempt, subject to annual review by the IT Committee, annual Board approval, and production to SEBI, CERT-In or another government agency "within a reasonable time not exceeding 48 hours from the time of request." sebi.gov.in · CSCRF | The localization clause and its SaaS exemption. The clause has been in abeyance since 31 December 2024. | With nano in your own environment, security logs never go to an offshore SaaS tool, so the exemption's review, Board approval and 48-hour production conditions do not arise for them. |
Clarifications for SEBI REs that are also regulated by another regulator, such as banks.
| Ref | What SEBI says | In plain English | How nano helps |
|---|---|---|---|
| Para 5.2 | "The scope of CSCRF shall be limited to only those systems/ applications/ infrastructure/ processes which are exclusively used for SEBI regulated activities." sebi.gov.in · CIR/2025/119 | For entities under several regulators, CSCRF covers only the systems used exclusively for SEBI-regulated activities. Shared infrastructure can still come into SEBI's audit scope if the primary regulator does not cover it. | Collect from the systems in scope, and keep their logs for the CSCRF period, alongside what your primary regulator asks for. |
| Table 1 | Lists "Data Localisation (currently in abeyance vide SEBI circular SEBI/HO/ ITD-1/ITD_CSC_EXT/P/CIR/2024/184 dated December 31, 2024)". sebi.gov.in · CIR/2025/119 | SEBI confirms the localization clause is in abeyance. SEBI does not currently require security logs to stay in India. | Logs stay wherever you run nano. If that is an Indian cloud region or your own data center, they are in India in any case. |
SEBI issues the Cybersecurity and Cyber Resilience Framework, CIR/2024/113.
sebi.gov.in · CSCRF ↗SEBI's clarifications circular CIR/2024/184 keeps the data localization standard (PR.DS.S2) in abeyance until further notification.
sebi.gov.in · CIR/2024/184 ↗CIR/2025/119 sets the Principle of Exclusivity for entities under several regulators.
sebi.gov.in · CIR/2025/119 ↗The localization clause is in abeyance. As written, it let security data go to SaaS tools outside India on conditions. A SIEM you run in your own environment keeps the logs out of that path.
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 is yours to set. Keep the last six months on fast disk and tier older data to your own object storage, where it stays searchable. Storage and retention
Detections run as events arrive and raise alerts; related alerts group into cases that hold the evidence and timeline.
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.
The Cybersecurity and Cyber Resilience Framework, issued by the Securities and Exchange Board of India on 20 August 2024 in circular SEBI/HO/ITD-1/ITD_CSC_EXT/P/CIR/2024/113. It sets cybersecurity standards and guidelines for SEBI-regulated entities, including a Security Operations Center and log retention for user access to critical systems.
Yes. The CSCRF says it "has mandated SOC for all REs (except client-based stock brokers having less than 100 clients)". Entities can use their own or group SOC, the Market SOC implemented by NSE and BSE, or a third-party managed SOC. Small-size and self-certification REs are onboarded to the Market SOC.
Records of user access to critical systems are kept for at least two years, with at least 6 months in online mode and the rest in archival mode (PR.AA guideline (e)). For other logs, the CSCRF points to government guidelines such as the IT Act, the DPDP Act and the CERT-In Directions, which ask for 180 days of logs from all ICT systems.
Not at present. The CSCRF's data localization clause (PR.DS.S2) has been in abeyance since SEBI's circular CIR/2024/184 of 31 December 2024, as CIR/2025/119 confirms. Even as written, the clause exempted IT and cybersecurity data sent to a global SOC or to SaaS cybersecurity tools, on conditions.
As written in PR.DS.S2, IT and cybersecurity data sent to SaaS cybersecurity solutions or a global SOC outside India is classified, assessed and reviewed at least once a year by the IT Committee for REs, approved by the Board, Partners or Proprietor annually, and made available to SEBI, CERT-In or another government agency within a reasonable time not exceeding 48 hours from a request. With a SIEM you run yourself, the logs never go to such a tool.
For SEBI-regulated entities that are also regulated by another regulator, such as banks acting as custodians or depository participants, SEBI's August 2025 clarifications limit the CSCRF to systems, applications, infrastructure and processes used exclusively for SEBI-regulated activities. Shared infrastructure can still fall within SEBI's audit or inspection scope if the primary regulator's framework does not cover it.
Yes, for an own or group SOC. nano is software you run in your own environment: it collects logs from the sources you choose, runs detections, raises alerts and groups them into cases. It is not a SOC service; your team or provider operates it.
No. SEBI does not approve SIEM software, and nano, LLC holds no SEBI approval, empanelment or certification. It is the SIEM you run to collect, keep and search the logs it asks 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.