Difference between revisions of "Cookbook for Security Considerations"
JohnMoehrke (talk | contribs) |
JohnMoehrke (talk | contribs) |
||
| Line 7: | Line 7: | ||
= The Process = | = The Process = | ||
| − | Formal Process should be followed. See the References below | + | Formal Process should be followed. See the References below (This text comes from section 2) |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | When considering security and privacy issues associated with a standard, one must: | ||
| + | # Identify (See section 2.2) | ||
| + | ## And clearly define the scope of the standard, including the baseline assumptions | ||
| + | ## New threat scenarios and describe the type of impact that scenario implies | ||
| + | # Analyze (See section 2.3) | ||
| + | ## The level of impact and likelihood of occurrence for each threat scenario to determine risk | ||
| + | ## Prioritize these risks in order to focus on the most important ones | ||
| + | # Plan (See section 2.4) | ||
| + | ## Determine mitigation strategies that should be implemented for all medium to high risk threat scenarios | ||
| + | # Track (See section 2.5) | ||
| + | ## Assess the effect of the application of the mitigation strategies | ||
| + | ## Reassess the risks by going through steps 2 and 3 until all medium and high risk threat scenarios have been addressed | ||
| + | # Document all security considerations (See section 2.6) | ||
Do NOT use [http://www.crypto.com/bingo/pr this tool] :-) | Do NOT use [http://www.crypto.com/bingo/pr this tool] :-) | ||
Revision as of 04:36, 16 February 2010
As not all HL7 standards writers are security experts, this cookbook is intended to provide basic knowledge on conducting a risk assessment and some “tricks of the trade” relevant to Security Considerations section writing. It is not only based on best practice in the field of risk assessment and mitigation but also on the experience of the Security Workgroup while compiling the Security Considerations section for new HL7 works.
This cookbook is specifically intended for HL7 standards writers. Though it is based on best practice, it is not a complete method for thorough risk assessment of a package product. HL7 does not endorse any use of this cookbook outside of the scope of HL7 standards editing.
After presenting the basics of risk assessment and risk mitigation, the cookbook explains how to scope Security Considerations for HL7 standards and finally provides guidelines on the effective writing of the Security Considerations section.
The Process
Formal Process should be followed. See the References below (This text comes from section 2)
When considering security and privacy issues associated with a standard, one must:
- Identify (See section 2.2)
- And clearly define the scope of the standard, including the baseline assumptions
- New threat scenarios and describe the type of impact that scenario implies
- Analyze (See section 2.3)
- The level of impact and likelihood of occurrence for each threat scenario to determine risk
- Prioritize these risks in order to focus on the most important ones
- Plan (See section 2.4)
- Determine mitigation strategies that should be implemented for all medium to high risk threat scenarios
- Track (See section 2.5)
- Assess the effect of the application of the mitigation strategies
- Reassess the risks by going through steps 2 and 3 until all medium and high risk threat scenarios have been addressed
- Document all security considerations (See section 2.6)
Do NOT use this tool :-)
Resources
- HL7 gForge folder with resources http://gforge.hl7.org/gf/project/security/docman/?subdir=144
- Tutorial Presentation on the Security Risk Assessment Cookbook Version 7.4
- Formal Security Cookbook Paper Version 2.4
- Template Spreadsheet for Risk Assessment Version 1
Examples of Risk Assessment Spreadsheets
- SAML use in CCOW -- spreadsheet not yet published
- CDA-Consent -- spreadsheet not yet published
