Why are heads NOT rolling?
This is page 2 of the discussion. Read the opening post
Malware
This is page 2 of the discussion. Read the opening post
by fcleroux
Here here! This is exactly why I asked the question and this is exactly my point.
I have seen the worst corporate IT disasters happen because of incopetence and not one person was fired.
I now do Consulting and two or three times a year I still run into Law Firms that do not have Backups!!
by cosburn
The way your post was written is entirely designed to annoy and provoke a response. Congratulations...there are a lot of threads here.
IT management at any level has a series of jobs (as I'm sure you know).
1. Keep the company running.
2. Manage your staff so that they can accomplish tasks.
3. Manage you boss (or multiples of) to keep everyone employed and the budget to buy at least what you need.
4. If you and the staff are lucky enough to have time and some extra budget, test-buy-deploy and remediate any problems you can that exist today. Very rarely do most IT people at any level have the chance or luxury to play on the future toys.
I'm sad that you have the time to state that people should lose their jobs because of a virus attack and/or stating that the entire attack and downtime is a result of incompetence. Drop MS a line and let them know about a certain critical flaw called the OS.....they might care.
People lose their jobs for a variety of reasons, but your post 'is designed' to state that you must enjoy the process. If someone must be fired, part of a layoff or 'reduced', then it should be for the correct reasoning and done with style and intelligence. The entire event is difficult enough, but I would love to hear you explain to any number of IT people that they just got canned because of a virus attack. How's your reputation in the city you work in?
The line of reasoning in your post reveals a severe character flaw and lends strong credibility to the theory that good/great management and leaders and born, not trained.
by kingdre31
by fcleroux
OK, you are a good example of what I am getting at.
It is your job to know about threats out there, specially the bad ones.
Now, lets say you get an outbreak. Management deems thats it is because some patches were not done but that was because you being by yourself did not have the time to do it all, you DO NOT GET FIRED. Great.
On the other hand, if all along you had not ever suggested that they needed Anti Virus SOftware installed, and then got hit by a Virus. SHOULD YOU BE FIRED?
If you suggested that they have Anti Virus Software and explained to yout middle management boss that they could loosed ALL their DATA and that three days of production could be lost, but he decided NO we do not need to spend money on something as frivilous as Anti Virus Software. Should HE be FIRED if there is a dissaster??
by psk_
by mgordon
by toby
The ever famous Some Other Dude Did It
I know from personal experience that when a tech or an entire IT department gets caught with their pants down it's oh so easy to just blame someone else.
When I was a Jr. Tech many many years ago I actually witnessed the head of our IT department (fortune 500 company mind you) double talk the CEO into thinking it was HIS fault the systems were down and it was going to take him all weekend to fix the mistake and ended up getting a raise because of it.
It's really not that hard to blame someone else... so and so opened an attachment they shouldn't have or simply check the CEO's or CFO's internet history and then make a general announcement stating that a certain site (one that shows up in their history multiple times) was to blame for the infection.
Then basically all you have to do is sit back and watch the big wigs scramble to cover YOUR ass.
It really is simply a game, those that play the best go the farthest, which is why most of upper management is more or less incompetent in many companies. They simply know how to pass the buck better than the guys below them.
by fcleroux
Obviously you have not read all the threads.
My point is that sometimes people have been negligent in their duties. I have seen it from MIS Managers and Middle Management in the corporate environment.
Now I do consulting. I usually get brought in to companies that have just had BIG disasters happen to them.
If my job to find out the why's, where's, and how's, what needs to be done to fix the problems and how to do it.
Several times a year I see things like Financial and Legal companies without Firewalls, many without ANY passwords on ANY equipment, not Anti Virus Software. Very often these companies do not even have backups or very old and outdated backups.
Sometimes this is because the IT people did not do their jobs, sometimes it is because middle management people did not think it important enough, but inevitably no matter how bad or how stupid (or negligent) the reason.... no one gets fired!!
I have even seen a tech who had formatted C: /SYS on a system before he realized he was KVM'd into the server and not the workstation he thought he was on. Cost the company about four expensive days of several IT people re building their server before they could recover the DATA from tape!
If I ever screwed up that bad I would probably resign before they had a chance to fire me (as I would expect them to).
And, NO, I luckily enough never had a major Virus Outbreak anywhere that I have worked. Yes partly luck but mostly because of a little diligence.
by tc
how about you come up with a single, simple solution with proper fw protection alone, or proper av protection alone, or os patches alone that can prevent these viruses?
this simple solution should cover everything from servers, desktops, laptops and pdas/smartphones.
by fcleroux
Eddie,
We do not know or assume that nobody has ever been fired. It has not been reported by large companies that they have ever held someone accountabloe after a large outbreak.
SpyCatches Alliance Inc. is a new company that is being setup by a group of about 10 large corporate IT Consulting/Management companies in Western Canada that specialize in Disarter Recovery, Security, Anti Virus, Anti Spyware, Firewalls, VPN and such.
It is forming the alliance to better help protect their own customers by join forces and sharing resources (and employees).
This new venture has not only been succesfull already in its early state but also it has been profitable.
by eddie15068
The Golgafrincham coordinate the colour of the anti-malware strategy. Traffic light meters and colour-coded threat-status alerts are key when implemented with Visio flowcharts, Project tracking and Exchange reportage.
Heads do not roll because everything is under control.***
[*** Provided Blackberries remain functional: Dead Blackberries spell reorganisation.]
by vigilanti.x
by nottheusual1
by mr l
by nottheusual1
by kblack1a
by bndplus2
by bhunsinger
Funny no one here has mentioned the most important reason- IT security training. Even more important- non vendor security training. Look at this site- half the information is vendor provided- not exactly the most unbiased sorce of information. That's OK here, it's clearly labeled.
But how do you make the case to upper management when all you have are what they see as sales brocures? (Yeah yeah, it's a white paper. Sure it is. Printed on our very own printer's white paper)
Refusing funding for training is not, on it's face actionable, since it is and investment, not a repair. Payig someone to learn how to spend even more money is even worse.
Finally, security people are facing a backlash from y2k and the dotcom bust. "We just spent all this money and it still works great." "They said we had to keep upgrading stuff or die, we stopped upgrading and didn't die yet." or the real issue "They said we had to do this for Y2K and they lied- we could have just patched - not bought new." Any one out there who didn't see Y2K as a reason/excuse to get everything they thought they needed?
Chicken little, the boy who cried wolf. Bad training or vendor only training. They just want the latest toys to play with. Everytime they do one of their security thing it makes it harder for people to do their jobs. All of these things argue for the lack of funding.
Few people get fired for not doing someing a subordinate asked them to do. their defense is simple - My boss said we had to live in budget-I said not yet not no.
Risk management means the risks sometimes hit.
by tonythetiger
Just that, despite best precautions, malicious stuff still happens. Antivirus code cannot be written until the virus appears, leaving a window of vulnerability. The same with O/S updates. Most vulnerabilities are discovered by good intentioned people, but we don't know of ALL are, so again with the window.
I am all for getting rid of employees who are failing in their individual responsibilities, but I'm afraid that, with all these recent scares and outbreaks, that management's expectations as to what is and isn't foreseeable (hmmm, I should probably run that past the spelling people in another thread :)) may become unreasonable.
by kblack1a
by doc
I agree with this sentiment. But then again, who will be the arbiter of "was this virus/worm/malware truly preventable". As you know, some are - simply by installing an AV program and/or keeping Microsoft systems patched/updated.
But if we're looking for heads to be lopped off, then why not take it a step further? Why not fire the bonehead decision-maker that decided to implement Microsoft enterprise-wide? After all, doesn't this kind of poor decision-making warrant a good beheading?
If heads are to roll, then let's start at the top, and *then* work our way down. Firing lowly systems administrators is not quite as practical as one might think; you have to consider replacing all the beheaded system admins, which could be quite costly. Perhaps not as costly as the downtime caused by their carelessness - so the *real* fiscal impact should also be taken into account. Chopping an admin's head off as a knee-jerk reaction makes about as much sense as the decision-maker blindly selecting Microsoft for the entire enterprise.
So if your company or organization is "stuck" with a Microsoft-centric computing platform, then at least provide adequate training to those unfortunate admins that have to take care of this poor-excuse-for-a-computing platform.
After all - if you fire all the Microsoft admins - you will have to retrain their replacements anyway. So providing adequate training to begin with should probably be the fist step, and *then* fire them for failing to perform up to corporate policies and standards if worms and viruses continue to plague employee's neglected systems.
-Rene' Mente
Neptune Consulting Group, Inc.
doc@neptune.net
by mark
by sluster67
by bill.affeldt
So anyway this soldier is in combat and takes a bullet right between the eyes. Instant death.
Does the family sue the helmet maker for not putting a bridge of the nose gurad on the helmet?
Does the army fire the supply officer for giving out a helmet that didn't protect the soldier properly?
Is the captain who told the soldier to go left instead of right culpible?
Is it the fault of the Secretary of state for sending troops without proper protection?
Is it the presidents fault for misleading you into a war ?
Or is it the fault of the SOB who pulled the trigger on the gun that shot the soldier?
Or is it the fault of the leader who antagonized us into the war ?
Protecting your assets is a war. There are casualties.
So what you do is create an environment where honesty is rewarded not punished. You look at what happened and you put thing in place to keep it from happening again. It may be that the admin should be reprimanded. However it may be that the CIO should be fired for not explaining the risk of viruses to the steering comittee. It may be the CEO's fault for rejecting a proposal because he was too stubborn to understand the risks. It might have even been a defective product.
What is most irritating about this thread is the lack of attention given to the real problem. Stopping the viruses from being written and transmitted. People caught writing and distributing viruses should face VERY stiff penalties. They are liable.
I hope that all of you who are so quick to fire someone for something that may or may not have been your fault ... have something you are associated with break and your boss comes through with the broad axe.
Do you really think that sysadmin WANTED ts ee a virus infect his system? Probably not. So take some advice: use the experience to learn how to prevent things. Get to the root of the problem and then make sound decisions based on root cause analysis.
by haidehaide
by issinho
From what I read in your post, you were asking why IT HEADS WEREN'T ROLLING. You didn't mention MANAGEMENT.
Plus, we are hired to take care of the system, so LET US!!!!! So often our hands are tied with policies, procedures and company rules. That is the last thing that IT needs!!! I'm not saying to let us run rampant, I am saying to let us do our job. An IT technician should have full reign of the infrastructure. Don't limit us so that it takes longer.
Another: IT should make all IT decisions and policies. Not some management that knows nothing about our job. I have a supervisor who tries to make changes to people's jobs that he doesn't even know.
by haidehaide
by is girl
I think that the larger companies that recently got caught in the last wave of worms hold off onl applying patches routinely in order to test them.
Those of use who are truly members of understaffed IT depts don't have time to test, so we just apply the patch and hope for the best.
In the truly understaffed world of IT it's a risk to patch and a risk not to patch.
I large companies, there is enough staff to expect some testing to take place. However, this would take a few weeks to actually complete - assuming there are not other fires to put out during that period.
These days, the time between the release of a patch and a virus or worm that takes advantage of unpatched systems can be measured in hours....not weeks.
by mr l
Sorry Mike, but you (and every other IT wonk who says it's inevitable that your shop will get hurt at some point no mater what you do when you get infected/compromised)are dead wrong.
Appropriate firewall rules, appropriate AV at the server/desktop/mail gateway, appropriate mail server policies, AND making damned sure that when MS releases Critical level patches they get on your systems in a hurry WILL keep your environment safe. NOTE that I did NOT say no one would ever get infected...we can't protect the laptop that some user took home last night, got 0-day'd, then brought in and put on the network. But IF we have patched, and we have good IPS/IDS rules, good statefull firewalls, up-to-date patches and AV signatures...guess what? One or two infections do NOT take the company down..they are isolated, contained, controlled.
Mr. Cleroux, I have the this repsonsibility at a 10+ Billion/Year firm. If I screwed it up badly enough that my corporate office got taken down (when I was not refused permission to patch against the vuln that got us)...I should be fired. Period. It doesn't have to happen.
by arjee63
C'mon - I can think of two distinct instances where IT knew the risks, was informed by other people of problems with their systems that spelled trouble, and chose to ignore it. Budget and time limitations had nothing to do with it.
In one case, an "IT Pro" dragged his feet getting the corporate antivirus configured correctly. No one was getting their definitions. On top of that, even though they had purchased SMS, they weren't using it to keep Windows updated, so no security patches were going through either. One particularly nasty virus disabled the entire network, and the support staff (who have no access to SMS or NAV administration) spent three days manually patching people's computers. There was no budget or time shortage that caused this problem. The problem was just arrogance and laziness.
Another one that happened more recently is a corporation whose internet policies were so unsafe that they had been repeatedly warned they were at risk by their antivirus provider. Their local techs had to boot computers from a floppy when they went down a few weeks ago.
Sure, sometimes people's hands are tied. But, sometimes, the people who have the ability, time, and resources to take care of these problems, just don't, because they know they can fool their non-IT upper management.
Think of this. There are 400+ servers that are supported by a team of 5 people. Everytime MS puts out a patch you have to go through the routine of testing the patch on a test enviroment from there you can deploy it. Now imagine that out of these 400 servers you have 150 different enviroments. SO you have to install this patch 150 different times test to make sure it doesn't break anything then deploy it to the production enviroment. That's what happens to the large companies. People get tired of doing this every month for M$ stupidity.
Now on the other end of the spectrum. Imagane having 5 servers. Absolutly no test enviroment. One day you install this new patch and it KILLS your servers. How like like are you going to take that chance or take the chance of getting hit with a virus.
It really is a lose lose situation. BUT there is an answer. There are product out there like one by Cisco call Cisco Security Agent (CSA) I've learned that this is a great type of product. Basicly you teach it what that machine is suppose to do and if it gets hit with a buffer over flow or something like that CSA will not allow it to run. You still end up with an infected machine but the virus/worm just can't do anything.
by dsilva
Sometimes on large corporations it's a mess due to internal organization and policy.
There are sites that have a good IT resources well supported by local management that can avoid troubles. Other sites without resources or resources with limited time(management can take IT resources focus to other less important subjects) and knowledgement can put their systems into real troubles.
by jdmercha
By way of example:
I assume that we can all agree that network printers are more economical than putting a printer on everyones desk.
But what the bean counters don't see is the time spent by employees to get up from their desks and walk down the hall to get their print job off the network printer. Only to find out that someone has changed the paper. So now they have to walk back to their desk and print the document agian. Or they have to track down their print job because someone else has walked off with it.
by mhambrecht
by mipsv
Don't forget you generally have to have just cause to fire some one and being the victim of a "criminal" act is not justifiable. IE: You can't claim much insurance if you blame someone. Now, it doesn't mean that things will be all rosey for those in IT but generally managers look at this as "no press is bad press".
It would also mean a detailed blow-by-blow of company books, emails, and lots and lots of employees talking on the record. Then you would have to still prove that the attack was BECAUSE of someone in the company (they planned it) - an "inside job."
However, it doesn't mean that an employer can't find another reason to get rid of someone. Its amazing how important it can suddenly be to be on time everyday, for instance. So, senior managers might not go right away but his/her staff is slowly changed out.
by jdmercha
by blarman
In today's world of outsourcing, downsizing, and doing more with less, you suggest these aren't valid critiques? You must work in management.
Whose responsibility is it to set goals for IT and monitor progress towards those goals? Hint: Management!
If management's goal is to reduce company exploits to zero, they then would have to take responsibility to devise a strategy for obtaining the goal and allocate resources to do that. Most managers aren't either technically savvy enough to do this, or look at the expense coming off the bottom line and say "It's not worth it."
Management issue? You bet it is.
by bndplus2
Wow. What a well written, consise response.
"In today's world of outsourcing, downsizing, and doing more with less, you suggest these aren't valid critiques? You must work in management."
*claps hands*
*waves arms*
TESTIFY!
How many hours a week do most admins put in? Mine, although slower these days, is still a MINIMUM of 50. Standard is around 60. Vacations range from 10-40 (seriously - last year I got wind of some new vulnerabilities and spent time looking into them and firming up the firewall. Remotely, over a SLOOOOW connection, with my laptop. That was probably close to 40 hours (connection issues accounted for a substantial amount of that, honestly)). My efforts were required because there's nobody else here who can do what I do, and I feel a personal sense of responsibility to maintain my network whenever possible. I feel that effort and attitude are not recognized, appreciated or rewarded, and that's one of the hardest things about my job. People like this guy are typical of this type of thinking and attitude, and make our jobs so unrewarding.
"Whose responsibility is it to set goals for IT and monitor progress towards those goals? Hint: Management!"
Yup. But if there's no management committment to enabling you do to the work, then it's pointless. Around here, there's a ton of lip service but no backing it up. If there aren't enough hours to do the task, or we can't be allowed the system downtime, then how can we accomplish our tasks? How do we win? We DON'T.
"If management's goal is to reduce company exploits to zero, they then would have to take responsibility to devise a strategy for obtaining the goal and allocate resources to do that."
I define the strategy. I outline it, and they tell me I can do whatever I need to do. They say they will give me the time/resources/skills, but when it comes time to deliver, they change what they told me I'd have (downtime, resources, whatever). My company, for instance, thinks we're a 24X7 business. We KEEP it that way, for the most part, but that's due to very proactive management of the systems and applying defense in depth wherever possible. But when you need to down a system to apply a patch, you're given relatively no time at all to be fully operational again. They WANT 24X7 operation, but aren't willing to invest in the manpower, training or make other resources available that would facilitate that. If it costs money, they don't want to hear it. Since our time is free, they don't care how much of our time we spend. That's the reality. But we can't make the bits and bytes and processes line up properly without a reboot/downtime. They don't understand the intricacies involved, and for the most part they don't care. They're used to pushing sales numbers and other things that are far more easy to quantify. Computers are not absolutes and are not as easy to work with as they think they are to those of us who are technical. There's part luck, part finesse and part educated planning. And those vary. I can't count the number of times I've thoroughly researched a patch and had it blow me out of the water, anyway (ones that modify TCP/IP, for example, get a lot of my attention). Maintaining these sytems requires a liberal allowance for downtime, and often we just don't get the time we need.
"Most managers aren't either technically savvy enough to do this, or look at the expense coming off the bottom line and say "It's not worth it.""
Yet the admins are the ones who are looked upon poorly when something happens.
Even with as liberal as I am with multiple layers of defense, we still get whanged by a virus now and then (not on the servers but the clients get hit now and then). It's not that the virus scanners were broken or not updated, or that the system wasn't patched: it was because the virus scanner failed to catch it in any of the 3 previous layers (but, for the record, the desktop scanners DID catch them. This is good but also disturbing in that they should have been caught at the first point, not the last). One of the layers I need to add is a scanner from a different vendor, but that also takes money (hardware, software).
Note I did NOT say "time" as my time is worthless to them....
"Management issue? You bet it is."
You're preaching to the choir, my brother...
by blarman
by nzbn
by trekman1
I have to disagree it has everything to do with OS. Windows
architecture is full of holes and no where near as mature as the
Unix environment.
by 0troy
I think he was saying that writing software for windows is a lot harder than writing it for other OSs. Not often does Unix undergo a dramatic change in the way the operating system works. While every third windows patch seems to break custom third party programs
Agreed that if your company spent money developing or buying this tool that only runs on SP1, it's hard to say, "Abandon the expensive tool and go for something that runs on *nix." (such a move might be construed as a request to managment to fire you)
by richdemars
The makers of the faulty software should be getting sued for not doing the correct research and testing on their rush to market products. If a product is taking years to rush to market, then maybe it should take more years to correctly bring to market. If that is not financially possible, well that is to bad, that is capitalism.
An IT shop cannot rush into patch management. Business does not run on operating systems, the applications that support business runs on the operating systems. Any changes to the any part of the puzzle must be completely and thoroughly tested to keep the applications/business running first.
by pretselz
by superclone
by wroach4
by dfarrich9
It's fairly simple to do this. Take the number of people working at your corporation and average out the estimated (ask HR for an estimation and tell them why you're doing so) salaries. It's simple math.
Assuming the average salary is $40K per year, now divide that by the number of working hours in a year (2080) and you get $21.63 per hour on average per employee/user.
1000 users with an average of $21.63 per hour equals just over 21,636 per hour of uptime or if your network is down and users can't work then this is the cost of your outage on an hourly basis not including sales and profit.
For averaged sales per hour, take your yearly sales volume and do the same as above. Sales divided by 2080.
And the same can be done for profit. Profit divided by 2080.
Again, it's simple math which any manager worth his/her weight should know how to do just to show TCO and ROI for technological purchases and what have you.
by jdmercha
What about the time spent by the IT people fixing the problem. What about the time spent after the problem is fixed to investigate the root cause of the problem. What about the time lost from doing what they sould be doing instead of investigating the problem. What about the time spent explaining to everyone why the systems went down.
I could go on and on. This is also related to my previous post about the type of hidden costs that the bean counters just don't see.
by fcleroux
What if you are a Law Firm and need to do a conveyance now. Computers are down. Depending on the state or province you are in you could get fined (and sued) for not completing the deal on time. Or, you need to farm out the work to some other firm with higher costs. Some very small firms to 5 or 6 of these a day. A large firm may need to farm out several hundred a day at a cost of about $400.00 a each. What if they cannot find firms that have the time to do the work as these would all be rush jobs?? And this is all only one small aspect of the many things the firms do. No contracts get printed out. Schedules and meetings get missed. Think of all the lost opportunities.
What if it brings the PBX/VOIP system down and all new sales calls are lost??
So, yes everyone can do the smple math, its the not so simple math people have problems with. Some of it can be worked out, but at best its always going to be a guess.
by bigwazza
I can think of a few issues here. My first thought was "Are you comparing 'user letting a virus onto their system and losing their job' and the 'Manager who fails to stop a simple attack doesn't get fired' in the same organisation?"
If Company "A" fires Clerk A, but Company "B" does not fire Manager B, then it's an unfair comparison. I assume, to some extent, the reference is for the same (group of) company(ies), so the comparison has some common ground.
My next thought was that managers are people too. They are where they got for a number of reasons, one of them is their negotiation skills. If they can talk their way into a job, they can talk their way out of being fired (regardless of "hot air" or not). My boss has said many times if some of our jobs are to go, he'd cast us adrift to save his own job. No malicious feeling intended, he just needs to keep his job. He won't take the bullet unless he really has to, even if I wish otherwise. And that's a fair reality check!
Lastly, and this is two-fold, is Politics. As ugly as it is, unless you play the game - and to the rules of those in charge - you won't get anywhere. I, along with my boss, have slowly and steadily educated our senior management. They are no longer scared of computers, and we can now talk to them without the blank looks you sometimes get. They understand, so now the requests for better stuff has a better chance of success, and if it fails, it's not just a rubber stamp, but an informed decision with an understanding of the risk involved.
Maybe I'm lucky here - I don't work on my holidays, I'm not in immediate fear of losing my job through one failure, and so on. But I do know this, I would have gone after 4 years if I hadn't taken the time to educate and explain - in their terms - what was happening. I've been here nearly 10 and seen many, many changes, and my job has changed dramatically since I started.
But then, I know the executive management here are very good people. So maybe I am just lucky.
Great excuse although I have to say it's not a very good one.
I'll agree that AV products can and will most likely slow your processes down. I have customers that I work with who are in that same situation but that doesn't mean those machines should be connected to your corp network without an extra layer of protection. Having an IPS solution separating those environments would allow you the flexibility of not having AV on those machines in the "secure environment" as well as keeping your security posture from being impacted. You would also want to limit if not terminate said machines with any internet or external connectivity. Again, think of your overall security posture.
I know with some AV products you can exclude certain processes and or files/folders from scanning. There's another option if you don't want to invest in a good IPS solution.
In very large companies, there is often a disconnect between top and middle management, in that orders come down, but advice often never goes up. Sometimes there is a blocker because the nuts and bolts of IT (for instance) is not as sexy as M&A, Six Sigma or whatever the outside consultants are pushing as flavour of the month.
Here is an example which while not directly related to this thread, shows what I mean.
I used to work for Telstra, the biggest Australian telco as a contractor, looking after a system that ran their teleconferencing products. This was unusual as just about everything else was outsourced to IBM Global Services. Telstra fell out with IBM and a campaign started to "recapture our intellectual property". One of the rules wheich emerged was "Contractors should not be in charge of major systems". Our system was based on a dying technology and a new system was already in preparation. We expected to work another year and walk away after the new system was installed. However, we were told that our contracts were being terminated in favour of permanent staff. The problem was, no one in Telstra wanted the job. They therefore had to hire in two people and put them through all of the training courses. After three months, one of them could not stand the pressure and left.
The point is that management edicts (which were actually good in principle) were carried out mindlessly because no one had the guts to stand up and point out that our situation did not fit the preconception. IT security is a significant expense, but there is little if any personal payback for the top management concerned, so there is often (but not always) a wall that must be broken through to push the message upwards. It takes a fearless senior manager to do that.
by yanipen
As usual, I am late to join this discussion. Maybe I am the only one that is logged-in rigth night. Anyway, I will still say my piece.
An issue just like this was brought-up in one of our company's meetings a long time ago. We actually had a heated debate about firing people. That is what you call in your place "heads rolling". But the HR and IT was against it. It is just being insecure, and narrow-minded, and having a false sense of security, and just being overly paranoid.
So we ended-up with some resulotions and thus, it became one of our company's standing policy. Like, unless the so called virus/worm activity was proven deliberate, the employee can not be blamed entirely for the havoc that will or can happen. If it was proven that it was deliberate, then the management can take action.
It just means that things like this should be handled with care. I dont know about the place you are at, but it is entirely different from where I am.
IT people should know, in the first place that our technology right now is not 100% fool-proof. Those that are in place, which I assume are being updated regularly does not provide all the guarantee.
There a number of virus/worms, etc. that are being created every day. And a number of patches a few days after. We all know that new virus/worm is not yet recognized by security systems in place. Unless some security group has recognized the threat. So why put the blame on others?
Again, I do not know how you do things there. But here, we tend to look at the bigger picture before we point things inside that picture.
I said my piece. I hope this helps.
by cheufte
by marionuke
by mikeewalton
by mjd420nova
Todays market place is slanted to production, as
that's what earns the money. You only stop when you have to or if it doesn't interfere with regular production. Providing an outlet to users who have the need to browse or play games
means no need to do so during working hours and on production units. Diligence may sound as
a strange term but keeps the bosses happy and workers working. Each day in the life of an IT
person should be like a sponge and supervisors
should know when they need to get wrung out
and some even set aside to dry.
by pineapplebob
Why do Doctors not get fired or licensed revoked for killing people? How abotu engineers and Architects who make bad design decisions?
Simple, it boils down to we are all human and thus make mistakes. If you have never made a mistake, you have done nothing in your life. Anyhow things happen, you atay on top of it as best you can, but you cannot win every battle.
Perhaps the OP should be fired next time he makes a mistake. Duh!
by wetsox
by fcleroux
by macghee
by pretselz
FACT: Virus writers are ALWAYS one step AHEAD of antivirus makers.
FACT: There is still no effective anti-malware solution that can guarantee 100% protection against known malicious code or exploits
FACT: Not all exploits get a solution within an acceptable timeframe
FACT: There are AT LEAST 4 new viruses DAILY that comes out. This data is as of 2 years ago.
FACT: Additional software in the enterprise = additional security exploits. (New firewall? New Proxies?)
Expecting that any particular group in a company can foresee ALL possible problems(even to those directly related to their department) and provide 100%-effective preventive solutions is way too optimistic to the point of foolishness.
Btw, how much do you spend per IT staff and per computer user with regards to:
- Trainings related to IT security
- IT solutions that implement IT security policies
- Implementing multi-tiered, redundant anti-malware solutions
You oversimplify the challenge of IT security.
by gometrics
Some updates break critical applications and therefore cannot be installed. Antivirus programs tend to not work well together and consume significant computer resources and no one package catches everything. I suppose if an IT person was apathetic about the whole thing (took no precautions) then their head should role. But in my experience, the IT person/manager can be viewed as chicken little for pointing out threats (and needing money to fortify the system) until after something happens. So in this case who will you fire? The CEO or Owner? Usually won't happen.
It's a game of $, it seems like nothing will be done until the damage is already done. Finally, there are cases where some manager or owner demands inappropriate network rights. Despite many protests from IT ultimately the boss wins out and can install all sorts of trash on their computer. In one case, an owner of law firm liked to go to chinese porn sites and when scolded by the IT person they laughed it off. Maybe large companies are different but this is the world I live in.
by eduslave
I work in K-12 education, and on top of the "management doesn't know,care,understand,etc." problem there is the major contributing factor of under-funding by government. For example, in our schools probably 70% of educational computers run Win9x. Not because we don't realize it should be long gone, either. Something like 92% of the budget goes to salaries. That leaves very little for everything else, so upgrading/replacing several thousand computers is NOT going to happen quickly even if all levels want it done. This summer we replaced about 500 of the oldest machines with used machines from a broker. 2500 to go. We do have pretty complete anti-virus coverage, but firewalls for our schools are still out of reach.
So now who do we blame? The ministry, the politicians, the economy? In the end it comes down to everyone doing the best they can with very limited resources. We have been hit in the past, and as others have said, we get down to work and clean it up, and try to learn from it. Sure, we keep pushing management for more resources, and if we get some, that's a bonus. The hardest thing is not letting it eat you up.
One of the advantages of Linux is that even the newest kernel can still work on remarkably ancient hardware.
Here's a story about an elementary school in Winnipeg that converted to Linux, with the assistance of the local LUG:
www.gentoo.org/news/en/gwn/20050509-newsletter.xml
From the article:
"Cory Oldford is the vice-president of Prairie Linux User Group and manager for a remarkable community project in Winnipeg. His group was approached some time ago to switch a lab at a local private elementary school to Gentoo Linux. The lab consisted of about 30 workstations ranging from a P75 with 16MB RAM to a handful of PIII 667mhz with 128MB RAM. The machines were constantly plagued with issues caused by hardware failures and outdated operating systems and software."
by 0troy
by 0troy
by 0troy
Either the bean-counters, or management figures the total cost of lost productivity. SOMEONE is figuring it out. And if not, what kind of mickey-mouse company is it???
The real problem, I think, is the misconception that the problem was preventable and avoidable.
Until management knows that this million dollar loss in downtime could have been circumvented it's just another number that they think they have to live with.
by 0troy
What company doesn't figure ROI? or cost of downtime? If they did, they'd realize that all this patching is costing them lots of money. Or that they need to get a secondary T1. Or that the cost of an outage was way more than the last purchase request for a redundant server!
Encourage the ROI if they're not already figuring it!
by 0troy
We've got over 40 customers we completely manage IT for. Not one got hit.
Sure, not having to worry about virii for Linux is fun, but keeping windows safe is still possible. (even for a linux fan)
by 0troy
by 0troy
by systemsgod
It's the classic blame game. Like my grandma used to say: **** rolls downhill.
The board of directors asks the CIO why this happened and he blames the IT directors, who, in turn blame the IT managers who then blame the senior techs who in turn blame the junior tech who gets wrote up and prays for the day they hire someone he can blame.
by miles999
by wford
by info
Make the decision makers responsible for refusing your suggestions!
Write down the threats and (if you have any idea) the downtime or data loss which may occur if the Worst Case hits you.
Make your suggestion, tell them the cost and refuse further responsibility for the system if your suggestions will not be set up.
Put it into writing.
Will say: pass the responsibility to you seniors,
most may prefer to spent the company?s money than bearing the blame. It may be THE ONLY way to argue into our CFO and CEO!
regards
Jurgen
Management by Terrorism:
Set goals AND refuse means
by rm3mpc
I'm not averse to blaming management for all sorts of problems.
I dare say that too many businesses pay too little attention to
providing a secure environment. But consider this: Microsoft
comes out with patches all the time, and in the course of
Microsoft taking care of Microsoft, they break things. Lots of
times it's third party things, like device drivers or applications. In
fact, Microsoft sometimes breaks Microsoft stuff, too.
So, do you routinely and religiously plop every patch from
Microsoft onto your systems in the name of improved security?
How do you explain to your customers (internal or external) that
they're better off not having access to that printe or scanner
than not having access to their computer system?
It's the techies who are often reluctant to accept all the fixes
from Microsoft et al. for the very simple reason that they need
time and a sandbox to check out the integrity of these fixes. It's
time-consuming and costly, and with the accelerating
development of worms and viruses (days, not weeks, from
announcement of security hole to exploit), an almost impossible
burden to meet.
I'm picking on Microsoft (one of my favorite sports, I'll admit),
but by extension, I think the argument applies to the more
secure environments like Unix and Linux, too.
People use computers to get their work done, or for recreational
purposes at home. They don't want to invest time and money
and mental effort to defend themselves every time they turn the
thing on to write a letter. Techies should take cognizance of the
wants and needs of their constituency.
They should also take cognizance of the constraints on their
management. Sometimes, those who sit in the corner offices are
indeed idiots bent on making their quarterly numbers so they
can move on before the deluge hits, but sometimes they're
trying to satisfy everyone while dealing with impossible
constraints. Plan B is not only off with their heads, but
outsourcing to some cheapo outfit that makes promises, collects
revenues and moves on to the next sucker after their contract
isn't renewed.
by nighthawk808
by nighthawk808
It's nice to see that the Department of Labor's "Executive Placement for Morons Program" worked for you. What's next, Hooked on Phonics?
I guess you don't have to worry about being fired, do you? After all, the Americans with Mental Disabilities Act would preclude that for you.
I've said it before and I'll say it again: the most inane, incoherent, or outright useless posts always come from:
A - a person with manager in the title
and/or
B - a person with the Windows logo in their avatar
This isn't to say that all posts from the above groups are stupid, but almost all stupid posts come from them.
It is amazingly easy to say anybody could be held responsible for infections showing up on any system.
Even if a user can be tied to a specific breach of security there is no guarantee whatsoever that any given IT pro cannot be blamed for the existence of a minefield that is, in far too many cases, invisible by design.
Its not as if an employer needs a real reason to fire you any more, is it?
Armchair quarterbacks are cheaper than a dime a dozen, and when those who control your employability know less about the obstacles you face than you do, it is only normal for the uninformed (manager, supervisor, CEO) to summarily point a finger and fire anyone who cannot control damage said supervisor is already taking heat for.
It is immaterial to the uninformed that even the original writers of the programs that provide so many expolitable holes and other assorted security problems don't know they are there.
Too many of these armchair experts refuse to accept or even acknowledge the architecture of modern software companies which use compartmentalization to assure that insider knowledge of a specific segment of any program does not completely compromise the entire suite.
This is exactly why even Microsoft is left to reacting to faults it created on purpose, as opposed to preventing their occurance in the first place.
When you have perhaps 3 people in a company who know ALL THE HOLES, you can better control what specific information comes out, and know exactly who that leak can be tied to, and if you split the suite into 15 different sections, each with its own little closet of secrets, it becomes almost a piece of cake to know who to sue when someone ignores their confidentiality agreement.
With all the information that has come out about earlier redmond products for example, and their rather questionable practices regarding data mining and useage tracks, is it really any surprise that more and more cryptography is being used to specifically prevent any software engineer outside of the the original coders company from seeing what is really going on behind the GUI?
At a MINIMUM they have a duty to their stockholders to prevent software privacy... If, however, they have somewhat more nefarious purposes in mind, such as providing a surrepititious and transparent surveillance system, they have far more reason to compartmentalise everything under the sun AND encrypt every function they can, as in XP.
How is it even remotely possible for any IT department to find these holes in the midst of day-to-day business when even the original writers are most often notified of them months or years after a product has already hit the street?
ANSWER... IT ISN'T POSSIBLE!
If your organization is not specifically in the business of reverse engineering and hacking code written and encrypted by others, you have no hope of seeing the writing on a wall that is invisible by design, unless you stumble upon it, and then have the time and resources to examine it.
I would suggest every IT pro on the planet immediately start finding and archiving each and every instance of what I refer to above, just to be sure you can adequately defend your positions to those above you who may well be unaware of the facts.
I would even go so far as to blatantly suggest that this question even coming up is a shot across the bow of your employability when companies everywhere are looking for an office to which one can assign BLAME, where hackers and other operatives remain far too unaccountable for the liking of stockholders and insurance companies.
by gprinsloo
The IT department is like a soldier at war. He fights to the death and should only be transfered or killed.
Sometimes issued a medal or award but paid for success NEVER.
Bottom line, it goes with the job.
WAS IT NEGLIGENCE
If yes.. Fire them.
If no .. Leave them be and work.
If Maybe .. Leave them be and work.
Otherwise Truth be told, dont mess with them they are mostly unsociable creatures who live to work not WORK to LIVE.
by pivert
by master3bs
I was just hired prior to the latest worm attack. One of the first things I did was make sure we had the patches necesarry and adequate security. The security was actually already in place, but the virus defs and patches needed updating.
It should be a routine process.
by server queen
Look, I haven't been hit with a major worm or virus since the loveletter.vbs - and that was quite literally my first day here. My first action in this job was to shut down email for two days when I realized that almost nothing here had any virus protection on it at all.
We're very restrictive on what we allow through the firewall, types of attachments, etc., that can go through email - and all we get is flak and bitching from the customers about how our "stupid paranoia" is "preventing them from doing their jobs." But let me reiterate - we have not been hit with a virus since loveletter. Do we get thank-yous for protecting the enterprise so well? No, we get continually bitched at for being control freaks, and we get called into management meetings to explain why we don't allow people to send 100MB files through email, or .exe's, etc.
As to patching - I do patches when I'm able to. I'm the sole admin for 150 servers, none of which can easily be brought down during regular hours. This is a school district, so I have more leeway than in a corporate environment, but I still have to wait for school breaks to do widescale patching, or else go through major negotiations for planned outages. And the servers here at the central office - well, these freaking people NEVER go home, so I just have to bring them down sometimes and listen to the phones ring.
The realities of the situation are that, in most environments, there isn't sufficient staff to keep systems totally up-to-date. What staff there is is too busy fighting fires and keeping things working to be able to spend all their time researching what the latest threats and patches are. An example is the recent fooforaw with APC software - the Java certificate on the older version expired. Now, APC didn't really bother to tell anyone - including registered customers - about this. The information was out there if you dug for it, but most of us found that out when our servers started to hang on logon. Should we have been fired for not knowing that was going to happen? Are we supposed to be able to absorb this kind of information by osmosis, or spend every hour we're at work digging for the latest patches and versions on every bit of software running in our environment? That's hardly realistic.
by masinick
trekman1@... on: 08/25/05, said:
"Anyone who suggests to use windoze over a Unix OS (SUN, MAC OS X) in their environmnet should be fired".
Well, I come from a strong UNIX systems background myself, and I most certainly prefer UNIX and UNIX-like systems myself, but to make a sweeping statement like that is just inviting controversy, it isn't solving anything.
While I prefer to use inexpensive Linux desktop software at home, and I am using it right now, I can understand why people flocked to Windows and why they don't rush off to something else.
Windows software on the PC was the first thing that ordinary people could use without having the kind of degree and years of experience that I am fortunate enough to have.
I have had a long standing beef with UNIX vendors. They could have done something about usability at least fifteen years ago, but instead they fought amonst themselves and split into two or three camps, fighting against AT&T, who they feared would come in and dominate the computer industry. Instead, they wasted time while Microsoft turned Windows from a toy into a very usable and useful platform.
Microsoft made many mistakes along the way. It's obvious that they had virtually no understanding or appreciation of computer security.
I can remember in the mid 1990s, when Java came along, how it was considered very insecure to do certain things with Java. Did it stay that way? No, not at all. Sun and those who worked with Sun developed many schemes to make Java useful and usable and to isolate insecure features.
So Microsoft has ignored some things in the past and UNIX vendors have ignored other things in the past. Each can learn much from each other. Microsoft still has a long way to go to tighten up system and application security. UNIX systems still have a long way to go to make themselves easier to use for every day tasks. Linux systems have a bit of an edge on UNIX systems, but they have much of the same baggage and need some of the same improvements.
Instead of bashing each other over the heads and criticizing one another, I wish all software developers would study history and learn from it.
When I was going to college, I did not like history. In retrospect, I think it was because my teachers and instructors in those courses did not light my interest. In contrast, one of my high school math teachers lit my interest in computers and that interest has never subsided.
Let's get history and computers together and learn some lessons from each!
by trekman1
That was very well put. But, I have to say that Apple has done a
superb job of melding the complex Unix environment with a
beautiful and very easy to use interface. Unix is light years ahead
of Micrsoft. Although I still don't consider Microsoft a serious OS
but a toy like you had stated. If Microsoft OS was any good then I
wonder why they are using the Apple G5 MAC to create their games
on their new Xbox. Also, why are they using Unix systems on
hotmail.com it is because they know themselves that their OS is
unstable and cannot be used for high volume computing.
by awolfe_ii
My employer has a terrific firewall and is as aggressive about PC
and network security as you could want. 95+% of our
employees have PCs configured using a master disk image with
automatic monitoring, scanning, and virus update.
We still got hit with Zotob. Now, we didn't get it as badly as
many other organizations, but we still got it.
There is no "preventable" on Windows. Any operating system
that needs an anti-virus is inherently insecure. If Windows had
any kind of serious access control and memory protections,
viruses would be impossible the way they are on Unix.
Now what were people saying about Windows TCO being less
than Linux???
by noyoki
This discussion is closed to new replies.
Sort by Trending