Difference between revisions of "Securing OpenEMR"
From OpenEMR Project Wiki
Bradymiller (talk | contribs) |
Bradymiller (talk | contribs) |
||
| Line 4: | Line 4: | ||
==OpenEMR== | ==OpenEMR== | ||
:After installation/upgrade consider removing(or | :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 | ::*library/sqlconf.php | ||
::*acl_setup.php | ::*acl_setup.php | ||
| Line 15: | Line 15: | ||
::*admin.php | ::*admin.php | ||
::*entire contrib directory | ::*entire contrib directory | ||
:After a patch consider removing(or | :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 | ::*sql_patch.php | ||
Revision as of 20:23, 22 October 2011
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
