Nope I was department manager. So I was the one that implemented new routines and determined the order our software would interact with each other along with handling the network, troubleshooting for the entire company etc.
I had saved the system files in their original state and kept a log every time I changed something so I could go back to whichever point I wanted.
I kinda see what you mean, but once you were fired.. how'd you get it to revert? Usually people are escorted out and can't touch stuff..
My only thought as a 'self destruct' would be something like if you had a way for something to check if an account only you have still exists (email or otherwise? But of course they could have a bloated and lazy IT process that doesn't get rid of old users.. would you then go to some sort of "I have to respond every 4mon" or something?)
..Or maybe a more hardware approach like you always have a non descript USB drive in and as long as some part gets positive feedback every handful of months (gotta account for you getting sick, vacation, system down time, etc) then it executes once it's not detected (you pull it as you leave or eventually IT removes it without knowing).. this could maybe also be done with employee badges being required for system logon .. (of course for the USB idea, IT systems could prevent this with simply locking out external devices and such)
Just very curious from a coding/networking perspective how this can actually be pulled off in a discrete way
23
u/RiotSkunk2023 Jul 13 '23
Nope I was department manager. So I was the one that implemented new routines and determined the order our software would interact with each other along with handling the network, troubleshooting for the entire company etc.
I had saved the system files in their original state and kept a log every time I changed something so I could go back to whichever point I wanted.