GB/T 17143.8-1997 Information technology Open Systems Interconnection System management Part 8: Security audit trail function
Some standard content:
GB/T17143.8--1997
This standard is equivalent to ISO/IEC10164-8:1993 "Information Technology Open Systems Interconnection System Management: Security Audit Trail Function" and ISO/IEC10164-8:1993/Cor.1:1995 "Information Technology Open Systems Interconnection System Management: Security Audit Trail Function Technical Modification 1".
Based on ISO/IEC10164-8:1993/Cor.1:1995, this standard modifies Chapter 13, Appendix A, Appendix B, Appendix C, Appendix D and Appendix E of ISO/IEC10164-8:1993. GB/T17143, under the general title of "Information Technology Open Systems Interconnection System Management", currently includes the following 8 parts: Part 1 (i.e. GB/T17143.1): Object management function Part 2 (i.e. GB/T17143.2): State management function Part 3 (i.e. GB/T17143.3): Attributes representing relationships Part 4 (i.e. GB/T17143.4): Alarm reporting function Part 5 (i.e. GB/T17143.5): Event report management function Part 6 (i.e. GB/T17143.6): Log control function Part 7 (i.e. GB/T17143.7): Security alarm reporting function Part 8 (i.e. GB/T17143.8): Security audit tracking function Appendices A, B, C, D and E of this standard are appendices to the standard. Appendix F of this standard is a prompt appendix. This standard is proposed by the Ministry of Electronics Industry of the People's Republic of China. This standard is under the jurisdiction of the Standardization Research Institute of the Ministry of Electronics Industry. This standard was drafted by the Standardization Research Institute of the Ministry of Electronics Industry. The main drafters of this standard are Zheng Hongren, Zhou Xiaohua, Zhang Xiaotao and Huang Jiaying. 292
GB/T 17143.8-1997
ISO/IEC Foreword
ISO (International Organization for Standardization) and IEC (International Electrotechnical Commission) are specialized standardization organizations worldwide. National member bodies (all of which are members of ISO or IEC) participate in the formulation of international standards for specific technical scopes through various technical committees established by international organizations. The technical committees of ISO and IEC cooperate in areas of common interest. Other official and non-official international organizations in contact with ISO and IEC can also participate in the formulation of international standards. For information technology, ISO and IEC have established a joint technical committee, namely ISO/IECJTC1. The draft international standards proposed by the joint technical committee are circulated to national member bodies for voting. At least 75% of the voting fees of the national member bodies participating in the voting are required to publish an international standard.
International standard ISO/IEC10164-8 was developed by the ISO/IECJTC1\Information technology" Joint Technical Committee in cooperation with CCITT. The equivalent text is CCITT X.740. ISO/IEC10164, under the general title of "Information technology open systems interconnection system management", currently includes the following 14 parts: Part 1: Object management functions
-Part 2, State management functions
Part 3: Attributes representing relationships
-Part 4: Alarm reporting functions
Part 5: Incident report management functions
Part 6: Log control functions
Part 7: Security alarm reporting functions| |tt||Part 8: Security audit trail function
Part 9: Objects and attributes of access control-Part 10: Accounting and metering function
Part 11: Workload monitoring function
Part 12: Test management function
Part 13: Generalization function
Part 14: Reliability and diagnostic test classification Annexes A, B, C, D and E constitute a part of this standard; Annex F is for reference only. 293
GB/T 17143. 8--1997
GB/T17143 is a standard consisting of multiple parts formulated in accordance with GB9387 and GB/T9387.4. GB/T17143 is related to the following standards:
Information Technology Open Systems Interconnection
GB/T 16644
GB/T 17142
GB/T 17175
GB/T 16645
Information technology-Open systems interconnection
Information technology
Open systems interconnection
Information technology
Open systems interconnection
Definition of public management information service
System management overview
Management information structure
Public management information protocol
National standard of the People's Republic of China
Information technology-Open Systems Interconnection -Systems Management-Part 8: Security audit trail function1Scope
GB/T 17143. 8--1997
idtIS0/1EC10164-8:1993
This standard defines the security audit trail function. The security audit trail function is a system management function that provides for application processes to exchange information and commands in a centralized or decentralized management environment for the purpose of system management as defined in GB/T9387.4. This standard is located in the application layer of GB9387 and is defined according to the model provided by GB/T 17176. The role of the system management function is described by GB/T 17142. This standard
establishes user requirements for the definition of services needed to support the security audit trail reporting function; defines the services provided by the security audit trail reporting function, specifies the protocols necessary to provide the services; defines the relationship between services and management notifications, defines the relationship between services and other system management functions; specifies conformance requirements.
This standard
does not define security auditing, nor does it define how to perform security auditing. Security auditing can be used to help evaluate the effectiveness of security policies. The security policy identifies the classification of security-related events that require auditing, as well as the units for recording security audit trail information; - does not define the characteristics of any implementation intended to provide security audit trail functionality; - does not define appropriate occasions for using security audit trail functionality, - does not define the services necessary for establishing, normal release, and abnormal release management connections; and does not define any other notifications defined by other standards that may be of interest to security managers. 2 Referenced standards
The provisions contained in the following standards constitute the provisions of this standard through reference in this standard. At the time of publication of this standard, the versions shown are valid. All standards are subject to revision, and parties using this standard should explore the possibility of using the latest versions of the following standards. GB9387-88 Basic reference model for information processing systems (idtISO7498:1984, eqvCCITT X.200:1988)
GB/T9387.2—1995 Basic reference model for information processing systems (idtISO/IEC 7498-2:1988, eqvCCITT X.800:1991)GB/T 9387.4—1996 Basic reference model for information processing systems (idtISO/IEC 7498-4:1989, eqvCCITT X. 700:1992)GB/T15129-94 Information Processing System Open System Interconnection Service Agreement (idtISO/TR8509,1987,eqvCCITTT X.210:1988)
Approved by the State Administration of Technical Supervision on December 15, 1997 and implemented on August 1, 1998
GB/T 16262--1996
GB/T 17143. 8--1997
Information Technology Open System Interconnection Abstract Syntax Notation One (ASN.1) Specification (idtISO/IEC8824:1990,eqvCCITTT X.208:1988)GB/T16263-1996 Information Technology Open System Interconnection Abstract Syntax Notation One (ASN.1) Basic Encoding Rules Specification (idt ISO/IEC 8825:1990,eqvCCITTT X. 209:1988)GB/T16644-1996 Information technology Open Systems Interconnection Common Management Information Service Definition (idt1ISO/EC9595:1991,eqv CCITT X.710:1991)
GB/T17142-1997 Information technology Open Systems Interconnection System Management Overview (idtISO/IEC10040:1992)GB/T17143.41997 Information technology Open Systems Interconnection System Management Part 4: Alarm reporting function (idtISOIEC 10164-4:1992)
Interruption technology Open Systems Interconnection
GB/T 17143.5-1997
System management: Part 5: Event reporting management function (idtISO/IEC 10164-5:1993)
GB/T 17143. 6---19971
Information technology Open Systems Interconnection
IEC10164-6:1993)
GB/T 17143. 7--1997
Information technology Open Systems Interconnection
ISO/IEC 10164-7:1992)
System management Part 6: Log control function (idtISO/System management Part 7: Security alarm reporting function (idtGB/T 17175. 2---1997
Information technology Open Systems InterconnectionbzxZ.net
Management information structure Part 2: Alarm information definition (idtISO/IEC 10165-2: 1992)
Information technology Open Systems Interconnection Management information structure Part 4: Definition of managed objects GB/T 17175.4--1997
South (idt ISO/IEC 10165-4:1992) Information technology Open Systems Interconnection Application Layer Architecture (idtISO/IEC9545:1994) GB/T 17176-1997
GB/T 17178. .-1997
Information technology Open Systems Interconnection Conformance test methods and framework Part 1: Basic concepts (ISO/IEC 9646-1:1994)
ISO/IEC 9646-2:1991
Information technology Open Systems Interconnection
Conformance test method and framework Part 2: Abstract test suite specification
Conformance test method and framework Part 7: Implementation conformance ISO/IEC96467:1995 Information technology
Open Systems Interconnection
Conformance statement
Information technology Open Systems Interconnection Management information structure Part 6: Requirements and guidelines for implementation conformance proformas related to OSI management ISO/IEC 10165-6:1994
Information technology Open Systems Interconnection Open systems security framework: Security audit and tracking framework 3 Definitions
This standard adopts the following definitions.
3.1 Basic reference model definitions
This standard adopts the following terms defined in GB9387: Open system.
3.2 Security Architecture Definition
This standard adopts the following terms defined in GB/T9387.2: a) Security audit trail;
b) Security policy.
3.3 Management Framework Definition
This standard adopts the following terms defined in GB/T9387.4: Managed object.
3.4 System Management Overview Definitions
GB/T 17143. 8—1997
This standard adopts the following terms defined in GB/T17142: a) Agent role;
b) Managed Object Conformance Statement (MOCS); c) Management Information Conformance Statement (MICS); d) Management domain;
e) Manager role;
f) MICS proforma;
g) MOCS proforma,
h) Notification;
i) System Management Functional Unit.
3.5 Event Report Management Function Definitions
This standard adopts the following terms defined in GB/T17143.1: Identifier.
3.6 Security Alarm Report Definitions
This standard adopts the following terms defined in GB/T17143.7: Security-related events.
3.7 Log Control Definition
This standard adopts the following terms defined in GB/T 17143.6: a) log,
b) log record.
3.8 OSI-Conformance Test Definition
This standard adopts the following terms defined in GB/T17178.1: a) PICS proforma;
b) Protocol Implementation Conformance Statement (PICS) c) System Conformance Statement.
3.9 Implementation Conformance Statement Proforma Definition
This standard adopts the following terms defined in ISO/IEC 10165-6: a) Managed Relationship Conformance Statement (MRCS);
c) Management Information Definition Statement (MIDS) proforma;
d) MCS proforma;
e) MRCS proforma.
4 Abbreviations
Abstract syntax notation~
Common management information service
Implementation-conformance statement
Management application protocol data unit
Management conformance profile
Management information conformance statement
Management information definition statement
5 Conventions
Managed object conformance statement
Managed relationship conformance statement
Open Systems Interconnection
Protocol implementation conformance statement
System management application protocol machine
GB/T 17143.8—1997
This standard defines services for the security audit trail function following the descriptive conventions defined in GB/T15129. In clause 9, the definition of each service includes a table listing the service primitive parameters. For a given service primitive, the presence of each parameter is described by one of the following values:
Parameter is mandatory;
Parameter value is equal to the value of the parameter in the left column;
Use of the parameter is optional for the service user; The parameter is not present in the interaction described by the primitive; The parameter is conditional, the condition is defined by the text describing the parameter; The parameter is subject to mandatory constraints of GB/T16644.
Note: Parameters marked with "P" in Table 1 are directly mapped to the corresponding parameters of the CMIS service primitive without changing the semantics or syntax of the parameter. The remaining parameters are used to construct MAPDUs.
6 Requirements
Security management users need to be able to record security-related events that occur in the management domain in a security audit trail log. The security policy of an open system may require that specific security-related events be sent to a security audit trail log in the same open system or in a different open system. Security-related events that may be subject to security auditing include, but are not limited to: connection, disconnection, security mechanism utilization; administrative operations; usage accounting. Security management users also need the ability to control the operation of the security audit trail function. This standard describes the use of these services and technologies to meet these requirements. 7 Model This standard requires that security-related events be logged according to the procedures defined in ISO 17143.6. The construction of discriminators in the security audit trail log should be specified to allow the capture of incoming events that the security policy requires to be logged. If event reports are to be sent to different destinations, an event forwarding discriminator as defined in ISO 17143.5 should be created and the destination address should be set to send events to the selected system where the security audit trail log is located. The security audit trail log is the log defined in ISO 17143.6. The model for delivering event reports to the system where the security audit trail log is located is defined in ISO 17143.5. The model for creating and retrieving items in the security audit trail log is defined in GB/T 17143.6. 8 Generic definition
8.1 Generic notification
GB/T 17143.8—1997
This standard defines a set of generic security audit trail notifications and their available parameters and semantics. The set of generic notifications, parameters and semantics defined by this standard provides in detail the following parameters of the M-EVENT-REPORT service defined by GB/T 16644:
-Event type;
-Event message;
-Event response.
All notifications are potential items of the system management log. GB/T 17175.2 defines the generic event log from which all items are derived: the record object class, additional information specified by the event message, and the event response parameters. 8.1.1 Event type
This parameter defines the type of security audit trail report. The following event types are defined in this standard:--Service report: indicates an event that falls under the terms of denial or restoration of service. The specific reasons for generating the event are described in 8.1.2;--Usage report: indicates a record containing statistical characteristics information related to security. Other notifications defined in other standards (e.g., GB/T17143.7) may be recorded in the security audit log. Notification types (similar to security audit trail report types) and their associated parameters are defined in appropriate standards. 8.1.2 Event Information
The service report reason parameter constitutes notification-specific event information. This parameter should be provided when the event type specifies a service report and defines further restrictions on the possible causes of the service report. This parameter value, together with the event type value, determines which parameters constitute the service report and what possible values these parameters can be. For notifications, the service report reason value should be indicated in the behavior clause of the object class definition. This standard defines service report reasons that have broad applicability to managed object classes for use in the system management application context defined in GB/T17142. These values are registered in accordance with Appendix A of this standard. The syntax of the service report reason should be an ASN.1 type object identifier. Additional service report reasons may be added to this standard and registered using the registration procedure defined in GB/T 16262 for ASN.1 object identifier values for use in the context of system management applications defined in GB/T 17142. Other service report reasons may be defined outside the scope of this standard and registered using the registration procedure defined in GB/T 16262 for ASN.1 object identifier values for use in the context of system management applications defined in GB/T 17142. The following service report reasons are defined:
-Requested service: This value specifies that a notification has been generated due to a request for service provision;-Rejected service: This value specifies that a notification has been generated due to a request for service being denied;-Service response: This value specifies that a notification has been generated due to a request for service being satisfied;-Service failure: This value specifies that a notification has been generated due to an abnormal condition that caused a service failure to be detected during the provision of the service;-Service recovery: This value specifies that a notification has been generated due to a service having recovered from an abnormal condition;Other reasons: This value specifies that a notification has been generated due to reasons other than those listed above. The actual reason and other relevant information are specified in the other parameters of the report.
8.1.3 Event Response
This standard does not specify the management information used in the parameters of an event response. 8.2 Managed Objects
The Security Audit Trail Record is a managed object class that is derived from the Event Log Record object class defined in ISO 17175.2. The Security Audit Trail Record object class represents the information stored in the log resulting from a Security Audit Trail Notification. 8.3 The generic definition introduced
also uses the following parameters. These parameters are defined by ISO 17143.4: Additional Information;
Additional Text;
-Related Notification;
Notification Identifier.
8.4 Conformance
ISO 17143. 8-1997
The managed object class definition supports the functionality defined in this standard by referencing the notification sample defined in Appendix A, in conjunction with the notification specification. The reference mechanism is defined in ISO 17175.4.
For each instance of a security audit trail report, one or more managed object class definitions for security audit trail notifications defined in this standard are required to be imported in order to select the security audit trail report type that most closely reflects the actual event that caused the managed object to issue the notification. For each imported notification, the managed object class definition shall specify in the characteristics clause which selection parameters and conditional parameters are to be used, the conditions under which they are used, and their values. It is allowed to declare that the use of parameters remains optional. 9 Service definition
9.1 Introduction
Security audit trail notifications provide the ability to report security-related events detected by a managed object. This parameter conveys information related to the security audit trail.
9.2 Security alarm reporting service
The security alarm reporting service uses the parameters defined in clause 8, as well as the general M-EVENT-RE-PORT service parameters defined in ISO 16644. Table 1 lists the parameters of the security audit trail reporting service. Table 1 Security Audit Trail Report Parameters
Parameter Name
Call Identifier
Managed Object Class
Managed Object Instance
Event Type
Event Time
Event Information
Service Report Reason
Notification Identifier
Related Notification
Additional Text
Additional Information
Current Time
Event Response
Req/Ind
Rsp/Conf
The event time, related notification and notification identification parameters may be assigned by the managed object or managed system sending the notification. 10 Functional Unit
The security audit trail function constitutes a single system management functional unit. 11 Protocol
11.1 Procedure elements
11.1.1 Proxy role
11.1.1.1 Invocation
GB/T17143.8—1997
The security audit trail report procedure is initiated by the security audit trail report request primitive. Upon receiving the security audit trail report request primitive, the SMAPM shall construct a MAPDU and issue a CMIS M-EVENT-REPORT request service primitive with parameters from the security audit trail report request primitive. In non-confirmed mode, the procedure in 11.1.1.2 is not used. 11.1.1.2 Receive response
Upon receipt of a CMIS M-EVENT-REPORT confirm service primitive containing a MAPDU in response to the security audit trail report notification, the SMAPM shall issue a security audit trail report confirm primitive with the parameters from the CMIS M-EVENT-REPORTconfirm service primitive to the security audit trail report service user, thereby completing the security audit trail report procedure. NOTE: The SMAPM ignores all errors in the received MAPDU. The security audit trail report service user may ignore these errors or contact the service provider accordingly.
11.1.2 Manager role
11.1.2.1 Receive request
Upon receipt of a CMIS M-EVENT-REPORT indication service primitive containing a MAPDU in response to the security audit trail report service, if the MAPDU is intact, the SMAPM shall issue a security audit trail report indication primitive with the parameters from the CMIS M-EVENT-REPORT indication service primitive to the security audit trail report service user. Otherwise, in confirmed mode, the SMAPM shall construct an appropriate MAPDU containing an error notification and issue a CMISM-EVENT-REPORT response service primitive with the error parameters present. In unconfirmed mode, the procedure in 11.1.2.2 is not used. 11.1.2.2 Response
In confirmed mode, the SMAPM shall receive the security audit trail report response primitive and construct a MAPDU to confirm the notification and issue a CMISM-EVENT-REPORTresPonse service primitive with the parameters from the security audit trail report response primitive.
11.2 Abstract syntax
11.2.1 Managed objects
This standard defines the following supporting objects, whose abstract syntax is specified in GB/T17175.2. securityAuditTrailRecord
11.2.2 Attributes
Table 2 shows the relationship between the parameters defined in 8.1.2 and the attribute type specifications defined in Appendix A. Table 2 Attributes
Service Report Reason
11.2.3 Attribute Group
This system management function does not define an attribute group. 11.2.4 Actions
This system management function does not define specific actions. 11.2.5 Notifications
Attribute Name
serviceReportCause
Table 3 shows the relationship between the notifications defined in 8.1.1 and the notification type specifications defined in Annex A. Table 3 Notifications
Security Audit Trail Type
Service Report
Usage Report
The abstract syntax referenced by the notification type specification is carried in the MAPDU. 11.2.6 Service Report Cause
Notification Type
serviceReport
usageReport
Table 4 shows the relationship between the service report cause defined in 8.1.2 and the ASN.1 value reference defined in Annex A. 301
Service report reason
Service request
Service denial
Service response
Service failure
Service recovery
Other reasons
GB/T 17143.8—1997
Table 4 Service report reason
11.3 Negotiation of security audit trail report functional unit This standard assigns the following object identifier values: ASN.1 value reference
serviceRequest
serviceDenial
serviceResponse
serviceFailure
serviceRecover
otherReason
(joint-iso-ccitt ms(9) function(2) part8(8) functional UnitPackage(1)) as the value of the ASN.1 type FunctionalUnitPackageId defined in ISO/IEC 17142 to negotiate the following functional unit: O security audit trail reporting functional unit The numbers here indicate the bit positions assigned to the functional unit. The name refers to the functional unit defined in clause 10. The mechanism for negotiating the security audit trail reporting functional unit is described by ISO/IEC 17142 within the context of a systems management application. NOTE The requirements for negotiating the functional unit are dictated by the application context. 12 Relationship to other functions
Control of the security audit trail reporting service is provided by the mechanisms specified in ISO/IEC 17143.5. Modification of security audit trail log attributes is provided by ISO/IEC 17143.6.
The security audit trail notification service may exist independently of the control services of ISO/IEC 17143.5 and ISO/IEC 17143.6. 13 Conformance
Implementations claiming conformance to this standard shall comply with the conformance requirements defined in the following clauses. 13.1 Static Conformance
An implementation shall conform to this standard with respect to the manager role, the proxy role, or both. Claims to conform to at least one of the roles shall be made in Table B1.
If a conformance claim is made to support the manager role, the implementation shall support at least one notification or at least one management operation specified in this standard. The conformance requirements for these management operations and notifications for the manager role are identified in Table B3 and further tables referenced in Annex B.
If a conformance claim is made to support the proxy role, the implementation shall support at least one notification specified in this standard. The conformance requirements for the proxy role are identified in Table B4 and further tables referenced in Annex B. The implementation shall support the transfer syntax derived from the encoding rules specified in ISO 16263 entitled (joint-iso-ccitt asn1(1) basic encoding(1)) for the abstract data types referenced by the definitions claimed to support. 13.2 Dynamic Conformance
An implementation claiming conformance to this standard shall support the procedural elements and semantic definitions corresponding to the definitions claimed to support. 13.3 Management Implementation Conformance Claim Requirements
Any MCS proforma, MICS proforma and MOCS proforma conforming to this standard shall be technically identical to the proformas specified in Annexes B, C and D, maintaining table numbering and item indexing, with differences only in page numbering and page headers. A supplier of an implementation claiming conformance to this standard shall complete a copy of the Management Conformance Summary (MCS) provided in Annex B as part of the conformance claim, together with any other ICS proformas referenced as applicable for that MCS. An ICS conforming to this standard shall:
- describe the implementation conforming to this standard, completed in accordance with the instructions given in ISO/IEC 10165-6; include the information necessary to uniquely identify both the supplier and the implementation. Claims of conformance to management information defined in this standard with respect to managed object classes defined elsewhere shall include the MIDS proforma requirements in the MOCS for the managed object classes.1 Static Conformance
An implementation shall conform to this standard with respect to the manager role, the proxy role, or both. Claims to conform to at least one of the roles shall be made in Table B1.
If a conformance claim is made to support the manager role, the implementation shall support at least one notification or at least one management operation specified in this standard. The conformance requirements for these management operations and notifications for the manager role are identified in Table B3 and further tables referenced in Annex B.
If a conformance claim is made to support the proxy role, the implementation shall support at least one notification specified in this standard. The conformance requirements for the proxy role are identified in Table B4 and further tables referenced in Annex B. The implementation shall support the transfer syntax derived from the encoding rules specified in ISO 16263 entitled (joint-iso-ccitt asn1(1) basic encoding(1)) for the abstract data types referenced by the definitions claimed to support. 13.2 Dynamic Conformance
An implementation claiming conformance to this standard shall support the procedural elements and semantic definitions corresponding to the definitions claimed to support. 13.3 Management Implementation Conformance Claim Requirements
Any MCS proforma, MICS proforma and MOCS proforma conforming to this standard shall be technically identical to the proformas specified in Annexes B, C and D, maintaining table numbering and item indexing, with differences only in page numbering and page headers. A supplier of an implementation claiming conformance to this standard shall complete a copy of the Management Conformance Summary (MCS) provided in Annex B as part of the conformance claim, together with any other ICS proformas referenced as applicable for that MCS. An ICS conforming to this standard shall:
- describe the implementation conforming to this standard, completed in accordance with the instructions given in ISO/IEC 10165-6; include the information necessary to uniquely identify both the supplier and the implementation. Claims of conformance to management information defined in this standard with respect to managed object classes defined elsewhere shall include the MIDS proforma requirements in the MOCS for the managed object classes.1 Static Conformance
An implementation shall conform to this standard with respect to the manager role, the proxy role, or both. Claims to conform to at least one of the roles shall be made in Table B1.
If a conformance claim is made to support the manager role, the implementation shall support at least one notification or at least one management operation specified in this standard. The conformance requirements for these management operations and notifications for the manager role are identified in Table B3 and further tables referenced in Annex B.
If a conformance claim is made to support the proxy role, the implementation shall support at least one notification specified in this standard. The conformance requirements for the proxy role are identified in Table B4 and further tables referenced in Annex B. The implementation shall support the transfer syntax derived from the encoding rules specified in ISO 16263 entitled (joint-iso-ccitt asn1(1) basic encoding(1)) for the abstract data types referenced by the definitions claimed to support. 13.2 Dynamic Conformance
An implementation claiming conformance to this standard shall support the procedural elements and semantic definitions corresponding to the definitions claimed to support. 13.3 Management Implementation Conformance Claim Requirements
Any MCS proforma, MICS proforma and MOCS proforma conforming to this standard shall be technically identical to the proformas specified in Annexes B, C and D, maintaining table numbering and item indexing, with differences only in page numbering and page headers. A supplier of an implementation claiming conformance to this standard shall complete a copy of the Management Conformance Summary (MCS) provided in Annex B as part of the conformance claim, together with any other ICS proformas referenced as applicable for that MCS. An ICS conforming to this standard shall:
- describe the implementation conforming to this standard, completed in accordance with the instructions given in ISO/IEC 10165-6; include the information necessary to uniquely identify both the supplier and the implementation. Claims of conformance to management information defined in this standard with respect to managed object classes defined elsewhere shall include the MIDS proforma requirements in the MOCS for the managed object classes.
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.