True Tales of (Mostly) White Hat Hacking
snydeq writes "Stings, penetration pwns, spy games — it's all in a day's work along the thin gray line of IT security, writes Roger A. Grimes, introducing his five true tales of (mostly) white hat hacking. 'Three guys sitting in a room, hacking away, watching porn, and getting paid to do it — life was good,' Grimes writes of a gig probing for vulnerabilities in a set-top box for a large cable company hoping to prevent hackers from posting porn to the Disney Channel feed. Spamming porn spammers, Web beacon stings with the FBI, luring a spy to a honeypot — 'I can't say I'm proud of all the things I did, but the stories speak for themselves.'"
much worse has happened and it has been someone at the cable head end messing up.
Like porn on the OTA channel showing the super bowl on cable systems or porn showing up on the EAS / public access channels.
'Three guys sitting in a room, hacking away, watching porn, and getting paid to do it — life was good,'
It's not gay if we don't make eye contact with each other... Why are you staring at m-- Ohh, my bad. Carry On!
i-Guide
Now did that hack let you get FREE HBO and PPV movies or just local remap channels?
Over the years there have been stores of getting big pron PPV / VOD bills for shows they did not see how likely was it that some hacked the box so they where able to get free pron?
http://consumerist.com/2008/06/21/listen-time-warner-the-60-year-old-english-teacher-didnt-order-1400-of-porn/
One of the sillier things that the culture of individualism has brought is heroism: the idea that one person or a very small group of people are supermen, able to challenge all perceived evil and win the day. But it's bullshit. There are only two ways to make a system secure: 1) Have everyone on your side; 2) Have no one use it. 2 is approached by an awful lot of firms: why release an exploit for system X, when you get 100x the exposure with an exploit on system Y? 1 is approached another way: many eyes. Three guys in a room aren't going to find shit, no matter how much porn they watch (well, unless it's *that* sort of porn). There will always be hundreds among the 7 billion odd people who will spot something you've missed. So, a security team comprising only three people is merely there for show, and the only reason you haven't been broken into is because you've approached close enough to 1 or 2.
'I can't say I'm proud of all the things I did, but the stories speak for themselves.'"
Not proud? I assume that means that you were not proud of watching porn with three other guys. I don't even want to know what you did that might make you feel not proud.
But good going with the techniques you used to catch the bad guys,
Spamming porn spammers, Web beacon stings with the FBI, luring a spy to a honeypot
...watching porn...probing for vulnerabilities...
...of an idiot who was teaching people how to hack into certain types of setups in an open IRC channel of mine.
And he was using his employer's servers to do it!
Now this guy was, at the time, causing ALL sorts of grief for me and several of my colleagues. He kept trying to hack our message boards, hack our e-mails, break onsite computers, tried DDOS'ing us numerous times, was sniffing wifi traffic for all he was worth, etc. All while claiming he was "twice the hacker of all of us put together".
Anyhow, I was basically logged into my channel 24x7. So I'd logged the whole thing. Including the part where the guy promised to "eventually" get around to cleaning up the hack job they'd used to get in.
Well, he probably WOULD have.
Had a copy of the complete IRC log, including the mention of live customer financial data being on that server, NOT found its way directly to the company's owner.
The next time the guy came in, he was detained, his system was imaged for evidence, and he was let go.
And it took him nearly 3 months before anyone got around to actually telling him who'd dropped the dime on him.
And all without doing a single illegal thing.
I later wound up helping the FBI give him a vacation at Club Fed.
And it looks like he's going back to stay for a while.
Chas - The one, the only.
THANK GOD!!!
Nothing will ever be proven 100% secure because it's easier to break things than make them. However, typical software is akin to a car door that's not only unlocked, but swung wide open. 95% of developers have less than two weeks of security training, often less than 8 hours. They put approximately zero effort into security. It doesn't take a huge team of security experts to close the door and lock it.
When I started my current job, it took me maybe 40 hours to reduce our attack surface by 90% because my predecessor either knew nothing about security, or just didn't care.
Oh, for the love of %DEITY....
Here's a link to the one page version of the story:
http://www.infoworld.com/print/222831