Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 343
  • Last Modified:

Best practices for sending secure information over web.

Hi all,

Our organization has recently undergone a conversion to using an outside provider for much of our functionality, and it's requiring our customers to set up new user profiles on the outside provider's site.  To help them with that, we'd like to set up a page that would allow the customer to look up their new outside provider account number based on the data we have in our system, including address info, name, and SSN (Aye, there's the rub).  

I'm obviously concerned about sending SSN information from outside our secure login (where this page, unfortunately, needs to be located).  What are best practices for making sure this data is sent securely?  

We're using VB.NET 4.0 and Visual Studio Premiuim 2012 for our work.  

I'd appreciate any input you might have - security work is not my strong suit.  Thanks!

Jamie
0
Jamie Fellrath
Asked:
Jamie Fellrath
  • 2
  • 2
1 Solution
 
mankowitzCommented:
couple of options

1. HTTPS is the best and easiest, if you can't do that,
2. Use some sort of separate factor approach. For example if you have their cell phone, let them log in to your site and send them a text with the new login information. If you have their email, send it that way.
3. If you are concerned about them SENDING their SSN to the unprotected site, just ask for the first or last 4 digits. That gives a hacker only 1 in 10000 chance of guessing correctly, and you can lock down the site if they try more than 3 times.
0
 
Jamie FellrathApplication Developer/Data AnalystAuthor Commented:
We're already using HTTPS - that should be enough?  

And the user in question will not have a login on the current site any longer, unfortunately.
0
 
mankowitzCommented:
HTTPS should be enough. Very hard to crack unless you have some access to the database or the user's computer. I wouldn't worry about sending SSN over HTTPS. That's how banks and hospitals protect privacy.
0
 
Jamie FellrathApplication Developer/Data AnalystAuthor Commented:
Thanks so much! I'd forgotten we were using secure HTTP and got a little perturbed when I heard we wanted to do what we were doing.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now