Security Risk Assessment Cookbook: Incorporating Security in HL7 Standards. HL7 Security Working Group John Moehrke Diana Proud-Madruga. Agenda. Introduce the Security Risk Assessment Cookbook Process Break Apply the Process to Student Provided Sample Standard Wrap up and Questions. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
To quantify risk, experts use the calculation of level of threat (probability of event) to the level of vulnerability, often stated as:
Threat x Vulnerability = Risk.
• Point A: A significant vulnerability with little or no threat = low to medium risk. • Point B: A high threat with little or no vulnerabilities tied to the threat = Low to medium risk. • Point C: A high threat with a credible vulnerability = high risk.
Risk is “The potential that a given threat will exploit vulnerabilities of an asset or group of assets and thereby cause harm to the organization.”
The risk is that the building and equipment in the building could be damaged as long as the vulnerability exists and there is a likely chance that rain will fall.
Step 2 – Assess Level of ImpactImpact Reputation NIST 800-30 Legislative and
regulatory compliance
Very HighPotential for reduction in WG or TC mandate
Potential for policy or rulings against HL7 due to non-compliance with Privacy and security regulations
High
Serious adverse attention from media, medical establishment and / or public attention to HL7
Exercise of the vulnerability (1) may result in the highly costly loss of major tangible assets or resources; (2) may significantly violate, harm, or impede an organization’s mission, reputation, or interest; or (3) may result in human death or serious injury.
Potential for major fines or financial loss due to non-compliance with Privacy and Security regulations.
Medium
Minor adverse attention from media, medical establishment and / or public to HL7 or to standard
Exercise of the vulnerability (1) may result in the costly loss of tangible assets or resources; (2) may violate, harm, or impede an organization’s mission, reputation, or interest; or (3) may result in human injury
Potential for non-compliance with Privacy and Security regulations
LowLoss of reputation among clients / partners
Exercise of the vulnerability (1) may result in the loss of some tangible assets or resources or (2) may noticeably affect an organization’s mission, reputation, or interest.
Privacy and Security regulations in some countries may conflict with one or two elements in the standard
Example:Car insurance with a high deductible is an
example of partial transference and partial acceptance. In the case of an accident, expenses below the $1000 deductible need to be accepted. Any expenses above $1000 are covered by insurance, thus the risk is transferred to the insurance company. An example of mitigation would be performing regular car maintenance to reduce the risk of having an accident that is caused by mechanical failure.
Review Security Risk Assessment for HL7 Standards document: When the standard is updated Concerns are voiced Technology changes To determine impact of mitigation strategies
Use Comments section to record effect of mitigation strategy
Place a “Security Considerations” section in the standard Description of scope and assumptions Description of mandatory/optional mitigations Description of unmitigated risks for implementers to
know about
Keep Security Risk Assessment for HL7 Standards document in committee knowledgebase
Wiki Site: “Cookbook for Security Considerations” •http://wiki.hl7.org/index.php?title=Cookbook_for_Security_Considerations
•HL7 gForge folder with other resources •Tutorial Presentation on the Security Risk Assessment Cookbook•Formal Security Cookbook Paper•Template Spreadsheet for Risk Assessment•IHE Equivalent Process