Securing OpenEMR

Securing OpenEMR

Overview

With the advent of the Patient Portals, the community is now addressing the issues of how to best secure OpenEMR instances that are open to the web. Doing this requires a firm understanding of securing several parts, which at least include OpenEMR itself, Apache, MySQL, firewall, router, https, certficates, etc. A forum that began to discuss this issue can be found here. Note this document is just a work in progress; hopefully as members of the community began securing their OpenEMR instances for the web, they will place things they learned here in order to help others.

OpenEMR

• After installation/upgrade consider removing(or ensuring no access to) to the following scripts, which are not needed for general OpenEMR use:

• library/sqlconf.php
• acl_setup.php
• acl_upgrade.php
• sl_convert.php
• setup.php
• sql_upgrade.php
• gacl/setup.php
• ippf_upgrade.php
• admin.php
• entire contrib directory

• After installing a patch consider removing (or ensuring no access to) to the following scripts, which is not needed for general OpenEMR use:

• sql_patch.php

Network

• On server, consider only opening port 443 (https).
• Consider a firewall that only allows port 443 (https) traffic to the server.

Apache

• General hardening of Apache, which is described here.
• Do not allow direct web access to the directories at site/*/documents , site/*/era, site/*/edi
• If not using portal and want to allow users to access over the internet, then consider using client-sided certificates to only allow users access to site
• If want to give access to the patient portals over the internet, then consider using a client-sided certificate to only allow users access to the main OpenEMR login page
• If using third party patient portal, then consider:

• Only allowing the IP address of the third party portal access to the SOAP APIs (for patient access)