Security threats Toolkit
Story: Be prepared to pay for security
Posted by: M Dundas (Wednesday 24 August 2005, 8:01 PM)
Don't agree 100%. I think the answer is to legally and financially responsible make Micro$oft and any other Vendor responsible for security of their software.
That will drive the cost up, but if they are going to be held accountable, they will spend the proper amount of time required to ensure that their software is secure, create proper provisions as to how the software is to be installed, configured etc.
I can't just go make a car that doesn't meet certain safety requirements. Nor can I build a building that will fall down, and say 'oops' sorry. Version 1.2 will be better. Same logic with software.
Full Talkback thread
Story: Be prepared to pay for security
-
What a load of rubbish! joe blake -
Paying for increased security (services) is one th... Arthur B.
-
So are you suggesting that those of us who *d... Chris Rankin -
Am I prepared to pay for security. Yes, with... Janet McCall
-
Don't agree 100%. I think the answer is to legall... M Dundas -
Chris, good point.
One might think of the followin... Arthur B.
-
Why is it unrealistic to expect Microsoft to produ... David Hayes
-
They should just monitor outgoing traffic. If a PC... Ofer Hadas
-
David. Good point.
Although I prefer solving cause... Arthur B.
-
Be prepared to pay for security Leader
Mr. AT Alis... A.T. Alishtari, POA and Founder EDI Secure LLLP
Back to: Be prepared to pay for security
