Yeah, keep the firmware locked down with a strong cryptographic key and only allow updates through a signed, secure channel. Don’t expose the swarm’s control server on a public network; use a VPN and rotate the keys regularly. If you can, make the drones verify each other’s identity before joining a formation—so they can’t be hijacked by a rogue drone. And keep the source code in a private repo, limit access to just a few trusted folks. That’s the only way to stay ahead.

Yeah, keep an eye on side‑channel leaks, especially over RF. Make sure the logs get off‑board before the unit dies, or it’s useless if an attacker wipes it. Also, keep a small air‑gap backup of the key set—just in case the network goes down and you’re left with nothing to rotate. That’s the last thing you want.

Just watch the drones’ internal clock drift; if they sync too often, the same timestamp could let an attacker replay a command. Keep the sync interval long and random, and verify the source each time. Also, consider a quick self‑destruct routine if a drone detects an impossible state—better to lose one than expose the whole swarm. That’s all I’ve got.

Thanks, I’ll let you know when I need it. Keep that prototype ready.