ECMA 219-1996 Authentication and Privilege Attribute Security Application with related key distribution functions - Part 1 Overview and Functional Model - Part 2 Security Informati.pdf

1、Standard ECMA-2192nd edition - March 1996Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chAuthentication and PrivilegeAttribute Security Applicationwith related key distributionfunctionsStandard ECM

2、A-2192nd edition - March 1996Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chGino Lauri - ECMA-219.DOC - 20/03/96 15:14Authentication and PrivilegeAttribute Security Applicationwith related key dis

3、tributionfunctionsPart 1: Overview and Functional ModelPart 2: Security Information ObjectsPart 3: Service DefinitionsBrief HistoryECMA, ISO and ITU-T are working on standards for distributed applications in an open system environment. Security ingeneral and authentication and distributed access con

4、trol in particular are major concerns in information processing.In July 1988, ECMA TR/46, “Security in Open Systems - A Security Framework“, was published. In December 1989, based onthe concepts of this framework, Standard ECMA-138, “Security in Open Systems - Data Elements and Service Definitions“,

5、was produced. It defines a set of Security Services for use in the Application Layer of the ISO OSI Reference Model. Some ofthese services have been expanded and are incorporated in the present work, though the definitions of the data elements inECMA-138 have been superseded by this document, and wi

6、th its publication, ECMA-138 is now withdrawn.This Standard ECMA-219 describes a model for distributed authentication and access control in which a trusted third party (the“Authentication and Privilege Attribute Application with Related Key Distribution Functions“ of this Standard) is used toauthent

7、icate human and software entities, provide them with the privileges they need for access control purposes and providethe means of protection of these privileges in interchange. The Standard covers bilateral peer-to-peer authentication, but only inconjunction with key distribution functions.It define

8、s the security information objects and services that allow Open Systems to interchange authentication information andaccess control information. The services defined in this document are independent of any particular security policy.This ECMA Standard is divided in three parts Part 1 provides an ove

9、rview of the Standard, its purpose and content, the functional model that underlies the Standard andits relationships to other standards. In addition, it provides all references for all parts of the Standard. Part 2 defines the major Security Information Objects used in the APA-Application. Part 3 p

10、rovides the Service Definitions of the APA-Application. It contains the abstract model, common arguments,common operations and definitions of the Authentication Port and the Privilege Attribute Port.This ECMA Standard is based on the practical experience of ECMA member Companies. It is oriented towa

11、rds urgent and wellunderstood needs.This ECMA Standard has been adopted by the ECMA General Assembly in March 1995.- i -Table of contentsPart 1 - Overview and functional model 11 Introduction 11.1 Scope 11.2 Field of application 11.3 Requirements to be satisfied 21.3.1 Background 21.3.2 Specific Req

12、uirements 21.4 Conformance 31.5 Overview and document structure 31.5.1 Overview of approach taken 31.5.2 Document Structure 52 References 52.1 Normative references 52.2 Informative references 63 Definitions and conventions 63.1 Imported definitions 63.2 New definitions 73.2.1 Access Identity 73.2.2

13、Attribute Set Reference 73.2.3 Attribute Authority 73.2.4 Audit Identity 73.2.5 Authenticated Identity 73.2.6 Authentication Level 73.2.7 Authentication Method Identifier 73.2.8 Basic key 73.2.9 Certificate 73.2.10 Charging Identifier 73.2.11 Client Key Block 73.2.12 Delegate Qualifier Attribute 83.

14、2.13 Delegate/Target Qualifier Attribute 83.2.14 Dialogue key 83.2.15 Initiator Qualifier Attribute 83.2.16 Logon Name 83.2.17 Non-repudiation Identity 83.2.18 Primary Principal 83.2.19 Primary Principal Qualifier Attribute 83.2.20 Principal Privileges 83.2.21 Privileges Attribute Certificate (PAC)

15、83.2.22 Security Authority 83.2.23 Secondary Principal 8- ii -3.2.24 Stateful Server 83.2.25 Stateless Server 83.2.26 Target AEF 93.2.27 Target Key Block 93.2.28 Target Qualifier Attribute 93.3 Conventions 93.4 Acronyms 94 Functional model 94.1 Environment 94.1.1 Proxy 104.2 Role of the APA-Applicat

16、ion 114.3 Functional model of the APA-Application 114.3.1 The APA-Application and APA-Clients 114.3.2 APA Abstract Model 144.3.3 Relationship between the APA-Application and other Applications. 144.4 Services provided by the APA-Application 164.4.1 Summary of Services 164.4.2 Configuration options 1

17、74.4.3 Distributed working 194.4.4 Modes of operation 204.4.5 Use of cryptographic features in clients 224.4.6 Certificate Controls 234.4.7 Certificate revocation 234.4.8 Walk-throughs 234.5 Data elements 294.5.1 Authentication Certificate (AUC) 304.5.2 Privilege Attribute Certificate (PAC) 304.5.3

18、Certificate Control Value 314.5.4 Keying Information 314.6 Authentication methods 324.7 Management and recovery of the APA-Application 335. Relationship to other Standards and Technical Report 335.1 Relationship to ECMA TR/46, “Security in Open Systems: A Security Framework“ 335.2 Relationship to St

19、andard ISO 7498-2, “Security Architecture“ 335.3 Relationship to Standard ISO/IEC 10181-2, “Authentication Framework“ 335.4 Relationship to Standard ISO/IEC 9594: 1990 Part 8, “Directory AuthenticationFramework“ 335.5 Relationship to Standard ISO/IEC 10181-3, “Access Control Framework“ 335.6 Relatio

20、nship to ISO/IEC 10164, “Standards for Systems Management“ 345.6.1 Managed Objects 345.6.2 Management operations on Managed Objects 345.6.3 Security management functions 35Annex A (Informative) Changes from the first edition (December 1994) 37- iii -Part 2 - Security information objects 391 Introduc

21、tion 392 Overview 393 GeneralisedCertificate 403.1 Common Contents fields 403.2 Specific Certificate Contents 423.3 Check value 423.4 Certificate Identity 444 Security attributes 445 Authentication Certificate (AUC) 456 Privilege Attribute Certificate (PAC) 467 Protection methods 487.1 “Control/Prot

22、ection Values“ protection method 497.2 “Primary Principal Qualification“ protection method 507.3 “Target Qualification“ protection method 507.4 “Delegate/Target Qualification“ protection method 517.5 “Delegate Qualification“ protection method 517.6 “Trace Pointer“ protection method 517.7 “Initiator

23、Qualification“ protection method 527.8 “Count“ protection method 527.9 “Check Back“ protection method 527.10 “Nested Chain“ protection method 537.11 Combining the methods 548 Generalised User Certificate (GUC) 549 External control values construct 5510 Specification of Keying Information 5510.1 Conf

24、igurations Supported 5610.2 General Description 5710.2.1 Keying Information Syntax 5810.3 Example walkthroughs of key exchanges 6010.3.1 Notation 6010.3.2 Example 1 6010.3.3 Example 2 6111 DialogueKeyBlock 62Annex A (Normative) Use of identities in the APA-Application 65- iv -Annex B (Normative) Sum

25、mary of ASN.1 (alphabetical order) 67Annex C (Informative) Changes from the first edition (December 1994) 75Part 3 - Service definitions 771 Introduction 772 APA abstract model 772.1 The APA-Application 772.1.1 APA ports 793 Specification of bind and unbind operations 823.1 A-bind 823.2 A-unbind 833

26、.3 PA-bind 833.4 PA-unbind 843.5 KD-bind 843.6 KD-unbind 854 Common atomic operations 854.1 Open Security Association (OpenSA) 854.2 DeclareOperationContext 874.3 Get Keying Information (GetKI) 894.4 Process Keying Information (ProcessKI) 914.5 Close Security Association (CloseSA) 924.6 RevokeCertif

27、icate 934.7 Abstract errors arising from common operations 954.7.1 AssocAlreadyOpen 954.7.2 AUCSpecificError 964.7.3 CertificateError 964.7.4 CertificateTypeNotSupported 984.7.5 ConstructTypesNotSupported 984.7.6 InitiatorKDSUnknown 984.7.7 InitiatorUnknown 984.7.8 InsufficientAuthorisation 984.7.9

28、InvalidAttributeRequirements 984.7.10 InvalidCondition 984.7.11 InvalidDialogueKeyBlock 994.7.12 InvalidKeyBlock 994.7.13 KdSchemeNotSupported 994.7.14 KiTypeNotSupported 994.7.15 OperationNotSupported 1004.7.16 PACSpecificError 1004.7.17 SAfailure 1014.7.18 TargetUnknown 101- v -4.7.19 TimingFailur

29、e 1014.7.20 TrustInformationFailure 1014.7.21 Unspecified 1015 Authentication Port atomic operations 1025.1 Authenticate 1025.2 ContinueAuthentication 1065.3 ChangePassword 1075.4 ContinueChangePassword 1095.5 Check Authentication Certificate (CheckAUC) 1095.6 ConfirmPresence 1115.7 Get Authenticati

30、on Server Name (GetASName) 1125.8 Get Authentication Ticket (GetAT) 1135.9 Abstract errors arising from A-Port operations 1155.9.1 AUCSpecificError 1155.9.2 CertificateError 1155.9.3 InsufficientAuthorisation 1155.9.4 InvalidAuthentication method 1155.9.5 InvalidChoice 1155.9.6 InvalidExchangeId 115

31、5.9.7 InvalidNewPassword 1155.9.8 InvalidOldPassword 1165.9.9 InvalidServiceRequested 1165.9.10 OperationNotSupported 1165.9.11 PACSpecificError 1165.9.12 UnacceptableLogonName 1165.9.13 UnacceptableTicketRequirements 1165.9.14 Unspecified 1176 Privilege Attribute Port atomic operations 1176.1 Get A

32、ccess Control Ticket (GetACT) 1176.2 Check Privilege Attribute Certificate (CheckPAC) 1196.3 Refine Privilege Attribute Certificate (RefinePAC) 1206.4 Abstract errors arising from PA-Port operations 1216.4.1 AUCSpecificError 1216.4.2 CertificateError 1216.4.3 InsufficientAuthorisation 1216.4.4 Opera

33、tionNotSupported 1216.4.5 PACSpecificError 1216.4.6 UnacceptableAttributeRequirements 1216.4.7 UnacceptableRestrictionRequirements 1226.4.8 UnacceptableTicketRequirements 1226.4.9 Unspecified 1227 Key Distribution Port atomic operations 122- vi -8 Combined operations 1228.1 Authentication port combi

34、ned operations 1238.2 Privilege Attribute port combined operations 1248.3 Key Distribution port combined operations 124Annex A (Informative) Information Model 125Annex B (Informative) Authentication Information Types 129Annex C (Normative) ASN.1 - Object Identifier Usage 133Annex D (Normative) ASN.1

35、 - Object Identifiers 135Annex E (Normative) ASN.1 - Abstract Service 137Annex F (Informative) ASN.1 - Authentication Methods 157Annex G (Informative) Changes from first edition (December 1994) 159Part 1 - Overview and functional model1 Introduction1.1 ScopeThis Standard ECMA-219 defines three appli

36、cations: an Authentication Application, a Privilege Attributes Application, a Key Distribution Application.These are distributed Security Applications that provide services concerned with authentication and access control,along with related key distribution information. This definition includes: dat

37、a elements for authentication and access control purposes, services for the authentication of human users of computer based systems as well as other active entities, services for the provision of Privilege Attributes for purposes of access control in distributed open systems, the means of protecting

38、 authentication information and Privilege Attributes in interchange between opensystems, key distribution information for establishing the keys used in this protection,The last two of these facilities requires that the above applications support a Key Distribution Service, which caneither be provide

39、d integrally, or as a separate application.In the interest of providing interoperability between different security systems, the service interfaces are definedsuch that security information objects not specified in this ECMA Standard but specified elsewhere can beincorporated. One example of such a

40、security system is Kerberos from MIT.Specification of security policies supporting real-world requirements is outside the scope of this ECMA Standard. Itsupports, however, a wide variety of such policies. For example identity based, capability based and label basedaccess control schemes.It is not wi

41、thin the scope of this ECMA Standard to specify subsets (profiles) for implementation andinteroperability purposes.There may be several APA-Applications within a security domain representing different authorities. The interchangeof authentication information and Privilege Attributes across security

42、domain boundaries may require an Inter-domain Application, which is for further study.1.2 Field of applicationThe field of application of this ECMA Standard is the design and implementation of distributed open systems thatsupport authentication of human users and software entities, and support secur

43、e access of users to applications andsecure access between distributed applications. Authenticatable users and applications are known as principals.This ECMA Standard also defines operations which permit clients to obtain cryptographic Keying Informationwhich can be used to secure communications and

44、 provide bilateral peer-to-peer authentication.This ECMA Standard does not define how security data elements are embedded into access protocols defined byother (application) standards (e.g. to support setting up secure associations between clients and servers). However,guidance is provided on how st

45、andards developers should make use of the data elements defined in this ECMAStandard.From an Open Systems viewpoint, the instances of the APA-Applications are Application Entities that are accessedby other Application Entities, the APA-Clients. The APA-Application protocol is implemented by a number

46、 ofApplication Service Elements (ASEs). These ASEs may be combined with other ASEs for other applications (e.g.ACSE, ROSE, Directory, Security Exchange ASE) as required by a given application context. Coordinationbetween the actions of the APA-ASEs and other ASEs is provided by the Single and Multip

47、le Association ControlFacilities defined by the OSI Architecture.- 2 -The Standard assumes a connection oriented way of working, i.e. the APA-Application is assumed to maintaincommunications state information. No such requirement is made for security state information however; both“stateful“ and sta

48、teless ways of working are supported.From the viewpoint of the general model of “Security Association Management and Support (SAMS)“ as defined inISO SAMS, the services provided by the A-, PA- and KD-Applications are all realisations of Security SupportServices. The ISO Security Support Service Abst

49、ract Interfaces are provided by the service interfaces defined inpart 3.1.3 Requirements to be satisfied1.3.1 BackgroundThis Standard is based on two general requirements that have been considered important: flexibility and ease ofmanagement. Flexibility is required in order to support a wide variety of security policies and to allowextensibility. Good security is possible only if it is easily managed, and monitored.Different authentication methods must be supported. The need for management and control of the logon process,including keeping state information relating to th