javachik, I've applied my extensive internet debating skillz to the confidentiality issue, and here's the answer: If you stamp confidential on a page that already says confidential, then clearly you have no expectation of confidentiality based on the word confidential on that page.
¡Quod erat voila!
Can someone tell me the name of the boyish blond gladiator in the first season of Spartacus? I don't want to risk spoiling myself by looking too hard.
The shit that got me in trouble at work was hearing word of a director trying to push a change through that observed none of our controls--not of code, architecture, or security. So I called a meeting on someone else's project that had ground to a standstill because I have the relationship with the business user, and because I'm the SME on the application used as the back end.
I tried to get one of the managers to stipulate controls over the platform for which he is responsible, but he demurred, saying it wasn't his place. IT IS ABSOLUTELY YOUR PLACE. And as much of a lowly maggot I am, I'm still calling that out--the director said he'd take care of security, and he managed to completely forget to mention the component of the application that waved the security red flag.
So I waved it. IT STILL IS MY PLACE.
Why am I in trouble? Because when I told the manager he had a task that needed to be started right away, he asked if I'd start the paperwork, meaning I'd be up for the deployment in the wee hours of the morning, whereas I only meant I'd get the paperwork in under the wire, and the work part was in the hands of the platform owner.
Apparently that's too much like telling him what to do, BUT I HAVE NOTHING TO DO WITH THIS APPLICATION other than having seen a number of flagrant risks in it.
Me and the other manager usually get along just fine. No idea why he had to complain about me behind my back, but my ex-manager does actually agree it's not supposed to be my job, even if I have to see this bit through.