Ravindra BagaleCourses & study guides मराठी Track your progress

28. Introduction to Digital Forensics

28.6 Forensics, Incident Response and the Law

By Last updated:

Forensics ekta chalat nahi – to incident response cha bhag aahe (Part 11 madhe purna baghu). Breach zalyavar order asa:

  1. Detect the incident (SOC, alerts – Part 11).
  2. Contain it (isolate the affected machine).
  3. Preserve evidence – image disks, capture memory, save logs (this chapter).
  4. Analyse – what happened, how, what was taken.
  5. Report and recover – fix, restore, and improve.

A note on Indian law: digital evidence is admissible under the Indian Evidence Act with a proper Section 65B certificate for electronic records (verify the current provisions yourself). CERT-In requires certain incidents to be reported. This is why chain of custody and integrity hashing matter so much – without them, good evidence can be thrown out.

Why this matters for security

After an attack, forensics answers the questions that stop the next one: how did they get in, what did they touch, and is it fully cleaned up? Done properly, it also turns an incident into evidence that can support legal action.

Ravindra Bagale's Tip

Interviewers ask, "There's been a breach – what will you do first?" The answer: not panic and delete or reboot everything! First, containment and preserving evidence (image + memory + logs). If you reboot, the evidence in RAM is lost for good. Follow the process with a calm mind.

Practice task

Write the six incident-response steps in order and mark which one this chapter covered. In one line, explain why rebooting a compromised machine immediately can destroy evidence.

Extended teaching notes

Why this lesson matters

A SOC turns logs into action. Good juniors triage with playbooks: what fired, which asset, how bad, contain or escalate, write the timeline.

  1. Prepare: asset list, contacts, runbooks.
  2. Detect: SIEM/EDR alerts with context.
  3. Contain: disable account, isolate host, block IOC.
  4. Eradicate & recover: patch, rebuild, restore.
  5. Lessons: one improvement ticket per incident.

Indian company (sample)

A 24×7 SOC at a large Indian IT services firm handles phishing and malware for many clients. Tier-1 analysts follow a script; they do not freestyle on production.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.