Security Considerations

From IHE Wiki
Revision as of 17:22, 12 February 2010 by JohnMoehrke (talk | contribs) (New page: This text taken from the formal White paper. All new IHE Profiles are required to have a Security Considerations section. This section communic...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This text taken from the formal White paper.

All new IHE Profiles are required to have a Security Considerations section. This section communicates security concerns that the implementers need to be aware of, assumptions made about security pre-conditions and, where appropriate, key elements of a risk mitigation strategy to be applied. Historically, IHE Profiles have not addressed security considerations and thus implementers have had no direction. This document helps IHE Profile writers complete the Security Considerations section of their IHE Profile.

1.1 The Security Considerations section of an IHE Profile is intended to help implementers make a security assessment of their product / information system in relation to implementing an actor in that profile. It is not a thorough standalone security assessment. The Security Considerations section of an IHE Profile should only deal with issues specifically relevant to the interoperability provided by the profile and not try to encompass every security aspect of the use cases identified in the Profile in Volume 1.

Profile/Supplement editors see Cookbook for Security Considerations