We did all that, the test Zach glitched but Inca allowed Wagner to help rectify.
What we're doing now has got nothing to do with the maglock (or the maglock rules), but with hacking into the system.
And I have to admit that something like what Inca is describing here is described in Unwired. Putting a system behind a system behind a system. Only way to get to the last is to first break through the first ones.
What might be possible is that Unwired meant that, instead of every device being one of those required steps, they're divided into larger subsystems than one single lock. (The pdf example doesn't even have those but only has one large "security" node)
Like for example, the maglocks run on their own system, the turrets run on their own system and both are running in the security system.
This would mean that hacking a secure account into the maglock sub-system is enough to control all locks -not just the one Wagner's hooked to. But getting to the turret system from the lock would mean first hacking the maglock system, then from there hacking the central-security system and only from there can the turret system be hacked.
Bleh, will find out after a matrix perception check. IP2 here? (I think Brick said he was delaying to shoot down whoever bust through the door, but TI might have changed his mind...)
@Inca: Wagner's shout over comms: Was just a free action speech thing. Not a simple action Issue Command; but since you sometimes seem to allow drone pilots a level of intelligence (they are attack combat drones after all) I figured it was worth a shot. I'll leave you to decide their action (or inaction) and rolls since it's their dog-brain deciding their actions, not Wagner.