SIEM Tools for Indian SOC Teams
Detection use cases, query translation, coverage analysis, and log sizing tools -- all mapped to MITRE ATT&CK and the APT groups active in India.
Use Case Library
Searchable library of detection use cases with both SPL (Splunk) and KQL (Sentinel) queries, mapped to MITRE ATT&CK and APT groups targeting India.
Browse use cases →Query Translator
Convert detection queries between SPL, KQL, and Sigma format. Useful when migrating SIEM platforms or sharing detections across teams.
Translate queries →Coverage Matrix
Visualise your SIEM detection coverage against the MITRE ATT&CK matrix. Identify gaps in detection for APT TTPs relevant to Indian organisations.
Check coverage →Log Volume Estimator
Estimate your daily EPS (events per second) and storage requirements based on endpoint count, log sources, and retention requirements.
Estimate volumes →Compliance Checker
Map your SIEM detection rules to CERT-In Directions 2022, DPDP Act 2023, and ISO 27001 requirements. Identify mandatory log retention gaps.
Check compliance →Sigma Rule Viewer
Browse community Sigma detection rules, convert them to your SIEM's native query language, and filter by APT group or MITRE technique.
Browse Sigma rules →What a SIEM does — and why detection engineering matters more than the platform.
A Security Information and Event Management (SIEM) system collects, normalises, and correlates log data from across an organisation's technology environment — endpoints, servers, firewalls, cloud services, applications — and applies detection rules to identify patterns that indicate security threats. Every mature SOC operates a SIEM as its core detection platform. In India, SIEM logging is not just a best practice: CERT-In Directions 2022 mandate that all ICT system logs be retained for a minimum of 180 days within India, and that logs from covered incident types be available for immediate inspection upon request.
The most common failure in Indian SIEM deployments is not the platform selection — it is the absence of detection engineering. A SIEM without tuned detection rules is an expensive log repository. The tools on this page are built to address that gap: a library of 50+ pre-built detection use cases with queries in both Splunk SPL and Microsoft Sentinel KQL, a translator for converting queries between platforms, a coverage matrix to identify which MITRE ATT&CK techniques have no detection, and a compliance checker to verify that mandatory detection categories under CERT-In and ISO 27001 are covered.
For Indian organisations, SIEM detection priorities are shaped by the specific APT groups that actively target this geography. Sidewinder (targeting Indian government and military), APT36 (targeting Indian defence personnel), and Lazarus Group (targeting Indian financial institutions and cryptocurrency exchanges) all use techniques that generic global threat feeds underweight relative to their actual frequency in Indian environments. The use case library on this platform includes specific detections for these actors alongside standard MITRE ATT&CK coverage.
Frequently asked questions — SIEM
What is the difference between Splunk SPL and Microsoft Sentinel KQL?
SPL (Search Processing Language) is Splunk's proprietary query language — pipe-based, flexible, and widely used in enterprise SOCs. KQL (Kusto Query Language) is Microsoft's query language used in Azure Sentinel (now Microsoft Sentinel) and other Microsoft products. Both query the same types of data but with different syntax. The Query Translator tool converts between them so detections written for one platform can be reused in the other.
What is a Sigma rule and why should SOC teams use them?
Sigma is a generic, vendor-neutral detection rule format. A Sigma rule describes a detection in YAML format that can be converted to any SIEM's native query language — SPL for Splunk, KQL for Sentinel, AQL for QRadar, EQL for Elastic. Writing detections in Sigma means you are not locked to any single platform. The Sigma rule viewer on this page lets you browse community rules and convert them to your SIEM's format instantly.
How many events per second (EPS) should I plan for?
EPS depends on the number of endpoints, servers, network devices, and log sources being collected. A rough baseline for a 500-endpoint Indian enterprise with standard log sources (Windows events, firewall, proxy) is 500–1,500 EPS. The Log Volume Estimator on this platform calculates your expected EPS and storage requirements based on your specific environment inputs.
What SIEM log sources are mandatory under CERT-In Directions 2022?
CERT-In Directions 2022 require logs from ICT systems to be retained for 180 days within India, with system clocks synchronised to NIC or NPTI NTP servers. The directions require that organisations be able to produce logs upon request covering the 20 notifiable incident types, which include data breaches, ransomware, phishing, and network intrusions. The SIEM Compliance Checker maps your current log sources to these requirements and identifies gaps.