Post reply

Encrypting Data

  • May 16, 2008 at 10:59 pm

    #816830

    jim.powers (5/14/2008)

    Another thought would be doing a cost-benefit analysis of taking the "risk" to be encrypted or not. Of course, the risk if you are not encrypted is that the data falls into the wrong hands. The risk, on the other side as was mentioned in the article, is losing the certificate. Which risk would cost the company more? Helping customers when your database is lost or replacing the lost data? Is doing a cost-benefit analysis reasonable or is the generally accepted approach to encrypt regardless of the risk? It also seems that the cost of the certificates should be included in that cost-benefit analysis. How about the cost of performance (or is this a non-issue)?

    That's not the only risk... if you don't pass PCI standards and are deemed "non compliant", the company could loose any CC or ACH Merchant Agreements necessary to do business.

    --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)

Viewing post 16 (of 16 total)

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