OpenMRS seeks seeks to be a reliable and trusted application. However, we also recognize that security incidents can (and do) still happen, and so it's just as important to have effective methods for handling them should they arise.
A security vulnerabilities group currently exists on OpenMRS talk. Membership is by invitation only and is open to existing members of the OpenMRS community working on security issues.
However, Anyone can send in reports via email to firstname.lastname@example.org.
The designated mechanism through which security incidents are reported is via email on email@example.com. Details of the incident are shared on the Security Vulnerabilities Group message message board for discussion.
Assessment of Incident :
|Severity Level||Characteristic||Time to resolve (Days)|
For critical vulnerabilities, it is advised that you patch or upgrade as soon as possible , unless you have other mitigating measures in place. For example, a mitigating factor could be if your installation is not accessible from the Internet.
|Low||Vulnerabilities in the low range typically have very little impact on an organization's business. Exploitation The exploitation of such vulnerabilities usually requires local or physical system access.||1 Year|
Routine security updates will be highlighted in the release notes for each release. If a vulnerability is a critical one (e.g something submitted by an external body), members will receive an email to that effect
Containment, eradication, and recovery
The security vulnerabilities group will determine depending on the level of severity of the incident, agree what corrective measures need to be taken to contain the incident, eradicate the underlying causes and start our recovery processes to ensure that operations return to normal. Thus a summary of activities at this stage would include:
- Upon receipt of incident the security vulnerabilities group is activated: Identify an “Owner,” developer, others on the core team
- Minimum a team of 3-5 people can be assigned to a certain vulnerability group i-e ‘Owner’, ‘developer’ and a ‘tester’,'coordinator' etc.
- Team The team can be formed by a security management team with discussion to OpenMRS management, based upon previous contributions of members in their concerned (security) area.
- Define a plan of action is agreed and executed upon
- We also have access to a range of external experts to assist us with investigating and responding as effectively as possible.
- Work on the fix
- Compliance with the deadlines
- Test and release
- Create an initial draft of the security review and circulate for review
- Deploy to our environments
- Notify the public via OpenMRS Talk
- Vulnerability with its solution and updated fixes be documented properly. (if possible within major other languages also.)
We aim to notify affected community members members within 5 business days or without undue delay if their data is involved in an incident or a breach. This might be light on detail at first, but we’ll provide every detail available , when it is available. These initial communications will be done directly with the affected party as the matter is being resolved, however as soon as the security group deems that it is possible to inform a broader audience, such information will be posted to designated the communication channel which is OpenMRS Talk.
Security Advisory Format
Contains at a minimum:
- Affected versions (including mentioning EOL’d versions)
- Exact steps on how to fix the problem, and any available workarounds (list exact versions)
- Acknowledgements Acknowledgments to people who reported it and fixed it.
- Finder (Discoverer/ Reporter) – the individual or organization that identifies the vulnerability
- External group (i.e: Bishop Fox)
- Internally (i.e:bug bounty/Hackerone)
- Manager - An individual with a role of managing volunerability the vulnerability process till the fixing and its updated release, appointed by the management of OpenMRS.
- Vendor (OpenMRS) – the individual or organization that created or maintains the vulnerable product that is vulnerable
- Deployer – the individual or organization that must deploy a patch or take other remediation action
- Release managers who needs need to include the patch in the ongoing release process
- Coordinator – an individual or organization that facilitates the coordinated response process
- Lead The lead of the Security and Vulnerability Management Group
- Tester -the individual who tests the updated release, its feedback is taken from the Deployer and documents the fixes finally reports report it to the "Owner".
Security Vulnerability “Manager” - Roles and Responsibilities
- Deciding (with the core team) which versions should be released
- Ensuring that a developer is working on the problem on a timely fashion
- Ensuring that a release is done as soon as possible
- Create the initial draft of the security advisory and ask for reviews. Create the CVE if relevant.
- Follow the process to release the security advisory
- Ensure all public OpenMRS community environments are updated.
- Follow up on any discussions or questions about the incident.
- Ensuring the documentation of vulnerabilities and their updated solutions in order to have a review for the next developments.
- Ensuring the proper testing of the Vulnerability fixing by cross-checking by with the pre-volunerability vulnerability state and documenting the final report for future use.