I think the key is that when you're designing a scold, you should ask whether a user circumventing the scold is going to be more dangerous than an unscolded user.
I'm reminded of a prior employer who didn't want us doing nontrivial networking at our desks, so they used STP traffic as a sort of canary. If you plugged in a switch that was smart enough to be running STP, your port would be disabled for 30 minutes.
So of course, we puzzled it out with wireshark, disabled STP, and created a monster by running network cables over the cube partitions. Sometime later we accidentally brought the network to its knees with the fallout of a switching loop (which is what STP prevents).
As a policy, it was like if you needed to pass a breathalyzer in order to put on your seatbelt.
At first I thought you were referring to shielded twisted pair cables for Ethernet, then I realized you were talking about the spanning tree protocol for switches.
I'm reminded of a prior employer who didn't want us doing nontrivial networking at our desks, so they used STP traffic as a sort of canary. If you plugged in a switch that was smart enough to be running STP, your port would be disabled for 30 minutes.
So of course, we puzzled it out with wireshark, disabled STP, and created a monster by running network cables over the cube partitions. Sometime later we accidentally brought the network to its knees with the fallout of a switching loop (which is what STP prevents).
As a policy, it was like if you needed to pass a breathalyzer in order to put on your seatbelt.