1、Designation:E259507(Reapproved 2013)An American National StandardStandard Guide forPrivilege Management Infrastructure1This standard is issued under the fixed designation E2595;the number immediately following the designation indicates the year oforiginal adoption or,in the case of revision,the year
2、 of last revision.A number in parentheses indicates the year of last reapproval.Asuperscript epsilon()indicates an editorial change since the last revision or reapproval.INTRODUCTIONThis guide arises from the ongoing development and implementation of privilege managementinfrastructures(PMIs)within t
3、he healthcare environment.The healthcare environment supported bythis guide is enterprise-wide and extends beyond traditional borders to include external providers,suppliers,and other healthcare partners.This guide supports privilege management within distributedcomputing as well as service-oriented
4、 architecture environments.This guide supports a distributedsecurity environment in which security is also a distributed service.The healthcare sector is continually improving the delivery of care by leveraging technical advancesin computer-based applications.Health professionals are increasingly ac
5、cessing multiple applicationsto schedule,diagnose,and administer patient care.These disparate applications are typicallyconnected to a common network infrastructure that typically supports patient,business,andnonbusiness services,communications,and protocols.Because increased access is made possible
6、through a common network infrastructure,secure access to these distributed,and often looselycoupled applications,is even more important than when these applications were accessed asstand-alone devices.Secure access to legacy computer-based healthcare applications typically involves authentication of
7、the user to the application using single-factor identification,such as a password,or multifactoridentification,such as a password combined with a token or biometric devices.After authentication,the application determines the authority that user may have to use aspects of the application.Determining
8、the level of authority a user has is typically done,if at all,by each application.Theapplication may restrict operations(such as read,write,modify,or delete)to an application-specificgroup or role affiliation.Authenticated users are frequently associated with groups or roles using alocal database or
9、 flat file under the control of an application administrator.The use of a local mechanism for authorization creates a patchwork of approaches difficult toadminister centrally across the breadth of a healthcare enterprise.That is,the software logicdetermining authorization is distinctive to each appl
10、ication.In some cases,applications can be adaptedto use a network database that contains a trusted source of name-value pairs.This information allowsapplications to determine the users group or role affiliation.This approach permits centralized controlover a shared user base.However,the resulting gr
11、anularity of control over user authorization is coarseand shall be interpreted by each application specialist.Granularity of user authority can only beimproved by increasing the number of application-specific groups or roles in the shared database.Storing information specific to each application cau
12、ses exponential growth of roles per user and resultsin provisioning difficulties.The better solution is to associate industry standard permissions to users.Each application can examine the permissions listed for a user and determine their level ofauthorization regardless of their group affiliation w
13、ithin the healthcare organization.The resulting system is a PMI.By the nature of the problem,the privileges shall be defined in anindustry standard way.This guide will discuss various aspects of identifying a PMI standard tovendors providing healthcare applications to the contemporary healthcare ent
14、erprise.1.Scope1.1 This guide defines interoperable mechanisms to manageprivileges in a distributed environment.This guide is orientedtowards support of a distributed or service-oriented architec-ture(SOA)in which security services are themselves distrib-uted and applications are consumers of distri
15、buted services.1.2 This guide incorporates privilege management mecha-nisms alluded to in a number of existing standards(forCopyright ASTM International,100 Barr Harbor Drive,PO Box C700,West Conshohocken,PA 19428-2959.United States1 example,Guide E1986 and Specification E2084).The privilegemechanis
16、ms in this guide support policy-based access control(including role-,entity-,and contextual-based access control)including the application of policy constraints,patient-requested restrictions,and delegation.Finally,this guide sup-ports hierarchical,enterprise-wide privilege management.1.3 The mechanisms defined in this guide may be used tosupport a privilege management infrastructure(PMI)usingexisting public key infrastructure(PKI)technology.1.4 This guide does not specifically support mechanism
