A software forensic platform that lets law enforcement investigators acquire, recover, and analyze surveillance footage from multiple vendor DVR and NVR devices.
National Technical Research Organisation (NTRO) · Software
Signing in saves it for your whole team — everyone on your invite link sees the same two entries. Anything you shortlisted while signed out comes with you.
Decomposed from what the description asks for. Nothing added.
Device Identification Module
Automatically identifies DVR and NVR models from major OEMs.
Acquisition and Parsing
Creates forensic images and parses proprietary file systems and video formats.
Recovery and Validation
Recovers deleted footage and generates MD5 and SHA-256 cryptographic hashes for evidence integrity.
Timeline and Analytics
Normalizes timestamps, correlates events across cameras, and runs AI-based object, face, and motion detection.
Reporting Module
Maintains chain of custody records and generates standardized forensic reports.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will check whether your platform supports at least five to six specified OEMs like Dahua, CP Plus, and Hikvision, parses proprietary file systems, recovers deleted recordings, and ensures evidence integrity using MD5 and SHA-256 hashes.
A jury can still ask about these. Decide them deliberately rather than by accident.
Generated from the brief's own wording and the competition's published rules — never from a guess about what this ministry prefers.
Specific sample forensic dump files from each named manufacturer?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Exact legal standards or court admissibility requirements for the target jurisdiction?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Has any part of this been shown at a previous event, hackathon or college project?
The guidelines are explicit: your solution must not have appeared in any previous event or programme, of any sort. A recycled project is what a team under time pressure reaches for.
The brief asks for device identification module. How would you build that?
Decoded from SIH26150 itself — Automatically identifies DVR and NVR models from major OEMs. The brief asks for it by name.
Each one is quoted from a gap in the brief, not a guess about your team.
Needs data you may not get
The description requires parsing proprietary storage formats and file systems from major manufacturers like Dahua, Hikvision, and Honeywell which students cannot easily obtain.
What the organisers attached, and what the brief assumes you can get.
Same organisation, same year. Reading two of theirs tells you more about what they care about than reading one.
Pick what you are about to do and copy the prompt. It carries the organisers' own wording, the constraints they never spell out, and an instruction not to invent requirements they never set.
Who has this problem, what already exists, and what you would have to find out.
The brief asks for acquisition and parsing. How would you build that?
Decoded from SIH26150 itself — Creates forensic images and parses proprietary file systems and video formats. The brief asks for it by name.
The brief asks for recovery and validation. How would you build that?
Decoded from SIH26150 itself — Recovers deleted footage and generates MD5 and SHA-256 cryptographic hashes for evidence integrity. The brief asks for it by name.
The brief asks for timeline and analytics. How would you build that?
Decoded from SIH26150 itself — Normalizes timestamps, correlates events across cameras, and runs AI-based object, face, and motion detection. The brief asks for it by name.
The brief asks for reporting module. How would you build that?
Decoded from SIH26150 itself — Maintains chain of custody records and generates standardized forensic reports. The brief asks for it by name.
Where does your data come from — a published source, one you collect, or one you generate?
No dataset is attached to this problem statement, so sourcing it is part of the work and nobody told you that.
Why not use what already exists? Name the closest thing to this that is already running.
A team that has not named the alternative themselves is answering this for the first time in the room.
Which single thing will you demonstrate end to end, start to finish, with nothing skipped?
Ours, not a rule: a narrow thing that fully works survives questioning better than a broad thing that half works. If nobody on the team can name it, that is the finding.
Show me this working: the jury will check whether your platform supports at least five to six specified OEMs like Dahua, CP Plus, and Hikvision, parses proprietary file systems, recovers deleted recordings, and ensures evidence integrity using MD5 and SHA-256 hashes.
This is the evaluator read for your problem statement, decoded from the brief's own wording.