11 replies
I might consider giving them my own written report of my own evaluation of their present network infrastructure, to include hardware, software and procedures. I'd include a worst case scenario outcome should one of those factors fail, and make my own recommendations to avoid it. The report would be compared to the auditor's report, however, so you might have to either defend yourself if it differs too much, or be "humble" enough if you missed too much.
But by providing your own report, you'd be covering yourself in case of some sort of failure or breech, and you might also be solidifying you position with them.
Don't be hesitant to call things the way you see it, do what you believe to be the right thing, and just let the chips fall where they may. If you do, they'll usually stack up in your favor.
by zlitocook
Poster rated this answer.
I might consider giving them my own written report of my own evaluation of their present network infrastructure, to include hardware, software and procedures. I'd include a worst case scenario outcome should one of those factors fail, and make my own recommendations to avoid it. The report would be compared to the auditor's report, however, so you might have to either defend yourself if it differs too much, or be "humble" enough if you missed too much.
But by providing your own report, you'd be covering yourself in case of some sort of failure or breech, and you might also be solidifying you position with them.
Don't be hesitant to call things the way you see it, do what you believe to be the right thing, and just let the chips fall where they may. If you do, they'll usually stack up in your favor.
by zlitocook
Poster rated this answer.
by cg it
sometimes patches and updates can do more harm to a network and servers than security threats from the Internet. Case in point XP SP 2. The firewall is turned on by default and in a network environment can cause problems with connectivity to DCs. So no critical patches on networked computers aren't a bad thing unless they are to fix critical problems not security related provided that workstations don't access the internet.
Being a sacrificial lamb, theres really no place to run even if you leave the company, if they have pegged you as the sacrifice, your it.
by zlitocook
Poster rated this answer.
by zlitocook
by zlitocook
by techierob
It would pay; if anything to have a base "standard" in an update level. When I first started at work we had an average of 37 critical updates missing; though the network was "stable" it was almost knocked over completely by the DCOM vulnerability earlier this year. Since then I have implemented Microsofts SUS (software update service) and a few registry tweaks in the GPO to push out all neccesary updates. Now the average is one missing patch - being SP2. The network has been as stable as anything.
Personally if it's a situation like a bank; or a company that deals in private information - security is king and you have increased responsibility to keep everything up to date as you possibly can - and dont forget your documentation.
by zlitocook
Poster rated this answer.
by zlitocook
This discussion is closed to new replies.
Trending Security posts
Sort by Trending