The Invoice Was Never the Problem - What's Actually Inside India's Military Drones

Checking the Invoice Was Never the

Same as Checking the Silicon Here's what's actually happening with AASHVAST: for years, the Army's check on a drone's origin was essentially a paperwork check - the invoice said where a component was purchased from and that was treated as proof of where it came from.

The problem is that an invoice tells you where money changed hands, not what code is actually sitting inside the chip. A component bought through a third country or relabelled along the way, could still carry firmware written somewhere else entirely - and there was no mechanism to check.

The Mechanism That Actually Changed

AASHVAST closes that exact gap by testing the firmware itself rather than the paperwork trail. Firmware is the low-level code baked into a hardware component that controls what it actually does - and vulnerabilities can be planted there during manufacturing or an upgrade, as hidden commands that trigger only under specific conditions.

The labs are built to catch roughly 14 categories of these: geospatial faults that make a drone malfunction over a certain location, hidden or unused code that can terminate a mission early and time-or-location bugs that let a component behave normally until a specific trigger condition is met.

None of this is visible by opening the drone and looking at it - it only shows up when the firmware is actually run through validation.

Why "Made in India" on an Invoice Isn't Enough This is the

sharper point buried in the story: a component can be procured with paperwork showing an Indian or third-country origin while the actual silicon inside was designed or manufactured elsewhere, because the invoice only reflects the point of purchase, not the true supply chain.

That is precisely why the Army has, in the past, banned Chinese-made parts outright rather than trying to vet them - outright bans were the only enforceable check available before a tool like AASHVAST existed. Now, firmware validation gives the Army a way to catch what a ban-by-origin-label approach would miss: components that were never declared as Chinese-origin in the first place.

The limit here is worth being honest about: firmware testing catches what the suite is built to look for - roughly 14 known categories of vulnerability. It is not a guarantee against every conceivable hidden threat and it depends on the testing suite itself being kept current as adversaries adapt.

For the exam, the real shift isn't "India worries about Chinese components"

• that's old news. It's that Indian defence procurement has moved from trusting where something was bought to actively verifying what it does, treating hardware the same way cybersecurity teams have long treated software: as something that must be tested, not assumed trustworthy.