{"id":2690,"date":"2026-11-13T06:00:17","date_gmt":"2026-11-13T06:00:17","guid":{"rendered":"https:\/\/www.newevol.io\/resources\/?p=2690"},"modified":"2026-11-13T06:00:28","modified_gmt":"2026-11-13T06:00:28","slug":"siem-cert-in-compliance","status":"publish","type":"post","link":"https:\/\/www.newevol.io\/resources\/blog\/siem-cert-in-compliance\/","title":{"rendered":"SIEM for CERT-In Compliance: Log Retention, Time Sync and 6-Hour Reporting"},"content":{"rendered":"

CERT-In’s Cyber Security Directions of 28 April 2022 ask organizations in India to do three things that security teams feel every day: keep ICT system logs for a rolling 180 days, synchronize system clocks with approved time sources, and report specified cybersecurity incidents within six hours of noticing them.<\/p>\n

Each requirement sounds simple on paper. In practice, all three depend on whether logs from firewalls, servers, endpoints and cloud workloads land in one place, whether their timestamps agree, and whether an alert reaches the right person fast enough to start a report.<\/p>\n

This is where Security Information and Event Management (SIEM)<\/a> <\/strong>earns its place. A SIEM collects and correlates security events across systems, giving teams the visibility, timelines and evidence these directions call for. This guide walks through each requirement, explains what SIEM can and cannot do for it, and ends with a readiness checklist your team can work through.<\/p>\n

\n
\n

Table of Contents<\/p>\nToggle<\/span><\/path><\/svg><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n