> OSINT INVESTIGATION PLAYBOOKS_
Step-by-step investigation SOPs for cybercrime investigators, corporate security teams, and defence analysts. Each playbook covers tools, methodology, evidence collection, and legal compliance specific to India.
Why Investigation Playbooks Matter
A playbook is a standard operating procedure for a specific type of investigation — a documented, repeatable sequence of steps from first report to final reporting. Under the pressure of a live case, structured procedure is what prevents missed evidence, broken chains of custody, and inconsistent outcomes between analysts. The discipline a playbook imposes is also what makes a conclusion defensible when it is later examined by a senior officer, a court, or opposing counsel.
How to use the playbooks on this page
Follow the sequence rather than improvising, and document each step as you complete it — what you did, when, and what you found. Adapt the procedure to the facts of your case, but record any deviation and the reason for it. The goal is an investigation that another competent analyst could reproduce from your notes and arrive at the same result.
Anchored in Indian law and procedure
Each playbook is written for the Indian legal environment. Where evidence must be obtained from an intermediary or service provider, production is sought under Section 94 of the Bharatiya Nagarik Suraksha Sanhita, 2023. Electronic evidence is accompanied by a certificate under Section 63 of the Bharatiya Sakshya Adhiniyam, 2023. Substantive offences are framed under the Bharatiya Nyaya Sanhita, 2023 and the Information Technology Act, 2000. Building these references into the procedure itself keeps the investigation aligned with what a prosecution will ultimately require.
How to adapt a playbook to your case
No two investigations are identical. Treat each playbook as a checklist of the questions a court, an auditor or a senior officer will ask later, and record why any step was skipped. The structure that holds up best follows the same sequence every time: secure the report, preserve volatile evidence, identify the infrastructure and the money trail, request records through the proper legal channel, analyse, and document.
Evidence handling that applies to every playbook
- Preserve before you analyse: capture pages, messages and files with time, date and URL visible, and hash every file at collection.
- Keep a contemporaneous log of who did what, when, and with which tool or account.
- Request platform and bank data through notices under Section 94 of the BNSS, 2023 rather than informal channels.
- Prepare a certificate under Section 63 of the Bharatiya Sakshya Adhiniyam, 2023 for every electronic record you intend to rely on.
- Report specified cyber security incidents to CERT-In within six hours where the April 2022 directions apply.
Choosing the right playbook
Financial frauds (UPI, investment, loan-app, digital arrest) start with speed: report on 1930 and freeze funds before anything else. Account takeovers and SIM swaps start with the telecom and platform trail. Ransomware and data breaches start with containment and log preservation. When a case spans several types — for example a phishing link that leads to a UPI fraud — run the playbooks in the order the money and the evidence are most likely to disappear.
Related: Indian cyber law reference · UPI fraud guide · SIM swap investigation
Frequently asked questions
Are these playbooks legal advice?
No. They are operational guides based on Indian law and common practice. Follow your organisation's policies and seek legal advice for case-specific questions.
Can corporate teams use them?
Yes. Corporate security and fraud teams can use the same evidence and reporting steps; requests for records from platforms and banks are made through law enforcement or the courts.
How often are the playbooks updated?
They are reviewed when laws, portals or common fraud patterns change — for example after the move from IPC, CrPC and the Evidence Act to the BNS, BNSS and BSA in 2024.