Securing Data for Transmission: HIPAA and FERPA compliance
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Securing Data for Transmission: HIPAA and FERPA compliance
We have to implement a facility to provide download capability of files to a limited group of clients. The information in the files is subject to HIPAA and FERPA guidelines. We will be using SFTP, but want to go further. We want to encrypt the files themselves at 128-bit or higher and password protect them before we put them up for transmission. Our site and sources are RHEL 4 and 5 servers. Our clients will be a mix of WinXP, Mac osX, and Linux. We do not want to have to purchase/maintain digital signature certificates. We do want to be able to script the encryption and password assignment on the files. We want our clients to have to provide a password to open the file once received.
Is there a single-source, multi-platform solution for accomplishing this scenario? Is single-source necessary? Are purchased products necessary?
GnuPG works on all platforms mentioned. That's not the problem. It's the scripting of passphrases. That definately does not comply with common sense, any Best Practices let alone official standards...
Sometimes the file will be generated by an application from database sources. The output file will need to be encrypted and password protected before put up for transmission. We would want to script a password generation algorithm and then assign the generated password to the file. We are NOT talking about putting a password into a script.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.