Warning: Constant ABSPATH already defined in /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php on line 24 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 Warning: Cannot modify header information - headers already sent by (output started at /customers/0/c/e/ogenstad.net/httpd.www/wp-config.php:24) in /customers/0/c/e/ogenstad.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1673 {"id":62,"date":"2006-09-25T19:06:43","date_gmt":"2006-09-25T18:06:43","guid":{"rendered":"http:\/\/ogenstad.net\/2006\/09\/25\/the-tale-of-the-disgruntled-employee-part-13\/"},"modified":"2006-09-25T19:06:43","modified_gmt":"2006-09-25T18:06:43","slug":"the-tale-of-the-disgruntled-employee-part-13","status":"publish","type":"post","link":"http:\/\/ogenstad.net\/2006\/09\/25\/the-tale-of-the-disgruntled-employee-part-13\/","title":{"rendered":"The Tale of the Disgruntled Employee – Part 13 – Conclusion"},"content":{"rendered":"

Two weeks later a server from Exibice connected to a box under n3m0’s control. Show time, I wonder if Mark can say \u00e2\u20ac\u02dcSchema Admin’<\/em>.<\/p>\n

At Beateval<\/strong><\/p>\n

“Hello, this is Thomas how may I help you?”
\n“Hi, my computer just went all blue. I tried turning off the power but now it doesn’t start.”
\n“Did you change anything on your computer?”
\n“No, and my colleagues have the same problem.”
\n“Huh,” suddenly Thomas saw the counter for incoming calls rising drastically.<\/p>\n

Someone shouted behind him when he looked back on his computer screen he saw that the virtual machine he had connected to the Exibice network had crashed. The host machine on the Beateval network was running fine.<\/p>\n

At Exibice<\/strong><\/p>\n

“What is happening?” Mark roared.
\n“We don’t know,” Keith whispered.
\n“What do you mean don’t know, what have you done?”
\n“It was just patch Tuesday<\/a>, one of the updates might have been flawed.” Ben said, his voice not much louder than Keith’s.
\n“Then remove the damn flaw!”
\nAfter a moments silence Keith worked up the courage to answer, “We can’t.”
\nMark just stared at him, Ben jumped in.
\n“We can’t get into the servers, our passwords doesn’t work. Something must be wrong with the AD.”
\n“The local server passwords don’t work either.”
\n“Oh, how delightful,” Mark said sarcastically. At least I won’t have to spend a fortune on Christmas bonuses.<\/em> “Didn’t you write the passwords down somewhere?”
\n“Yes, but we think someone might have\u00e2\u20ac\u00a6 changed them.” Keith said nervously.
\n“Thank god it’s Friday then, now you know what to do during the weekend. Let me know when this is fixed, I don’t care what time you call.” Mark walked away.<\/p>\n

Ben and Keith exchanged a glance, neither of them looked confident.<\/p>\n

Mark called them both several times during the weekend, not once did they have any good news to share with him. When Monday came the network was still a mess, and nobody could work.<\/p>\n

Two weeks later the network had been redesigned from scratch. The board of directors wasn’t impressed. Shortly thereafter Mark was sacked and a new CTO was hired along with a separate CIO.<\/p>\n

Please note this is a purely fictional story<\/a>, any names found here are made up. I’ve written this because I like writing, if someone reads it and enjoy it: great. If they get more conscious about security, that’s a bonus. If you have feedback or comments on the story please share them.<\/em><\/p>\n

Further Reading:<\/strong><\/p>\n