Are you sure your code is bulletproof? Let's see...
I've just read interesting MSDN Magazine article. If you're a software developer (or a hacker in any meaning of this word) I would recommedn to read it. For software developer I can comment it shortly:
Also make sure you read Top Ten Security Tips Every Developer Must Know.
- Only you are responsible for writing secure code. Not tools, not technologies of future.
- Never Trust Input Data. Assume all input is invalid and accept only good data, but not vice versa.
- Model possible treats that can affect your code, test your code to be bulletproof.
- Learn new possible attacks. Read books, subscribe to news.
- Test reliability (Fuzzing). Don't simply punt a crash as "just a crash." Every crach is a potential security issue.
- Do not write insecure code. IF you know a function should only accept "good" parameters - validate it. If encryption is required do not use MD5, DES (which are already broken). And so on...
- Use any tools to help find potential problems. But do not rely on them.
- Remember to review your old code becuase of it can become insecure.
Also make sure you read Top Ten Security Tips Every Developer Must Know.