Right now it is possible, and even easy, for a decker to secure a node they are working on so well that they just can't get back in. It seems a bit odd since they WROTE the security in the first place and I think it is unlikely that they would unintentionally do so in a way that locks themselves out.
With tat in mind, I'd like to propose a command that, when toggled on, limits how well the decker will secure a node. maybe call it @backdoor or something. The idea is that when a decker secures a node with this option enabled they will be unable to place a security level on a node than is higher than what their stats/skills will allow them to crack.
If a decker just doesn't care if they can access that node again and just wants to lay down the best security they can, they just disable the option and they secure the node like usual (without taking their cracking ability into account).