It is very time consuming to do this sort of testing. I would recommend going through your code very carefully, and finding places where it would be easy to make a mistake. Then write test cases to make sure you didn't make that mistake. Keep the tests around, and as the application evolves, you can reassure yourself you haven't made any of the mistakes you predicted by running the tests.
Also, read everything you can about secure programming. As you learn about new vulnerabilities, scour your code for them, then write tests to ensure they aren't introduced later. This article from SecurityFocus, Five common Web application vulnerabilities, is a good start. Searching here on PerlMonks for security would probably yield some helpful information, too.
For more advanced testing, fuzzing might be a useful technique.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.