Skip to content
VITI Security

CERT-In Log Retention: What to Keep, Where, and How to Prove It (180-Day Rule)

by VITI Security TeamNov 19, 2026

CERT-In's log retention directive mandates 180 days of critical system logs. This isn't just about storage; it's about defensibility during an incident and proving compliance.

CERT-In Log Retention: What to Keep, Where, and How to Prove It (180-Day Rule) - VITI Security

CERT-In's Directions under sub-section (6) of section 70B of the Information Technology Act, 2000, specifically mandate that all service providers, intermediaries, data centres, and government organisations retain logs of all their ICT systems for a rolling period of 180 days. This isn't merely a storage requirement; it's a critical control for effective incident response and a non-negotiable compliance burden. You need to know not just what to keep, but where to put it, how to protect it, and critically, how to prove its integrity when CERT-In or an auditor comes calling.

Mandatory Logs: The Absolute Minimum You Must Keep

The directive is broad, covering "all ICT systems." This means you can't pick and choose. You need a comprehensive logging strategy. Here's a breakdown of the log types CERT-In expects to see:

Beyond the general categories, remember that specific services will generate critical logs. Think about your SaaS applications, cloud infrastructure activity (AWS CloudTrail, Azure Monitor logs), DNS query logs, and database audit trails. If it processes data or provides a service, it generates logs you likely need to retain. Don't assume anything is exempt unless you have explicit written guidance.

A common failure mode here is collecting system logs but neglecting application-level logs. If your custom application handles sensitive data, its access logs, error logs, and transactional logs are just as critical as your firewall logs. Prioritize logs that can reconstruct an attack chain or unauthorized access.

  • Firewall and IDS/IPS logs: Connection attempts, rejected traffic, security alerts, rule modifications.
  • VPN and Remote Access logs: User logins, logout times, source IP addresses, tunnel initiation/termination.
  • Operating System (OS) logs: System events, security logs (login/logout, failed attempts, privilege escalation), process execution, service start/stop, kernel messages.
  • Web Server logs: Access logs (IP, user agent, requested URL, response codes), error logs, security events.
  • Database logs: Login attempts, query logs (especially for administrative actions), schema changes, data modification events.
  • Mail Server logs: Sender, recipient, subject, attachment names, delivery status, authentication events.
  • Network Device logs: Router and switch configuration changes, authentication failures, port status changes, high-bandwidth alerts.
  • Authentication and Authorization logs: Success/failure for user logins (AD/LDAP, SSO), privilege changes, account creation/deletion.
  • Anti-malware/EDR logs: Detection events, quarantine actions, scan results, policy changes.
  • Cloud Service Provider logs: Management plane actions, resource creation/deletion, API calls, access logs for storage buckets.

Secure Log Storage: Where to Put Your Digital Evidence

Simply retaining logs isn't enough; you need to store them securely and in a way that allows for rapid retrieval and forensic analysis. There are two primary architectural patterns:

Regardless of whether you go on-prem or cloud, always adhere to the principle of least privilege for access to log data. Segregate log storage from your production environment. Implement strong encryption at rest and in transit. Your log storage solution itself is a high-value target for attackers looking to cover their tracks. Don't skimp on its security.

For many SMBs in India, a hybrid approach makes the most sense. Keep immediate, high-volume logs locally for quick analysis and forward long-term archives to a secure cloud storage solution. This balances cost, performance, and compliance needs.

  • Centralized Log Management (CLM) / Security Information and Event Management (SIEM) System: This is the gold standard. A SIEM aggregates logs from all your systems into a single, searchable repository. This is critical for correlation, alerting, and incident response. Solutions like Splunk, Elastic Stack (ELK/ECK), Azure Sentinel, or Sumo Logic fit this bill. On-prem SIEMs require significant infrastructure, while cloud-native SIEMs offer scalability and managed services.
  • Cloud Storage Solutions: Services like AWS S3, Azure Blob Storage, or Google Cloud Storage are excellent for cost-effective, durable, and scalable log archiving. You'll need mechanisms to push logs to these platforms (e.g., using agents, API integrations, or log forwarders) and proper access controls (IAM policies, bucket policies). Ensure your chosen region complies with any data residency requirements beyond CERT-In, such as those from the DPDP Act.

Proving Compliance: How to Demonstrate Integrity and Availability

It's not enough to say you have the logs; you need to prove it. This involves three key pillars:

During an actual incident, proving you have the logs and can access them quickly is paramount. You can't afford to be fumbling with storage configurations when the CERT-In 6-hour reporting clock is ticking. Robust incident response services depend on timely log access and analysis. This is where a 24x7 SOC and an established vCISO service can make a real difference, providing the expertise and continuous monitoring to ensure your log infrastructure is always ready.

  • Integrity Verification: How do you ensure logs haven't been tampered with? Implement cryptographic hashing (e.g., SHA256) on logs as they're ingested and stored. Some SIEMs offer built-in tamper detection. Regular integrity checks are vital. Ensure proper write-once, read-many (WORM) storage where possible, or immutable storage buckets in the cloud.
  • Audit Trails and Access Controls: Maintain a clear audit trail of who accessed the logs, when, and for what purpose. Implement strong role-based access control (RBAC) to ensure only authorized personnel can view or manage log data. This is often overlooked but critical for the security of your evidence.
  • Documentation and Testing: Document your entire log retention strategy: what logs you collect, from where, how they're transported, stored, protected, and how long they're kept. Regularly test your log collection, storage, and retrieval processes. Can you pull a specific log from 100 days ago within minutes? If not, your system needs work. This testing should be part of your regular VAPT and compliance audits.

Operational Considerations and Common Pitfalls

Implementing a 180-day log retention strategy comes with practical challenges. Here's what to watch out for:

Ultimately, robust log management isn't just about compliance; it's fundamental to your organization's security posture. It enables threat detection, speeds up incident response, and provides the forensic evidence needed to understand and recover from attacks. Don't treat it as a checkbox exercise. Treat it as a critical component of your cybersecurity strategy.

  • Storage Costs: Logs generate massive volumes of data. Factor in the cost of storage (especially for hot storage if you need rapid access) and egress fees if using cloud solutions. Optimize by filtering unnecessary logs at the source and compressing data.
  • Data Privacy: Logs often contain sensitive information (IP addresses, usernames, potentially even PII). Ensure your log retention practices comply with the Digital Personal Data Protection Act (DPDP Act), 2023, and other relevant privacy regulations. Anonymize or redact sensitive data where possible before long-term storage.
  • Performance Impact: Log collection agents can consume system resources. Design your logging infrastructure to minimize impact on critical systems. Batching and efficient transport protocols are key.
  • Alert Fatigue: A SIEM that collects everything but doesn't have well-tuned correlation rules will overwhelm your security team. Focus on high-fidelity alerts that indicate actual threats. This is where expert managed security services can help.
  • Skill Gap: Managing a comprehensive logging and SIEM solution requires specialized skills. Many SMBs struggle to hire and retain security analysts with this expertise. Consider managed security services or a 24x7 SOC to bridge this gap.

Frequently asked questions

What specific log types does CERT-In require to be retained for 180 days?

CERT-In requires logs from "all ICT systems," which broadly includes firewall, IDS/IPS, VPN, OS (Windows Event Logs, Linux syslog), web server, database, mail server, network device, authentication, anti-malware, and cloud service provider logs. The key is to capture events that would allow reconstruction of an attack or unauthorized activity.

Can I store my CERT-In mandated logs in the cloud?

Yes, you can store your logs in the cloud. Cloud storage solutions like AWS S3 or Azure Blob Storage offer scalable and cost-effective options. However, you must ensure data sovereignty requirements (if any, beyond CERT-In) are met, implement strong encryption, and maintain robust access controls. Your cloud log storage must be as secure, if not more, than on-premises solutions.

How do I prove the integrity of my logs during a CERT-In audit or incident investigation?

Proving log integrity requires a combination of technical controls and documentation. Implement cryptographic hashing on logs at ingestion, use write-once, read-many (WORM) storage or immutable cloud buckets, and maintain clear audit trails of log access. Regularly test your log retrieval process and document your entire log management strategy.

What happens if I fail to comply with CERT-In's 180-day log retention rule?

Non-compliance with CERT-In directions can lead to penalties under the Information Technology Act, 2000. Beyond monetary fines, a lack of historical logs severely hampers your ability to respond to and recover from a cybersecurity incident, potentially leading to greater financial loss, reputational damage, and legal liabilities.

Is a SIEM system mandatory for CERT-In log retention?

While CERT-In doesn't explicitly mandate a SIEM system, it's the most effective and often necessary tool for achieving compliance with the spirit of the directive. A SIEM centralizes log collection, provides correlation capabilities, enables rapid searching, and supports incident response, making it significantly easier to meet the 180-day retention and retrieval requirements effectively.

Do I need to retain logs for SaaS applications I use?

Yes, if your SaaS applications are considered 'ICT systems' that process or store data relevant to your operations and security, you should retain their logs. This often includes user activity, administration changes, access logs, and security events. Many SaaS providers offer API access or integrations to export these logs to your centralized SIEM or cloud storage.

Stop Worrying About CERT-In Log Retention - Get 24/7 Managed Security

Maintaining a CERT-In compliant log management infrastructure is a complex, continuous effort. VITI Security's 24x7 SOC takes this burden off your shoulders, ensuring your logs are collected, secured, and ready for incident response or audit, around the clock. Focus on your core business; we'll handle the compliance and security.