Skip Navigation
Malicious Compliance @lemmit.online Lemmit.Online bot @lemmit.online
BOT

Boss applies policy, employee gets mad, CEO rips employee a new one.

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/maliciouscompliance by /u/Eldon42 on 2023-06-26 00:45:07+00:00.


Back in the early 2000s I was working for a local council in New Zealand. If you're not aware, NZ has a central govt, and a series of local areas around cities or rural boundaries, each run by an elected Mayor and Council.

The day to day business is, of course, done by employees in a typical business structure.

One of the things about this is that all computer systems are regarded as being "owned" by the council, and kinda-sorta by the populace. It a member of the public wants to see what's on the computers, they can make a request under the Official Information Act, and see pretty much anything, except private data. (Private data being defined by the Privacy Act as basically names, addresses, birth dates, phone numbers, etc.)

Also working in the council offices was a small business, that had an exclusive contract with the council. This group handled the more physical aspects of the council systems: maintenance of roads, sewer and water systems, etc. If the council said "we need a new pipe there", this small business made it happen.

Thing is, the Small Business leased (this is important) their computers from the council. The small I.T. team (three people, including me) built and supplied those machines. We owned the software that was on them, and they were connected to the internal council network. This meant they were subject to the same local govt and council policies as the rest of us.

Periodically, we in I.T. would clean out large files. (Early 2000s, when storage was expensive, and we were limited due to budget, etc.)

Now, the staff were fully aware of this, and knew to keep personal files to a minimum. If we, during a purge, found large personal files, we could delete them at our discretion.

During this time we found some... videos... on an SB employee's machine. It was pornographic, and not the nice kind of porn either. The words "fecal", and "mouth" apply.

Because this violated council policy in oh-so-many ways, we deleted it quietly.

The employee in question complained, claiming we had removed "personal" files. (I never saw the videos, happily, but my understanding is that he wasn't in them. They were stuff he had downloaded.)

We pointed at the policy.

He went to the CEO and complained.

The CEO came to us. My boss had figured this might happen (the employee in question was an... interesting... guy), and showed the CEO one of the videos. Which was on the backups, just in case we deleted something we shouldn't and had to restore it. (We were good enough at our jobs that we never had to do that, but better safe than sorry.)

I wasn't there when it happened, but by all accounts the CEO hauled the employee and the employee's boss (boss of the SB) to an out-of-hearing location and ripped them a new one. The only reason the employee wasn't fired was because he technically worked for the SB, and not the council.

FYI, we would regularly block porn sites. But, being the early 2000's, new ones popped up all the time. Unless an employee tried to access them, we probably didn't know they existed. It's not that we were prudes, it's just that most staff weren't stupid enough to browse that stuff at work.

0
0 comments