Post reply

Strategy advice for storing Personal Identifiable Information

  • October 22, 2018 at 8:12 am

    #366399

    Hello,  I am looking to understand best practices on how to store Personal Identifiable Information.  This project has not started yet and all looking to do my due diligence.  The high level is that the assignment is to determine how to best store information such as SSN, DOB, and possibly scanned documentation. 

    The intent is to allow users to enter SSN, DOB data via a public web interface and/or upload a scanned document containing applicable information.

    From the database side, what is the best way to safely store and decrypt this information?

  • October 22, 2018 at 9:06 am

    #2010598

    It's not that easy.  You have to understand the whole gambit of things including the real meaning of protecting data at rest as well as encryption of the sensitive columns and all that goes with both.  My recommendation would be to get some professional help so that you don't end up reading about yourself in the morning news.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • October 22, 2018 at 9:38 am

    #2010614

    Ha!  Thank you Jeff! =)

  • November 1, 2018 at 7:57 am

    This was removed by the editor as SPAM

  • November 1, 2018 at 7:58 am

    This was removed by the editor as SPAM

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply