Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I'm the wet blanket of despair... It's very good that you're asking. It's kinda bad that you're trying. There are many ways to mess this stuff up and doing it for a real live social-security/bank-account site the first time out of the gate is what I would call a really bad idea. Here is a partial list of concerns and ideas-

  • All requests with sensitive information (including sign-in) must be under HTTPS configured and set up on a guaranteed host; cookies must never contain customer information.
    • Cookies should be secure and httponly.
  • Taint all input. Escape all output.
  • Encrypt/salt passwords so they can't be discovered, reversed, or found in a lookup table.
  • Encrypt the stored financial and personal data. Keep the keys in a separate location; i.e., not the database.
  • Limit all access to all resources to the smallest possible permissions/connectivity needed to run.
  • Run everything as an untrusted user so you can't make dangerous mistakes.
  • Bone up on PCI compliance. Follow it.
  • Read OWASP. Take it all seriously.
  • Raise the bid on your contract, or eat the cost, to hire someone who has done all this several times to audit the project when you're close to a production release.

Good luck and stay scared. It makes more secure apps.

Update: changed PCI link to the one grep provided; it's better. Update:update: removed a redundant/awkward sentence.

Update: added OWASP and HttpOnly notes.

In reply to Re: collecting sensitive data by Your Mother
in thread collecting sensitive data by casimo

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • 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, 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, 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?

    What's my password?
    Create A New User
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others chanting in the Monastery: (2)
    As of 2020-12-06 02:11 GMT
    Find Nodes?
      Voting Booth?
      How often do you use taint mode?

      Results (65 votes). Check out past polls.