, 2003-08-18
Federal prosecutors in California went too far when they put a man in prison for disclosing a website security hole to the people at risk from it.
Expand all |
Post comment
(shrug) - he had it coming.
2003-08-18
Penguinisto (6 replies)
Penguinisto (6 replies)
(shrug) - he had it coming.
2003-08-18
Anonymous (1 replies)
Anonymous (1 replies)
(shrug) - he had it coming.
2003-08-18
Beelezubb (4 replies)
Beelezubb (4 replies)
(shrug) - he had it coming.
2003-08-18
Anonymous (2 replies)
Anonymous (2 replies)
(shrug) - he had it coming.
2003-08-18
CyCOtiC (2 replies)
CyCOtiC (2 replies)
(shrug) - he had it coming.
2003-08-19
Mark D. Rasch (1 replies)
Mark D. Rasch (1 replies)
Re: (shrug) - he had it coming.
2003-08-18
Anonymous (1 replies)
Anonymous (1 replies)
(shrug) - he had it coming.
2003-08-19
Anonymous (2 replies)
Anonymous (2 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Anonymous (5 replies)
Anonymous (5 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Anonymous (1 replies)
Anonymous (1 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Anonymous (2 replies)
Anonymous (2 replies)
The Sad Tale of a Security Whistleblower
2003-08-19
Anonymous (1 replies)
Anonymous (1 replies)
The good, the bad and the ugly.
2003-08-18
Mabrick (2 replies)
Mabrick (2 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Anonymous (8 replies)
Anonymous (8 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Chris Humphries (3 replies)
Chris Humphries (3 replies)
The Sad Tale of a Security Whistleblower
2003-08-18
Bob Radvanovsky (3 replies)
Bob Radvanovsky (3 replies)
It might have been better to talk to the press.
2003-08-18
Anonymous (2 replies)
Anonymous (2 replies)
The Sad Tale of a Security Whistleblower or How to cover your corporate @$$ when sweeping a problem under the rug
2003-08-19
Ashaman (1 replies)
Ashaman (1 replies)
The Sad Tale of a Security Whistleblower or How to cover your corporate @$$ when sweeping a problem under the rug
2003-08-19
Elc0chin0 (1 replies)
Elc0chin0 (1 replies)
Just where he has got the email addresses from?
2003-08-19
Anonymous (1 replies)
Anonymous (1 replies)
What about Cali's New Law?
2003-08-20
Nick Jacobsen (1 replies)
Nick Jacobsen (1 replies)
The Sad Tale of a Security Whistleblower
2003-08-22
Anonymous (1 replies)
Anonymous (1 replies)

Ok, you're the Security Specialist. We all appreciate that you're trying to do your job. However, there "should be" company policies and procedures on what to do if something like this is found.
In the case that there are no policies or procedures it is up to you, the Security Specialist, to create these policies and procedures to the best of your ability and with a whole lot of CYA built in.
Then, there is a nice big paper trail to follow on any possible exploit. If your company does not agree to this, it may be time to find another job. However, you should NEVER actually disclose information about a vulnerability to the general public until a fix is in place. If the company refuses to do anything about the but, and has been warned, report them to the State's Better Business Burearu for unethical business practices.
However, if you wish to keep your job and not be slapped as a business troublemaker, either leave a large paper trail or quit. Either way, keep your mouth shut in the public forums so that you don't get in trouble with the new computer laws.
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/columns/179/21615#21615