Re: Securing fields
- From: "David Lozzi" <dlozzi@xxxxxxxxxxxxx>
- Date: Thu, 8 Jun 2006 00:39:11 -0400
Yes, its more of a How than a Should. I'm working on .Net 1.1.
--
D a v i d L o z z i
Data & Web Technology Specialist
Delphi Technology Solutions, Inc.
Wilmington, MA
dlozzi@(remove this)delphi-ts.com - www.delphi-ts.com
"PeterKellner" <pkellnernews@xxxxxxxxxxxxxx> wrote in message
news:3d9f82pa8evfh6l380b4euf7a2ce3l90l1@xxxxxxxxxx
On Wed, 7 Jun 2006 23:55:49 -0400, "David Lozzi"
<dlozzi@xxxxxxxxxxxxx> wrote:
Howdy,
I'm planning on storing credit card numbers in my SQL database for online
ecommerce. Whats the best scenario to secure the data in SQL? Can I
encrypt
the field so if browsing table data it won't appear? Of course i'm using
SSL
for capturing the data from the website, sending it SQL. the SQL database
has limited logins and access but I want to protect this information as
best
as I can.
Thanks,
Great idea to encrypt it in the server. I wish more companies would
do this. I'm not sure if you asking whether you should, or how you
should. If you need help on the how side, the book Pro ASP.NET 2.0
2.0 in C# 2005 by Apress has a great example of doing exactly what you
are looking for on page 859. Their source is probably on line also.
(it's chaper 25)
good luck
Peter Kellner
http://peterkellner.net
.
- References:
- Securing fields
- From: David Lozzi
- Re: Securing fields
- From: PeterKellner
- Securing fields
- Prev by Date: Re: Securing fields
- Next by Date: Re: SelectCountMethod error - looking for parameters?
- Previous by thread: Re: Securing fields
- Next by thread: Re: Securing fields
- Index(es):
Relevant Pages
|