A long time ago, I worked for a company that had the firewall access logs available on our intranet. Probably the most popular one was who was trying to visit the porn sites. To this day, I have trouble keeping a straight face when I meet some of the people in that company because I know which particular leather/animal/gay/[insert fetish here] site they were trying to get to.
I asked one of the people responsible for that what they heck they thought they were doing. Were we begging to be sued? He replied "they signed an employment contract which forbade those activities. If they sue us, we'll win."
Anyone care to venture a definition for Pyrrhic victory?
I said "that's fine. But tell me, have we worked out how much it will cost us to win?"
The logs were taken down the next day.
Personally, I would not risk a programmatic approach with something this sensitive. What do you do if someone finds a hole in your code? What if someone comes behind to maintain the code and they open up a hole? All in all, I think a physical separation is the way to go. From an ethical standpoint, don't risk it.
Cheers,
Ovid
Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.
In reply to (Ovid) Re: Which way to go?
by Ovid
in thread Which way to go?
by bman
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |