You'll never think of everything a hacker might try, or rather it is safer to assume so. My advice is to make sure the project has a properly-planned alpha phase where in-house testers follow a test plan and perhaps even deliberately hack the service before it goes on general release. This is not just to tackle security but other aspects of a business critical release. And after that an additional beta phase can check the satisfaction of a small group of selected customers whose feedback would be even more valuable.
Such lifecycle decisions are not normally taken by programmers, but it covers your back if you at least recommended it.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|