Scroll down to comment or rave this story!

  • 2 raves

A Darker Shade of Grey

Problems with creating database's in a forced transpareny world
Neochick

When I first started creating databases professionaly 8 years ago, secruity was the least of my worries. Someone else would create most of the front end software for me, and encode into that the majority of the secruity protocols. As time has moved on, finding someone to do this who isn't going to put their own backdoors into it has proved increasingly difficult. Companies started asking me to create not only back-end, but the front end and all security as well. This ment I had to re-visit my coding days. After a couple of dummy runs with honey pots, I found that my protection methods left something to be desired.

Under an alias, I jumped into the hacker's world and started picking up on all their recent tips and tricks for breaking into company and personal files. Whilst wary of me at first, I have since become quite respected in their world. This keeps me up to date with my databases, and gives me the chance to adapt when new exploits come out. This however has comewith a price. To maintain my credability in this hacking culture, my alias has been guilty of cracking others protected files. I try to avoid as much damage as possible, but sometimes when everyone else arrives.... its like vultures to an animal carcass.

I don't believe I could protect my databases without this inside knowledge. I feel horrible for the owners of data that I open up, knowing that it is exactly the thing I'm working against.

Do my clients know about my 'summer job'? Yes, and a surprisingly large amount don't seem to mind all that much. This just goes to show how far they will go to have their database's secure. Willing to hire me.

I used to be a white hat. Now I am a grey hat. I fear my hats getting darker every day.

Oct 18


Please login or register to add a comment


Nominate For A Badge

Badge:
More detail on badges



NOMINATE CANCEL