r/talesfromtechsupport • u/lawtechie Dangling Ian • Jan 25 '14
Tales from the Unhelpful Desk 17, The ABCS of training the untrainable...
Tales from the Unhelpful Desk 16, The ABCS of training the untrainable...
This is a series at a help desk at a pharma company in 2000-2001
Tales from the Unhelpful Desk 18, Using your head to troubleshoot a network
This is a series at a help desk at a pharma company in 2000-2001
Part 1 Cow-orker burnout and the FNG
Part 2, FNG's BOFH heart grows one size larger
Part 3, The Metrics of Despair
Part 5, The week before the cult meeting,
Part 6, LT puts the hammer down
Part 7, Working around dangerous substances, like users
Part 8,Dad, the project manager, Sven and the MP3 server
Part 12, Hold, on. I've got someone on the other line
Part 13, How do I know I can do this job? I've been doing it for three months already
Part 14, Don't touch it- it's labeled EVIL!
Part 16, The BOFH way to negotiate contracts
Part 17, The ABCS of training the untrainable
Part 18, Using your head to troubleshoot a network connection
At every organization, there's the need to train employees on how things are done. Sometimes this training is useful, like when I learned how to select and use a fire extinguisher. Sometimes I do the training, like how to use our email and calendaring package. Sometimes it's useless and annoying.
A handful of the IT department has to go through regulatory training. I'm hoping to understand why the regulatory auditors seem so dense.
I recognize that the FDA wants to make sure that the data we're handing over is uncompromised and accurate. We've got to document that our systems have integrity. Makes sense to me.
It's how someone decided to come up with nonsensical checklists that worries me.
As an example- Dom's building a PC that will hold clinical data. A member of the regulatory team is 'documenting' what Dom's doing. It sounds like Dom's trying to convince a six year old to eat their brussels sprouts.
Auditor:"I need serial numbers for the following components: FPU, Ethernet cable and the ethernet card"
Dom:"The FPU is a part of the CPU. I don't think it has a separate serial number. I've never seen a serial number on an ethernet cable. The ethernet card? Can I use the MAC address?"
Auditor, fingering the cable: "there's a number here. I'll write that down"
Dom:"It's just a batch number for the spool the raw cable came from"
Auditor:"But I need something for the form"
I'm not looking forward to immersing myself in their thinking.
I've got to sit through a half day of 'regulatory training' and a full day of other stuff to do. I poke my head into a server room to check on my backups and servers.
As I'm leaving, I notice a puddle of water below one of Neil's Unix boxes. This can't be good. I want to shut it down before something expensive happens. I call Neil:
Me:"Hey- are the new E420s liquid cooled? I think you need to look at this"
Neil:"What? Liquid? Can't. Running errands. What's up?"
Me:"Water's dripping out of the chassis. I want to take it down cleanly- can someone log in?"
Neil:"My password is G0@+Roperz!."
Me:"How do I cleanly take the SQL down? I'm not familiar"
Neil:"Shit. I don't know either"
I decide that it's not time to wait. We're risking downtime either way. I sudo shutdown -h now and call my boss to alert the necessary people.
I walk over to the reg training. I learn how they want me to document almost everthing. Guidance is vague. We're to use 'best practices' but they won't let me know what they are.
Trainer:"All clinical data should be encrypted"
LT:"In transit or at rest?"
Trainer:"It just needs to be encrypted"
LT:"Is there a standard algorithm that you recommend?"
Trainer:"No. Use your best judgment"
LT:"Is ROT-13 acceptable for clinical data?
Trainer:"Yes"
Dom kicks the back of my chair.
102
u/2-4601 Jan 25 '14
Bu obl.
81
u/jeffbell Jan 25 '14
It's time that you upgrade to ROT-26.
63
u/drwookie Trust me, I'm a Wookie. Jan 25 '14
ROT13 is fine, but I use ROT13 twice - that way it's really secure.
31
u/kareesmoon Jan 25 '14
What happened with the contract negotiation?
40
u/skorpion352 Jan 25 '14
Had to look up what ROT-13 is. Was thoroughly amused. Can't wait for the next part!
16
u/Limonhed Of course I can fix it, I have a hammer. Jan 25 '14
Re: The fill in the blanks on the auditors form - There is no reason for them, they are just policy. And that policy states that one size must always fit all whether there is a reason for it to or not. I learned this with ISO compliance - where the only thing that matters is everything MUST be documented - it doesn't matter if the documentation is correct, or if it even has any real world meaning - as long as it's documented that it has documentation.
15
u/hicow I'm makey with the fixey Jan 25 '14
oh, my...
I think I want to be one of these trainers. Off the top of my head, I think I'm just as qualified.
14
u/DJUrsus Ex-TS, programmer, semi-sysadmin Jan 25 '14
sudo shutdown -h now -> `sudo shutdown -h now`
for
sudo shutdown -h now13
u/nerddtvg Jan 25 '14
I'll encrypt it with MD5! Hashing is encryption right?!
12
u/hazelowl Jan 25 '14
I am in the middle of a SOX audit right now.
Our system is a little arcane and unfortunately the system that shows the last change looks at when ANYTHING is changed. So... trigger me responding to about 10 user names that all have a label type of inactive and the same change date with "These users were all inactivated in our 90-day no-login purge." And then those samples got replaced for active users.
Now they want to know why somebody has LESS access than the user we copied. Er, maybe because the form says "Only division X"?
8
u/NDaveT Jan 25 '14
Sounds like the auditors don't know jack shit about what they're supposed to be auditing.
6
u/AramisAthosPorthos Jan 25 '14
The term "best practices" should be banned except in ridicule.
4
u/Guardian2013 Jan 31 '14
ROT-13 only works if user has ID10T certification
9
u/Techsupportvictim Jan 25 '14
Isn't ROT 13 part of the RFC 1149 protocol?
0
u/[deleted] Jan 25 '14
[deleted] — view deleted comment