|
Posted by =?Utf-8?B?Um9uIEg=?= on December 20, 2007, 9:13 am
If you were Registered and logged in, you could reply and use other advanced thread options Hi, I would like to know more on what you mean by :Flush the card
information after confirmation. If i've made purchases using a card #
where would that number be hiding on my computer. Thank You Ron
"jwgoerlich@gmail.com" wrote:
> Hello Griff,
>
> You may want to spend time researching the Payment Card Industry (PCI)
> Data Security Standard. This lays out in detail the best practices for
> handling credit card information.
>
> My advice is to not store the credit card at all. Process the
> transaction and then flush the card information after confirmation. If
> you abosolutely must keep the data, consider encrypting it at the
> database level. This incurs a performance penalty but is likely the
> most straight forward implementation.
>
> Regards,
>
> J Wolfgang Goerlich
>
> Related Links:
>
> Payment Card Industry Data Security Standard Compliance Planning Guide
>
http://www.microsoft.com/downloads/details.aspx?FamilyID=D8320DF1-D0D0-469F-A6FC-B53987BD74C2&displaylang=en
>
> Implementing Row- and Cell-Level Security in Classified Databases
> Using SQL Server 2005
> http://www.microsoft.com/technet/prodtechnol/sql/2005/multisec.mspx
>
>
> > If sensitive information (such as a credit card) has to be saved to a
> > database then there is a duty of care to protect this information.
> >
> > If the data is saved in plain text, then there is a concern that a hacker
> > gaining access to the server will therefore gain access to the credit card
> > data.
> >
> > One option is therefore to encrypt it. This means that the data is stored
> > on the server in an encrypted format. However, at some stage, the software
> > will legitimately need to decrypt the data in order to use this information.
> > To achieve this, it has to have access to the key to decrypt the
> > information. If the software has access to this decryption key then surely
> > so will any hacker. It would be equivalent to buying a secure safe and
> > hanging the keys next to it.
> >
> > There must be a more secure implementation - could someone describe it>
> >
> > Many thanks
> >
> > Griff
>
>
|