A programming language framework called JOCKY that generates scripts for forensic analysis without triggering antivirus tools, featuring a central management interface.
National Technical Research Organisation (NTRO) · Software
Signing in saves it for your whole team, so 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.
Custom Compiler Framework
Build a cross-platform compiler supporting Windows and Ubuntu that alters basic control flow graphs and token generation.
Polymorphic Script Engine
Implement automated obfuscation, variable encryption, and polymorphic engines to ensure unique hashes on every deployment.
In-Memory Execution
Create file-less execution techniques like process hollowing and reflective DLL injection to run scripts within trusted processes.
Kernel-Level Subversion
Incorporate support for Bring Your Own Vulnerable Driver techniques to disable security agent callbacks.
Central Management Interface
Develop a management dashboard that handles multiple system analyses simultaneously with traffic routed through trusted cloud infrastructure.
Both columns are read off the brief's own wording. Nothing here is inferred from the ministry's name.
The evaluators will test whether the created language framework and its generated scripts can actually bypass existing antivirus and EDR solutions, operate via in-memory execution or BYOVD techniques, and communicate via a central management interface without detection.
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 syntax requirements for the JOCKY programming language?
The brief never answers this, so a panel will. Whatever you decide, say it the same way twice.
Exact cloud infrastructure or CDN APIs to be used for routing?
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 custom compiler framework. How would you build that?
Decoded from SIH26148 itself: Build a cross-platform compiler supporting Windows and Ubuntu that alters basic control flow graphs and token generation. The brief asks for it by name.
The brief asks for polymorphic script engine. How would you build that?
Decoded from SIH26148 itself: Implement automated obfuscation, variable encryption, and polymorphic engines to ensure unique hashes on every deployment. The brief asks for it by name.
The brief asks for in-memory execution. How would you build that?
Decoded from SIH26148 itself: Create file-less execution techniques like process hollowing and reflective DLL injection to run scripts within trusted processes. The brief asks for it by name.
The brief asks for kernel-level subversion. How would you build that?
Decoded from SIH26148 itself: Incorporate support for Bring Your Own Vulnerable Driver techniques to disable security agent callbacks. The brief asks for it by name.
The brief asks for central management interface. How would you build that?
Decoded from SIH26148 itself: Develop a management dashboard that handles multiple system analyses simultaneously with traffic routed through trusted cloud infrastructure. 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 evaluators will test whether the created language framework and its generated scripts can actually bypass existing antivirus and EDR solutions, operate via in-memory execution or BYOVD techniques, and communicate via a central management interface without detection.
This is the evaluator read for your problem statement, decoded from the brief's own wording.
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 building complex kernel-level subversion and BYOVD techniques that interact with proprietary security solutions and drivers.
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.