3121

DFIR Services in India: What to Do After a Cyberattack

Last updated: November 12, 2026

Last updated: November 12, 2026

A cyber incident is not the time to wipe a machine and start afresh. When you suspect a cyber incident, your first response must focus on preserving evidence, limiting further damage, and bringing the right people into the investigation. Digital Forensics and Incident Response (DFIR) helps organizations investigate security incidents, establish their scope, contain threats, and support recovery. Knowing what to do in the first hour helps protect business operations while retaining evidence for legal proceedings, regulatory reporting, and cyber insurance claims.

Mitigata is an IRDAI-licensed, AI-native cyber resilience company serving more than 800 businesses across cybersecurity, compliance, cyber insurance and incident response. This guide covers what to do in the first hour of an incident and what a DFIR engagement involves.

What Is DFIR?

Digital Forensics and Incident Response (DFIR) is a blend of two interconnected activities – digital investigation and the management of security incidents. Together, they establish how an incident occurred, its entry point, and its impact, while supporting threat containment, limiting business disruption, and enabling recovery.

How Mitigata Helps Businesses Respond to Cyber Incidents

When a cyber incident strikes, rapid containment and evidence preservation are critical. Mitigata combines digital forensics, incident response expertise, and cyber risk management to help businesses investigate threats, limit damage, and recover effectively.

Here’s what sets Mitigata’s DFIR services apart:

  • Rapid Incident Response: A 60-minute war-room-to-containment benchmark to help limit business disruption.
  • Expert-Led Forensics: Investigate attack origins, compromised systems, and potential data exposure.
  • Evidence Preservation: Support forensic evidence collection and chain-of-custody documentation.
  • Regulatory and Insurance Support: Assist with incident documentation for CERT-In reporting and cyber insurance claims.

From Cyber Crisis to Containment, Faster.

Mitigata’s 60-minute war-room-to-containment benchmark combines rapid response with forensic expertise to help limit damage.

When To Call A DFIR Team

A business should contact a DFIR team as soon as it suspects a significant cyber incident. Waiting for complete confirmation may give an attacker more time to access systems, move across the network, or extract sensitive information.

Some incidents require specialist investigation beyond the capabilities of an internal IT or security team. Common indicators include:

Ransomware Or Suspected Data Theft

Encrypted files, ransom demands, unexpected changes to business systems, and unusual outbound data transfers indicate a need for investigation. Ransomware activity does not necessarily represent the full extent of an incident. Attackers may steal information before encrypting systems, creating additional legal, regulatory, and business risks.

Unauthorized Access And Account Compromise

Unrecognized administrator activity, suspicious login patterns, compromised credentials, and unauthorized access to business applications require investigation. Attackers may use legitimate credentials to access systems, making it important to examine authentication records, active sessions, and account activity.

Suspicious System Activity Or Malware

Unexpected processes, unexplained system changes, malware detections, and signs of persistent access within the network warrant further examination. These indicators may point to unauthorized activity that remains active even after an initial threat has been detected.

Legal, Regulatory And Insurance Implications

The team requires a clear understanding of the incident’s scope and impact if the suspected breach involves customer information, financial records, or other sensitive data. Forensic findings support legal proceedings, regulatory investigations, customer notifications, and cyber insurance claims. Organizations with an incident response retainer also have an established route to specialist support when an incident occurs.

The First Hour: Preserve Before You Clean Up

The first hour of a cyber incident is critical for evidence preservation and response coordination. Actions such as shutting down devices, deleting files, or redeploying workloads may destroy information needed for forensic investigation.

Organizations should prioritize the following five actions.

Step 1. Isolate Affected Systems And Compromised Accounts

Isolate affected devices from the network to limit lateral movement and prevent further communication with attacker-controlled infrastructure. Network isolation should be coordinated with the DFIR team, particularly when investigators need to collect volatile evidence before changing the system’s state.

Account compromise requires a separate containment response. Changing a password alone does not terminate existing authenticated sessions or revoke all active tokens. Revoke active sessions and refresh tokens, and review other authentication mechanisms associated with the compromised account. It also includes checking for unauthorized changes to account recovery details and registered authentication methods.

The aim: To restrict the attacker’s access across devices and identities while preserving evidence needed for investigation.

Step 2. Preserve Volatile Evidence Before Powering Off Or Wiping Devices

Do not shut down, restart, reimage, or wipe an affected device before forensic guidance. These actions may destroy volatile information stored in memory or available through live system activity.

Digital evidence collection follows the order of volatility. Investigators collect information most likely to disappear first, followed by evidence that remains available for longer.

The collection process generally prioritizes:

  • System memory and running processes.
  • Active network connections, routing information, and logged-in sessions.
  • Other volatile system information.
  • Forensic disk images and persistent system data.
  • Relevant logs and archived records.

The precise collection sequence depends on the system and the incident. Memory and live network connections require early attention because they change or disappear quickly.

Containerized environments require additional care. In Docker and Kubernetes environments, preserve relevant node and pod states, running processes, workload information, and available runtime data before redeploying workloads, scaling down services, or terminating affected containers. These actions may remove evidence needed to understand how the attacker accessed the environment.

Step 3. Preserve Logs, Mailboxes, And Cloud Evidence

Logs provide a record of activity across systems and help investigators reconstruct an incident. Preserve relevant firewall, endpoint, authentication, VPN, email, cloud, and application logs.

Email and identity systems require particular attention. Attackers who compromise an account may establish persistence through mailbox rules, forwarding settings, or unauthorized authentication methods.

Check for:

  • Suspicious mailbox forwarding rules and inbox rules.
  • Newly registered MFA devices or authentication methods.
  • Unrecognized sign-ins and changes to account permissions.
  • Unauthorized application access and suspicious OAuth grants.

Cloud and SaaS environments introduce another evidence preservation challenge. Audit logs and activity records often have service-specific retention periods. Export relevant records before those periods expire and result in permanent loss of historical information. Where retention deadlines are close, prioritize these exports alongside volatile evidence collection.

Preserve suspicious emails, available security alerts, and relevant communication records. Record the source and time of collection so investigators can correlate these records with endpoint and network evidence.

Step 4. Record The Incident Timeline And Maintain Chain Of Custody

Document the incident from the moment it is identified. Record when the issue was first noticed, who discovered it, which systems and accounts were affected, and what actions have already been taken.

Evidence handling requires a documented chain of custody from the first collection. Maintain a record that includes:

  • Who collected each piece of evidence.
  • The date and time of collection.
  • The source and method of collection.
  • Where the evidence was stored.
  • Every subsequent transfer or instance of access.

Immediately after collecting each evidence item, calculate its cryptographic hash value. Hashing produces a digital value used to verify whether evidence has changed during storage, transfer, or examination. Record the hash algorithm and resulting value alongside the acquisition details.

These records support evidence integrity and traceability. They also help establish how electronic records were collected and handled if they are later required in legal proceedings.

Step 5. Contact The DFIR Team And Establish Incident Ownership

Contact the incident response hotline and share the nature of the incident, affected systems, available evidence, and actions already taken. Avoid proceeding with further remediation without forensic guidance. The organization should appoint an incident lead and a designated decision-maker. Clear ownership helps prevent conflicting decisions during an incident. It also gives technical teams, business leadership, legal representatives, and insurers a coordinated point of contact.

Under Cyberattack? Every Minute Counts.

Get rapid incident containment, expert-led forensics, and recovery support with Mitigata’s DFIR services.

What A DFIR Engagement Looks Like: Triage, Collect, Contain, Explain

A DFIR engagement moves from the initial assessment of an incident to evidence collection, containment, and the delivery of investigation findings. Each stage contributes to understanding the incident and deciding what needs to happen next.

Triage: Understand The Incident

The DFIR team assesses available indicators, identifies affected systems, and determines the initial severity of the incident. This includes examining suspicious activity, compromised accounts, malware detections, and unusual network traffic.

An important part of triage is investigating potential data exfiltration. Attackers may use file archiving utilities, command-line tools, or cloud storage services to transfer information outside the organization. Tools such as rclone and services such as MEGA may feature in these activities. Investigators examine outbound traffic, file access patterns, archive creation, and cloud uploads to establish whether information was stolen.

Collect: Preserve And Examine Evidence

The collection stage involves acquiring and examining relevant digital evidence. Investigators calculate cryptographic hash values immediately after collecting each evidence item to support integrity verification. They also maintain acquisition records and chain-of-custody documentation to establish evidence provenance and traceability.

The investigation must also account for the legal requirements governing electronic records. Section 63 of the Bharatiya Sakshya Adhiniyam (BSA), 2023, addresses the admissibility of electronic records produced as computer output. The certificate identifies the record, describes how it was produced, provides relevant device particulars, and addresses the applicable conditions. It must carry the required signatures, including those of the person in charge of the relevant device or activities and an expert.

Hash values support evidence integrity verification. They do not establish admissibility under Section 63. Acquisition records, chain-of-custody documentation, and the applicable certificate requirements also matter.

Contain: Limit The Incident’s Impact

Containment restricts attacker access and limits further damage. Containment requires coordination. Isolated changes may alert an attacker that the organization has detected the intrusion. Investigators assess the available evidence and the risk of further attacker activity before planning containment measures across affected systems and accounts.

Mitigata states a 60-minute war-room-to-containment figure for its incident response capability. Organizations evaluating the service should understand the response milestone and the service scope associated with this figure.

Explain: Establish What Happened

The investigation establishes how the attacker gained access, what activity took place, which systems and accounts were compromised, and whether information was exposed or exfiltrated. The DFIR team consolidates these findings into an incident timeline, scope assessment, evidence records, and recommendations for remediation and recovery. These findings help leadership understand the business impact and guide subsequent technical, legal, regulatory, and insurance-related decisions.

CERT-In’s 6-Hour Reporting And The Evidence Behind It

Under CERT-In’s Cyber Security Directions, specified entities must report listed cyber incidents within six hours of noticing them or being informed of them.

The Directions also require applicable organizations to:

  • Enable ICT system logs and retain them securely for a rolling 180 days.
  • Store these logs within Indian jurisdiction and provide them to CERT-In when required.
  • Designate a Point of Contact for coordination with CERT-In.

Accurate timestamps and synchronized system clocks help correlate events across endpoints, servers, applications, and network infrastructure.

The six-hour deadline applies to incident reporting, not completion of the forensic investigation. DFIR helps establish the incident timeline, identify affected systems, and preserve evidence for further examination.

Conclusion

A cyber incident requires more than restoring affected systems and resuming business operations. Organizations need to understand how the incident occurred, what information or systems were compromised, and whether the attacker retains access. Preserving volatile evidence, maintaining chain of custody, and coordinating containment during the initial response help establish these facts. A structured DFIR investigation supports recovery, regulatory reporting, legal review, and cyber insurance claims by providing documented findings that decision-makers can rely on.

Save Mitigata’s incident response hotline, +91 80059 63112, and book a DFIR readiness call.

FAQs

Q1. When should a business hire a DFIR team?

A business should engage a DFIR team as soon as it suspects a significant cyber incident, including ransomware, unauthorized access, compromised accounts, malware infections, or data theft. Early investigation helps identify the extent of the compromise, preserve evidence, and guide containment and recovery.

Q2. Should an organization shut down an infected computer during a cyberattack?

Not without forensic guidance. Shutting down an infected computer may destroy volatile evidence stored in memory and information about active network connections or running processes. Investigators should assess the need to collect this evidence before the device is powered off. Network isolation is generally preferable when it limits attacker communication without destroying evidence.

Q3. How long does a DFIR investigation take?

There is no fixed timeline for a DFIR investigation. Initial triage and containment take place early in the engagement, while the full investigation continues until the team has established the incident’s scope, timeline, and impact. The duration depends on the complexity of the incident, the number of affected systems, evidence availability, and the extent of the compromise.

Q4. Does a DFIR report help with cyber insurance claims?

Yes. A DFIR report provides documented evidence of the incident, its timeline, scope, impact, and response measures. Insurers use this information to assess reported losses and determine whether the claim meets the policy’s coverage terms and requirements.

Pratyasha

Leave a Reply

Your email address will not be published. Required fields are marked *