A dashboard and AI pipeline that ingests one-way IP traffic data to detect and display cybersecurity threats in real time without sending data back.
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.
Read-Only Traffic Ingest
A module that reads incoming passive traffic feeds or flow records without attempting to send responses or probes.
Feature Extraction Pipeline
A component that processes packet captures and flow metadata to extract timing, entropy, and cryptographic fingerprints.
AI Threat Detection Models
Machine learning models that classify threats like DDoS, botnet beacons, and data exfiltration from metadata alone.
Streaming Alert Engine
An inference engine that processes traffic incrementally and generates structured alert records with bounded latency.
Visualization Dashboard
A user interface that displays live or replayed detections with severity levels, confidence scores, and supporting evidence.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The jury will check that your system operates strictly read-only with no return path, processes traffic via streaming rather than batch, and evaluates encrypted sessions using metadata without decryption. They will also verify your stated throughput performance and structured alert schema.
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 traffic datasets or PCAP files to train and test the models?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
The exact minimum throughput target required to pass evaluation?
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 read-only traffic ingest. How would you build that?
Decoded from SIH26145 itself — A module that reads incoming passive traffic feeds or flow records without attempting to send responses or probes. The brief asks for it by name.
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 feature extraction pipeline. How would you build that?
Decoded from SIH26145 itself — A component that processes packet captures and flow metadata to extract timing, entropy, and cryptographic fingerprints. The brief asks for it by name.
The brief asks for ai threat detection models. How would you build that?
Decoded from SIH26145 itself — Machine learning models that classify threats like DDoS, botnet beacons, and data exfiltration from metadata alone. The brief asks for it by name.
The brief asks for streaming alert engine. How would you build that?
Decoded from SIH26145 itself — An inference engine that processes traffic incrementally and generates structured alert records with bounded latency. The brief asks for it by name.
The brief asks for visualization dashboard. How would you build that?
Decoded from SIH26145 itself — A user interface that displays live or replayed detections with severity levels, confidence scores, and supporting evidence. The brief asks for it by name.
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 that your system operates strictly read-only with no return path, processes traffic via streaming rather than batch, and evaluates encrypted sessions using metadata without decryption.
This is the evaluator read for your problem statement, decoded from the brief's own wording.
Show me this working: they will also verify your stated throughput performance and structured alert schema.
This is the evaluator read for your problem statement, decoded from the brief's own wording.