?
Solved

Best practices for sending secure information over web.

Posted on 2013-11-15
4
Medium Priority
?
341 Views
Last Modified: 2013-11-15
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
Comment
Question by:Jamie Fellrath
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 24

Expert Comment

by:mankowitz
ID: 39651132
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
 
LVL 1

Author Comment

by:Jamie Fellrath
ID: 39651372
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
 
LVL 24

Accepted Solution

by:
mankowitz earned 2000 total points
ID: 39651427
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
 
LVL 1

Author Closing Comment

by:Jamie Fellrath
ID: 39651874
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

Get real performance insights from real users

Key features:
- Total Pages Views and Load times
- Top Pages Viewed and Load Times
- Real Time Site Page Build Performance
- Users’ Browser and Platform Performance
- Geographic User Breakdown
- And more

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Thoughout my experience working on eCommerce web applications I have seen applications succumbing to increased user demand and throughput. With increased loads the response times started to spike, which leads to user frustration and lost sales. I ha…
International Data Corporation (IDC) prognosticates that before the current the year gets over disbursing on IT framework products to be sent in cloud environs will be $37.1B.
This video teaches viewers how to create their own website using cPanel and Wordpress. Tutorial walks users through how to set up their own domain name from tools like Domain Registrar, Hosting Account, and Wordpress. More specifically, the order in…
Learn how to set-up custom confirmation messages to users who complete your Wufoo form. Include inputs from fields in your form, webpage redirects, and more with Wufoo’s confirmation options.
Suggested Courses

741 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question