Tag: hipaa

If you are using FTP, you should really stop!

February 28, 2013

FTP, the “File Transfer Protocol” has been around almost since the inception of the Internet.  As anyone with a web site knows, it permits files to be easily uploaded to and downloaded from servers.  It is built into every kind of web site authoring software and even into most web browsers. Unfortunately, FTP suffers from […]

Privacy and Security Policies Taken Seriously — How LuxSci Actively Protects Your Accounts

February 15, 2013

LuxSci is a small company and our staff are well trained and vigilant, watching for social engineering and other attacks on your accounts and data.  We have very strict privacy policies and internal security policies designed to ensure that your data remains confidential and that nothing unauthorized happens to your accounts. This may sound like normal […]

WordPress for HIPAA and ePHI? Is that a good idea?

February 12, 2013

For a deep dive, see our white paper: Securing WordPress WordPress is an extremely popular content management system for both blogging and creating web sites.  It’s popular because it is quick to set up, easy to administer, has a very large supported base of add-ons, and looks good.  As a result, many LuxSci customers use […]

Email Encryption Opt Out Now Available for Outlook and Other Email Programs

December 7, 2012

A few weeks ago, we introduced the option for users in security-enabled accounts (such as users subject to HIPAA compliance requirements) to determine for themselves which messages need to be encrypted and which do not.  See: HIPAA Compliant Email – You Decide Which Messages Need Encryption The  “SecureLine Opt Out” feature was then only available to users of […]

HIPAA Compliant Email – You Decide Which Messages Need Encryption

November 16, 2012

Customer feedback is extremely important to LuxSci and we have listened once again.  Customers faced with the need for HIPAA-compliant email now have the option to decide on a per-message basis which messages need encryption (e.g. contain Protected Health Information – PHI) and which do not.  Routine non-PHI-laden correspondence no longer needs to be encrypted and users […]