MANAGED FILE TRANSFER: 10 STEPS TO HIPAA/HITECH COMPLIANCE

Transcription

1 WHITE PAPER MANAGED FILE TRANSFER: 10 STEPS TO HIPAA/HITECH COMPLIANCE

2 1. OVERVIEW Do you want to design a file transfer process that is secure? Or one that is compliant? Of course, the answer is both. But it s not always easy to meet that objective. Good business practice dictates data protection for you, your customers, and your business partners including data-in-motion. But, even the best security practices do not alleviate the need to demonstrate compliance with a variety of regulations and standards that can carry high contractual, civil, and criminal penalties. Plus, the indirect loss of faith of your customers or business partners can have an incalculable impact on your bottom line. Most organizations require that all file transfers are secured. In particular, all must comply with HIPAA (Healthcare Insurance Portability and Accountability Act) and HITECH (Health Information Technology for Economic and Clinical Health Act). Often popular secure protocols, such as SSL or SSH, are used when data is transmitted outside the corporate firewall to customers, business partners, or other departments. Although secure protocols support a secure and compliant file transfer process, they are only one component in ensuring that your security goals are met. Delivering security and compliance with your file transfer process requires a Managed File Transfer solution to ensure that your data is at all times. Although secure protocols support a secure and compliant file transfer process, they are only one component in ensuring your security goals are met. Coviant Software offers Diplomat Transaction Manager, a suite of Managed File Transfer products that secure data-in-motion and adress HIPAA/HITECH compliance. Diplomat Transaction Manager brings together the security and workflow management features that IT and secur i t y professionals need in an easy to implement, cost- effective Managed File Transfer solution for automating your secure file transfer process. Knowing whether your file transfer process complies with HIPAA can be difficult. This white paper helps IT and security professionals who need to successfully implement and manage file transfer processes that address HIPAA and HITECH compliance. First, 10 practical steps to automate your secure file transfer process are detailed. The paper then reviews the sections of HIPAA and HITECH that relate to secure file transfer processes and how the 10 steps can meet the HIPAA/HITECH requirements. MANAGED FILE TRANSFER: 10 STEPS TO HIPAA/HITECH COMPLIANCE 1

3 10 STEPS TO SECURE 2. FILE TRANSFER STEP 1: CREATE A SECURE CONFIGURATION Secure file transfer requires a solution that spans the corporate firewall. One part of the solution, such as a secure FTP or web server, is located outside the firewall and acts as a temporary repository for files being transferred between business partners or other entities. Another part of the solution, such as a Managed File Transfer solution, resides in a secure location inside the corporate firewall and manages file transfers to and from the FTP server. Secure FTP servers are popular among business partners that want to standardize on non-proprietary solutions. To ensure file transfer security, only the secure FTP server should be outside the internal firewall and a Managed File Transfer solution, such as Diplomat Transaction Manager, must be safely inside the internal firewall. FIG. 1 SECURE FILE TRANSFER CONFIGURATION Job Scheduler Data Source File Transfer Manager 2 COVIANT SOFTWARE

4 STEP 2: CONTROL ACCESS Control access to your file transfer solution. Both the FTP or web server and the Managed File Transfer software must be designed and implemented to limit and monitor access when setting up file transfers and when file transfer jobs are run. Limiting users, tasks, and data accessibility prevents unintended errors and makes it more difficult for outsiders to successfully breach your file transfer solution. Set up access controls during implementation of your Managed File Transfer solution to: Protect internal communications. Most administrative consoles for FTP or web servers and Managed File Transfer software use client connections to communicate when setting up file transfer tasks. These client connections should be encrypted with SSL or other secure protocol. Encrypt access data. File transfer solutions should always encrypt sensitive data at rest and only decrypt it as needed, such as when the application is started or when file transfer jobs are executed. Encryption of user IDs, accounts, passwords, and encryption pass-phrases prevents unintended use of the access. Be careful to avoid file transfer applications that store data in plaintext, such as batch files or registry entries. Create unique user accounts. Any user uploading or downloading files from your FTP or web server needs to be uniquely identifiable with a user ID and password. Disable anonymous connections. Require complex alphanumeric passwords that must be updated at least every 90 days. Having individual accounts for each of your business partners or other internal groups means you can swiftly shut down accounts in the event of a possible security breach. Limit privileges on accounts. Each new FTP or web server account creates a potential point of access to your secure file transfer solution. When setting up new accounts, strictly limit privileges based on the precise needs of each user. Restrict access to only one default directory for each account. Restrict read, write, and delete privileges based on whether the user will be sending or receiving files from your server. If possible, restrict access to a limited set of IP addresses. Terminate inactive sessions. Each unattended administrative logon and each FTP or web session can create easy access to secure file transfer management software, as well as to data on FTP servers. Each logon should be set to automatically terminate after a specified period of time. STEP 3: AUTOMATE TRANSFERS Automate file transfers to reduce errors and limit access to sensitive. A file transfer solution must allow you to run jobs on an automated schedule using the job scheduler of your choice. You need the flexibility to use an internal scheduler that comes with the file transfer solution, a system scheduler (e.g., Windows Scheduler), or a scheduler in a separate application to kick off file transfer jobs that integrate with your business workflow. Running jobs automatically means that you can eliminate the hit-and-miss execution of file transfer jobs using a manual process. Jobs run on time. Plus, the correct encryption key and logon eliminate the possible introduction of a variety of security errors into the file transfer process. Automate file transfers to reduce errors and limit access to sensitive. Automated job execution means that users do not need to know sensitive access, such as user names, passwords, and pass-phrases. Each manual intervention required to complete a secure file transfer creates an opportunity for user error and for capture of sensitive passwords or pass-phrases. Look for file transfer solutions where access can be entered once and used as needed at run-time. MANAGED FILE TRANSFER: 10 STEPS TO HIPAA/HITECH COMPLIANCE 3

5 STEP 4: AUTHENTICATE USERS AND PROCESSES Require user authentication. User authentication ensures that only a limited number of known users with unique privileges can access your file transfer solution. Linking authentication to each user s network or local logon identity both simplifies user authentication with a single sign-on and strengthens security by ensuring that only named users have access to file transfer set-up tasks. Track all user activity. A file transfer solution must capture user activity data each time file transfer set-up data is changed. Knowing when file transfer set-up data was changed and who changed it provides an audit trail that simplifies the tracking and correction of problems. Authenticate all processes making file transfer requests. When an automated process initiates a file transfer job, the process must be authenticated much like a user might need to log into an application to manually encrypt, sign, and transfer a file. Any file transfer solution needs to authenticate job processes that attempt to initiate file transfer jobs. A process that requests a file transfer job be run can be authenticated with a password, user ID of the process making the request, or other authentication method. User authentication ensures only a limited number of known users have access to your managed file transfer solution. STEP 5: ENCRYPT FILES Encrypt all files before they leave the corporate firewall. Data files should be encrypted in a secure area before transfer to an FTP or web server in the DMZ. Using secure transmission protocols only protects data in transit. As soon as files are at rest on a server in the DMZ, they are vulnerable to attack. Some FTP servers offer data encryption, but these solutions can create a security loophole by waiting until files are in an internet-accessible location before encryption. Select a solid, widely-used encryption standard, such as OpenPGP. OpenPGP is one of the oldest public key encryption technologies. Because of its popularity, many users spend time attempting to find vulnerabilities in it. And, when vulnerabilities are found, they are rapidly addressed. Use good encryption practices. Strong encryption algorithms are important, but good encryption practices are equally valuable in decreasing the possibility of a file being breached. Create the minimum number of keys required to meet your business needs. If you select OpenPGP for file encryption, you have the option of using multiple encryption sub-keys with consecutive validity periods. Each new encryption sub-key provides the same security as creating a new key pair without the administrative hassle of sending a new public key to your business partners. When you create a new OpenPGP key pair, set up multiple encryption sub-keys that are valid for short intervals, such as a year or less. 4 COVIANT SOFTWARE

6 STEP 6: SIGN AND VERIFY FILES Sign and verify files to ensure integrity and non-repudiation. Sign all outbound data files and check for valid signatures on all inbound files. Signing and verification are the best way to guarantee non-repudiation of origin and to ensure decrypted files are safe to process. Verifying signatures on every file ensures that the files you receive have not been altered during transit and confirms the identity of the sender. With an encryption standard like OpenPGP, a signature is created and affixed to a file before it is encrypted in preparation for outbound transmission. The private key of the sender is used to create the signature. Without a signature, a recipient has no way to determine the sender of the file. When the file is received, the file is decrypted and the signature can be examined before the file is processed. Signatures are used to determine the sender of the file as only the public key of the sender can successfully verify a signature. If the signature verification fails, then the file should not be processed. Signatures verify the integrity of files. Part of the signature contains a hash of the original file. As part of the signature verification process, the hash is recalculated using the decrypted file and compared to the hash in the original signature attached to the file. Matching hashes mean that the file has not been altered since the signature was attached. In other words, the integrity of the decrypted file has been confirmed and it is safe to be processed. Sign and verify files to ensure data integrity and non-repudiation of origin. STEP 7: USE SECURE PROTOCOLS Use secure transmission protocols to protect logon data and add an extra layer of protection to encrypted files being transferred. Secure protocols protect logon data during each user access. File encryption protects your data, but does not protect the logon data used to access an FTP or web server. Secure protocols establish a secure connection with an FTP or web server before sending the logon data used to authenticate a user, such as usernames, passwords, and keys. If attackers capture logon data, they can initiate other file transfer jobs and potentially transmit files with malicious content. Without secure transmission protocols, an encrypted file can be captured intact during transit. Once the encrypted file is in their possession, attackers can work on decrypting the file at their leisure. Using a secure protocol provides an additional layer of encryption that must be penetrated before a file is compromised. MANAGED FILE TRANSFER: 10 STEPS TO HIPAA/HITECH COMPLIANCE 5

7 Use audit data strategically to demonstrate comprehensive data security and regulatory compliance. STEP 9: CAPTURE AUDIT DATA Capture audit data to demonstrate regulatory and internal audit compliance. Audit data can be used strategically to demonstrate regulatory compliance or tactically to confirm to a business partner the encryption key and destination location used by a specific file transfer job. Proving that you have a secure file transfer process can be an arduous task. Audit data needs to be both comprehensive and easy to analyze. Your file transfer solution needs to capture extensive data in a standard format, such as a SQL database. Two types of audit data are critical: STEP 8: ARCHIVE ENCRYPTED FILES Encrypt data files with your own master key before archiving. Archived files can be essential component in providing the business a record of that has been transferred. These archived files need to be equally as secure as the files that were transferred. Archival of encrypted files provides protection in case of an internal security breach, but you must be able to decrypt the archived files when they are needed. Encrypting archival copies of files to your own master key before storing in a secure location creates a repository of secure files that are safe and meet your business needs. Don t keep archive files that you can't decrypt. When you are encrypting files to be sent to your business partners, you use their public key. You will not be able to decrypt these encrypted files unless you also encrypt them with your own master key. Job and file data. Detailed on each file transfer job and each file transferred can demonstrate that secure procedures, such as encrypting files before transfer and use of secure transmission protocols, were used for each file transferred. User activity data. Data on who accessed your file transfer solution is equally as important. If files were transferred incorrectly, questions of who may have set up or updated the file transfers may become critical. The integrity of audit data must also be ensured. If you capture audit data into files, limit the user identities that are allowed to write, alter, or delete audit files. If you use database technology, such as SQL, limit write access to the audit tables to the identity used by the file transfer management software. 6 COVIANT SOFTWARE

8 STEP 10: MONITOR FILE TRANSFERS Monitor file transfer jobs to rapidly identify potential security problems. Automating file transfer jobs does not guarantee that no issues will arise at run-time. Your file transfer solution needs to provide real-time. A job not running on schedule or taking too long to complete may signal a security problem. When a file transfer job fails, the support person responsible for the job needs to be alerted as soon as possible. and/or paging notifications need to be sent, including the (e.g., log entries) needed to diagnose and correct the problem. If a security breach occurs unrelated to a file transfer (e.g., an FTP server or encryption key has been compromised), the specific file transfer jobs affected may need to be suspended until the security breach has been corrected. Creating a secure file transfer process does not always guarantee that all regulations and standards will be met. MEETING HIPAA/HITECH 3. REGULATIONS Creating a secure file transfer process does not always guarantee that all regulations and standards will be met. HIPAA is intended to protect the privacy and security of data. HIPAA/HITECH cover a wide range of technical safeguards. Only some of which are pertinent when designing and implementing a managed file transfer solution. The following figure identifies the portions of HIPAA that affect file transfer security and how the 10 Steps to Managed File Transfer can meet those mandates. MANAGED FILE TRANSFER: 10 STEPS TO HIPAA/HITECH COMPLIANCE 7

9 FIG. 2 HIPAA TECHNICAL SAFEGUARDS (a)(1) Access Control (a)(2)(i) Unique User Identification (a)(2)(iii) Automatic Logoff (a)(2)(iv) Encryption And Decryption (b)(1) Audit Controls (c)(1) Integrity (c)(2) Authenticate Electronic Protected Health Information (d) Person or Entity Authentication (e)(1) Transmissio n Security (e)(2)(i) Integrity Controls (e)(2)(ii) Encryption 10 STEPS TO SECURE FILE TRANSFER IMPLEMENTATION 1. Secure configuration 2. Control access 3. Automate transfers 4. Authenticate users/ processes 5. Encrypt files 6. Sign and verify files 7. Use secure protocols 8. Archive encrypted files 9. Capture audit data 10. Monitor file transfers Allow access only to those persons or software programs that have been granted access rights. Assign a unique name and/or number for identifying and tracking user identity. procedures that terminate an session after a predetermined time of inactivity. a mechanism to encrypt and decrypt. hardware, software, and/or procedural mechanisms that record and examine activity in systems that contain or use. Property that data or have not been altered or destroyed in an unauthorized manner. mechanisms to corroborate that has not been altered or destroyed in an unauthorized manner. procedures to verify that a person or entity seeking access to is the one claimed. technical security measures to guard against unauthorized access to that is being transmitted over an communications network. security measures to ensure that ally transmitted is not improperly modified without detection until disposed of. a mechanism to encrypt whenever deemed appropriate. The Health Insurance Portability and Accountability Act of 1996 established national standards for the security of care with both civil and criminal penalties for non-compliance by covered entitles, such as hospitals or physician practices. The HITECH Act of 2009 extended these penalties beyond covered entities to their business associates and established more rigorous enforcement policies. The HIPAA Security Rule in defines the technical safeguards required to protect and control access to patient data. FIG. 2. above identifies the relevant security standards in HIPAA and the related specifications that are necessary to protect data-in-motion. You can finds out more about HIPAA technical safegaurds at 8 COVIANT SOFTWARE

10 4.SUMMARY Both security and compliance are essential to smooth operations and business continuity. Developing a Managed File Transfer implementation can also meet the key objectives that are critical for compliance with industry mandates, such as HIPAA/HITECH. Focus on 10 PRACTICAL STEPS to meet your security and compliance needs: STEP 1: Secure configuration STEP 2: Control access STEP 3: Automate transfers STEP 4: Authenticate users and processes STEP 5: Encrypt files STEP 6: Sign and verify files STEP 7: Use secure protocols STEP 8: Archive encrypted files STEP 9: Capture audit data STEP 10: Monitor file transfers Coviant Software offers Diplomat Transaction Manager, a suite of Managed File Transfer products that secure data in transit and improve compliance with HIPAA requirements.

11 ABOUT COVIANT SOFTWARE Coviant Software delivers Managed File Transfer solutions to improve the productivity of file transfer administrators. Diplomat Managed File Transfer software uses Intelligent File Transfer design with embedded secure file transfer logic, so file transfer experts can quickly design and deploy file transfer jobs with fewer errors and failed transfers. For more or to download trial software, visit or us at T / F / Coviant Software. All rights reserved. Coviant and Diplomat are registered trademarks of Coviant Software Corporation. All other company and product names are trademarks or registered trademarks of their respective owners.