draft-ietf-sacm-information-model-06.txt   draft-ietf-sacm-information-model-07.txt 
SACM D. Waltermire, Ed. SACM D. Waltermire, Ed.
Internet-Draft NIST Internet-Draft NIST
Intended status: Standards Track K. Watson Intended status: Standards Track K. Watson
Expires: January 9, 2017 DHS Expires: March 13, 2017 DHS
C. Kahn C. Kahn
L. Lorenzin L. Lorenzin
Pulse Secure, LLC Pulse Secure, LLC
M. Cokus M. Cokus
D. Haynes D. Haynes
The MITRE Corporation The MITRE Corporation
July 8, 2016 H. Birkholz
Fraunhofer SIT
September 9, 2016
SACM Information Model SACM Information Model
draft-ietf-sacm-information-model-06 draft-ietf-sacm-information-model-07
Abstract Abstract
This document defines the Information Elements that are transported This document defines the Information Elements that are transported
between SACM components and their interconnected relationships. The between SACM components and their interconnected relationships. The
primary purpose of the Secure Automation and Continuous Monitoring primary purpose of the Secure Automation and Continuous Monitoring
(SACM) Information Model is to ensure the interoperability of (SACM) Information Model is to ensure the interoperability of
corresponding SACM data models and addresses the use cases defined by corresponding SACM data models and addresses the use cases defined by
SACM. The Information Elements and corresponding types are SACM. The Information Elements and corresponding types are
maintained as the IANA "SACM Information Elements" registry. maintained as the IANA "SACM Information Elements" registry.
skipping to change at page 1, line 43 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 9, 2017. This Internet-Draft will expire on March 13, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 5 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 12
2. Conventions used in this document . . . . . . . . . . . . . . 6 2. Conventions used in this document . . . . . . . . . . . . . . 13
2.1. Requirements Language . . . . . . . . . . . . . . . . . . 6 2.1. Requirements Language . . . . . . . . . . . . . . . . . . 13
2.2. Information Element Examples . . . . . . . . . . . . . . 6 2.2. Information Element Examples . . . . . . . . . . . . . . 13
3. Information Elements . . . . . . . . . . . . . . . . . . . . 6 3. Information Elements . . . . . . . . . . . . . . . . . . . . 13
3.1. Context of Information Elements . . . . . . . . . . . . . 6 3.1. Context of Information Elements . . . . . . . . . . . . . 13
3.2. Extensibility of Information Elements . . . . . . . . . . 7 3.2. Extensibility of Information Elements . . . . . . . . . . 14
4. Structure of Information Elements . . . . . . . . . . . . . . 7 4. Structure of Information Elements . . . . . . . . . . . . . . 14
4.1. SACM Content Elements . . . . . . . . . . . . . . . . . . 10 4.1. Information Element Naming Convention . . . . . . . . . . 17
4.2. SACM Statements . . . . . . . . . . . . . . . . . . . . . 11 4.2. SACM Content Elements . . . . . . . . . . . . . . . . . . 17
4.3. Relationships . . . . . . . . . . . . . . . . . . . . . . 13 4.3. SACM Statements . . . . . . . . . . . . . . . . . . . . . 18
4.4. Event . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4.4. Relationships . . . . . . . . . . . . . . . . . . . . . . 20
4.5. Categories . . . . . . . . . . . . . . . . . . . . . . . 16 4.5. Event . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.6. Designation . . . . . . . . . . . . . . . . . . . . . . . 16 4.6. Categories . . . . . . . . . . . . . . . . . . . . . . . 23
4.7. Privacy . . . . . . . . . . . . . . . . . . . . . . . . . 17 5. Abstract Data Types . . . . . . . . . . . . . . . . . . . . . 23
5. Abstract Data Types . . . . . . . . . . . . . . . . . . . . . 17 5.1. Simple Datatypes . . . . . . . . . . . . . . . . . . . . 23
5.1. Simple Datatypes . . . . . . . . . . . . . . . . . . . . 17 5.1.1. IPFIX Datatypes . . . . . . . . . . . . . . . . . . . 23
5.1.1. IPFIX Datatypes . . . . . . . . . . . . . . . . . . . 17 5.2. Structured Datatypes . . . . . . . . . . . . . . . . . . 24
5.1.2. ciscoTrainSoftwareVersion . . . . . . . . . . . . . . 18 5.2.1. List Datatypes . . . . . . . . . . . . . . . . . . . 24
5.1.3. rpmSoftwareVersion . . . . . . . . . . . . . . . . . 18 5.2.2. Enumeration Datatype . . . . . . . . . . . . . . . . 25
5.1.4. simpleSoftwareVersion . . . . . . . . . . . . . . . . 18 6. Information Model Assets . . . . . . . . . . . . . . . . . . 26
5.2. Structured Datatypes . . . . . . . . . . . . . . . . . . 18 6.1. Asset . . . . . . . . . . . . . . . . . . . . . . . . . . 27
5.2.1. List Datatypes . . . . . . . . . . . . . . . . . . . 18 6.2. Endpoint . . . . . . . . . . . . . . . . . . . . . . . . 27
6. Information Model Assets . . . . . . . . . . . . . . . . . . 20 6.3. Hardware Component . . . . . . . . . . . . . . . . . . . 28
6.1. Asset . . . . . . . . . . . . . . . . . . . . . . . . . . 21 6.4. Software Component . . . . . . . . . . . . . . . . . . . 28
6.2. Endpoint . . . . . . . . . . . . . . . . . . . . . . . . 21 6.4.1. Software Instance . . . . . . . . . . . . . . . . . . 28
6.3. Hardware Component . . . . . . . . . . . . . . . . . . . 22 6.5. Identity . . . . . . . . . . . . . . . . . . . . . . . . 29
6.4. Software Component . . . . . . . . . . . . . . . . . . . 22 6.6. Guidance . . . . . . . . . . . . . . . . . . . . . . . . 29
6.4.1. Software Instance . . . . . . . . . . . . . . . . . . 23 6.6.1. Collection Guidance . . . . . . . . . . . . . . . . . 29
6.5. Identity . . . . . . . . . . . . . . . . . . . . . . . . 23 6.6.2. Evaluation Guidance . . . . . . . . . . . . . . . . . 30
6.6. Guidance . . . . . . . . . . . . . . . . . . . . . . . . 23 6.6.3. Classification Guidance . . . . . . . . . . . . . . . 30
6.6.1. Internal Collection Guidance . . . . . . . . . . . . 23 6.6.4. Storage Guidance . . . . . . . . . . . . . . . . . . 31
6.6.2. External Collection Guidance . . . . . . . . . . . . 24 6.6.5. Evaluation Results . . . . . . . . . . . . . . . . . 31
6.6.3. Evaluation Guidance . . . . . . . . . . . . . . . . . 24 7. Information Model Elements . . . . . . . . . . . . . . . . . 31
6.6.4. Retention Guidance . . . . . . . . . . . . . . . . . 24 7.1. accessPrivilegeType . . . . . . . . . . . . . . . . . . . 31
6.7. Evaluation Results . . . . . . . . . . . . . . . . . . . 24 7.2. accountName . . . . . . . . . . . . . . . . . . . . . . . 32
7.3. administrativeDomainType . . . . . . . . . . . . . . . . 32
7. Information Model Elements . . . . . . . . . . . . . . . . . 24 7.4. addressAssociationType . . . . . . . . . . . . . . . . . 32
7.1. hardwareSerialNumber . . . . . . . . . . . . . . . . . . 25 7.5. addressMaskValue . . . . . . . . . . . . . . . . . . . . 32
7.2. interfaceName . . . . . . . . . . . . . . . . . . . . . . 25 7.6. addressType . . . . . . . . . . . . . . . . . . . . . . . 32
7.3. interfaceIndex . . . . . . . . . . . . . . . . . . . . . 25 7.7. addressValue . . . . . . . . . . . . . . . . . . . . . . 33
7.4. interfaceMacAddress . . . . . . . . . . . . . . . . . . . 25 7.8. applicationComponent . . . . . . . . . . . . . . . . . . 33
7.5. interfaceType . . . . . . . . . . . . . . . . . . . . . . 26 7.9. applicationLabel . . . . . . . . . . . . . . . . . . . . 33
7.6. interfaceFlags . . . . . . . . . . . . . . . . . . . . . 26 7.10. applicationType . . . . . . . . . . . . . . . . . . . . . 33
7.7. networkInterface . . . . . . . . . . . . . . . . . . . . 26 7.11. applicationManufacturer . . . . . . . . . . . . . . . . . 33
7.8. softwareIdentifier . . . . . . . . . . . . . . . . . . . 27 7.12. authenticator . . . . . . . . . . . . . . . . . . . . . . 34
7.9. softwareTitle . . . . . . . . . . . . . . . . . . . . . . 27 7.13. authenticationType . . . . . . . . . . . . . . . . . . . 34
7.10. softwareCreator . . . . . . . . . . . . . . . . . . . . . 27 7.14. birthdate . . . . . . . . . . . . . . . . . . . . . . . . 34
7.11. simpleSoftwareVersion . . . . . . . . . . . . . . . . . . 27 7.15. bytesReceived . . . . . . . . . . . . . . . . . . . . . . 34
7.12. rpmSoftwareVersion . . . . . . . . . . . . . . . . . . . 27 7.16. bytesSent . . . . . . . . . . . . . . . . . . . . . . . . 34
7.13. ciscoTrainSoftwareVersion . . . . . . . . . . . . . . . . 27 7.17. bytesSent . . . . . . . . . . . . . . . . . . . . . . . . 35
7.14. softwareVersion . . . . . . . . . . . . . . . . . . . . . 28 7.18. certificate . . . . . . . . . . . . . . . . . . . . . . . 35
7.15. lastUpdated . . . . . . . . . . . . . . . . . . . . . . . 28 7.19. collectionTaskType . . . . . . . . . . . . . . . . . . . 35
7.16. softwareInstance . . . . . . . . . . . . . . . . . . . . 28 7.20. confidence . . . . . . . . . . . . . . . . . . . . . . . 35
7.17. globallyUniqueIdentifier . . . . . . . . . . . . . . . . 28 7.21. contentAction . . . . . . . . . . . . . . . . . . . . . . 36
7.18. dataOrigin . . . . . . . . . . . . . . . . . . . . . . . 29 7.22. countryCode . . . . . . . . . . . . . . . . . . . . . . . 36
7.19. dataSource . . . . . . . . . . . . . . . . . . . . . . . 29 7.23. dataOrigin . . . . . . . . . . . . . . . . . . . . . . . 36
7.20. creationTimestamp . . . . . . . . . . . . . . . . . . . . 29 7.24. dataSource . . . . . . . . . . . . . . . . . . . . . . . 36
7.21. collectionTimestamp . . . . . . . . . . . . . . . . . . . 29 7.25. default-depth . . . . . . . . . . . . . . . . . . . . . . 36
7.22. publicationTimestamp . . . . . . . . . . . . . . . . . . 30 7.26. discoverer . . . . . . . . . . . . . . . . . . . . . . . 37
7.23. relayTimestamp . . . . . . . . . . . . . . . . . . . . . 30 7.27. emailAddress . . . . . . . . . . . . . . . . . . . . . . 37
7.24. storageTimestamp . . . . . . . . . . . . . . . . . . . . 30 7.28. eventType . . . . . . . . . . . . . . . . . . . . . . . . 37
7.25. type . . . . . . . . . . . . . . . . . . . . . . . . . . 30 7.29. eventThreshold . . . . . . . . . . . . . . . . . . . . . 37
7.26. protocolIdentifier . . . . . . . . . . . . . . . . . . . 31 7.30. eventThresholdName . . . . . . . . . . . . . . . . . . . 37
7.27. sourceTransportPort . . . . . . . . . . . . . . . . . . . 31 7.31. eventTrigger . . . . . . . . . . . . . . . . . . . . . . 38
7.28. sourceIPv4PrefixLength . . . . . . . . . . . . . . . . . 32 7.32. eventTrigger . . . . . . . . . . . . . . . . . . . . . . 38
7.29. ingressInterface . . . . . . . . . . . . . . . . . . . . 32 7.33. firmwareId . . . . . . . . . . . . . . . . . . . . . . . 38
7.30. destinationTransportPort . . . . . . . . . . . . . . . . 32 7.34. hostName . . . . . . . . . . . . . . . . . . . . . . . . 38
7.31. sourceIPv6PrefixLength . . . . . . . . . . . . . . . . . 33 7.35. interfaceLabel . . . . . . . . . . . . . . . . . . . . . 39
7.32. sourceIPv4Prefix . . . . . . . . . . . . . . . . . . . . 33 7.36. ipv6AddressSubnetMask . . . . . . . . . . . . . . . . . . 39
7.33. destinationIPv4Prefix . . . . . . . . . . . . . . . . . . 33 7.37. ipv6AddressSubnetMaskCidrNotation . . . . . . . . . . . . 39
7.34. sourceMacAddress . . . . . . . . . . . . . . . . . . . . 33 7.38. ipv6AddressValue . . . . . . . . . . . . . . . . . . . . 39
7.35. ipVersion . . . . . . . . . . . . . . . . . . . . . . . . 33 7.39. ipv4AddressSubnetMask . . . . . . . . . . . . . . . . . . 39
7.36. interfaceDescription . . . . . . . . . . . . . . . . . . 33 7.40. ipv4AddressSubnetMaskCidrNotation . . . . . . . . . . . . 39
7.37. applicationDescription . . . . . . . . . . . . . . . . . 34 7.41. ipv4AddressValue . . . . . . . . . . . . . . . . . . . . 40
7.38. applicationId . . . . . . . . . . . . . . . . . . . . . . 34 7.42. layer2InterfaceType . . . . . . . . . . . . . . . . . . . 40
7.39. applicationName . . . . . . . . . . . . . . . . . . . . . 34 7.43. layer4PortAddress . . . . . . . . . . . . . . . . . . . . 40
7.40. exporterIPv4Address . . . . . . . . . . . . . . . . . . . 34 7.44. layer4Protocol . . . . . . . . . . . . . . . . . . . . . 40
7.41. exporterIPv6Address . . . . . . . . . . . . . . . . . . . 34 7.45. locationName . . . . . . . . . . . . . . . . . . . . . . 40
7.42. portId . . . . . . . . . . . . . . . . . . . . . . . . . 35 7.46. macAddressValue . . . . . . . . . . . . . . . . . . . . . 41
7.43. templateId . . . . . . . . . . . . . . . . . . . . . . . 35 7.47. methodLabel . . . . . . . . . . . . . . . . . . . . . . . 41
7.44. collectorIPv4Address . . . . . . . . . . . . . . . . . . 35 7.48. methodRepository . . . . . . . . . . . . . . . . . . . . 41
7.45. collectorIPv6Address . . . . . . . . . . . . . . . . . . 36 7.49. networkAccessLevelType . . . . . . . . . . . . . . . . . 41
7.46. informationElementIndex . . . . . . . . . . . . . . . . . 36 7.50. networkId . . . . . . . . . . . . . . . . . . . . . . . . 42
7.47. informationElementId . . . . . . . . . . . . . . . . . . 36 7.51. networkInterfaceName . . . . . . . . . . . . . . . . . . 42
7.48. informationElementDataType . . . . . . . . . . . . . . . 36 7.52. networkLayer . . . . . . . . . . . . . . . . . . . . . . 42
7.49. informationElementDescription . . . . . . . . . . . . . . 37 7.53. networkName . . . . . . . . . . . . . . . . . . . . . . . 42
7.50. informationElementName . . . . . . . . . . . . . . . . . 37 7.54. organizationId . . . . . . . . . . . . . . . . . . . . . 42
7.51. informationElementRangeBegin . . . . . . . . . . . . . . 38 7.55. osComponent . . . . . . . . . . . . . . . . . . . . . . . 43
7.52. informationElementRangeEnd . . . . . . . . . . . . . . . 38 7.56. osLabel . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.53. informationElementSemantics . . . . . . . . . . . . . . . 38 7.57. osName . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.54. informationElementUnits . . . . . . . . . . . . . . . . . 39 7.58. osType . . . . . . . . . . . . . . . . . . . . . . . . . 43
7.55. userName . . . . . . . . . . . . . . . . . . . . . . . . 40 7.59. osVersion . . . . . . . . . . . . . . . . . . . . . . . . 43
7.56. applicationCategoryName . . . . . . . . . . . . . . . . . 40 7.60. patchId . . . . . . . . . . . . . . . . . . . . . . . . . 44
7.57. mibObjectValueInteger . . . . . . . . . . . . . . . . . . 40 7.61. patchName . . . . . . . . . . . . . . . . . . . . . . . . 44
7.58. mibObjectValueOctetString . . . . . . . . . . . . . . . . 40 7.62. personFirstName . . . . . . . . . . . . . . . . . . . . . 44
7.59. mibObjectValueOID . . . . . . . . . . . . . . . . . . . . 41 7.63. personLastName . . . . . . . . . . . . . . . . . . . . . 44
7.60. mibObjectValueBits . . . . . . . . . . . . . . . . . . . 41 7.64. personMiddleName . . . . . . . . . . . . . . . . . . . . 44
7.61. mibObjectValueIPAddress . . . . . . . . . . . . . . . . . 42 7.65. phoneNumber . . . . . . . . . . . . . . . . . . . . . . . 44
7.62. mibObjectValueCounter . . . . . . . . . . . . . . . . . . 42 7.66. phoneNumberType . . . . . . . . . . . . . . . . . . . . . 45
7.63. mibObjectValueGauge . . . . . . . . . . . . . . . . . . . 43 7.67. privilegeName . . . . . . . . . . . . . . . . . . . . . . 45
7.64. mibObjectValueTimeTicks . . . . . . . . . . . . . . . . . 43 7.68. privilegeValue . . . . . . . . . . . . . . . . . . . . . 45
7.65. mibObjectValueUnsigned . . . . . . . . . . . . . . . . . 44 7.69. protocol . . . . . . . . . . . . . . . . . . . . . . . . 45
7.66. mibObjectValueTable . . . . . . . . . . . . . . . . . . . 44 7.70. publicKey . . . . . . . . . . . . . . . . . . . . . . . . 46
7.67. mibObjectValueRow . . . . . . . . . . . . . . . . . . . . 44 7.71. relationshipContentElementGuid . . . . . . . . . . . . . 46
7.68. mibObjectIdentifier . . . . . . . . . . . . . . . . . . . 45 7.72. relationshipStatementElementGuid . . . . . . . . . . . . 46
7.69. mibSubIdentifier . . . . . . . . . . . . . . . . . . . . 45 7.73. relationshipObjectLabel . . . . . . . . . . . . . . . . . 46
7.70. mibIndexIndicator . . . . . . . . . . . . . . . . . . . . 45 7.74. relationshipType . . . . . . . . . . . . . . . . . . . . 46
7.71. mibCaptureTimeSemantics . . . . . . . . . . . . . . . . . 46 7.75. roleName . . . . . . . . . . . . . . . . . . . . . . . . 47
7.72. mibContextEngineID . . . . . . . . . . . . . . . . . . . 47 7.76. sessionStateType . . . . . . . . . . . . . . . . . . . . 47
7.73. mibContextName . . . . . . . . . . . . . . . . . . . . . 48 7.77. statementGuid . . . . . . . . . . . . . . . . . . . . . . 47
7.74. mibObjectName . . . . . . . . . . . . . . . . . . . . . . 48 7.78. statementType . . . . . . . . . . . . . . . . . . . . . . 47
7.75. mibObjectDescription . . . . . . . . . . . . . . . . . . 48 7.79. status . . . . . . . . . . . . . . . . . . . . . . . . . 48
7.76. mibObjectSyntax . . . . . . . . . . . . . . . . . . . . . 48 7.80. subAdministrativeDomain . . . . . . . . . . . . . . . . . 48
7.77. mibModuleName . . . . . . . . . . . . . . . . . . . . . . 48 7.81. subInterfaceLabel . . . . . . . . . . . . . . . . . . . . 48
8. SACM Usage Scenario Example . . . . . . . . . . . . . . . . . 49 7.82. superAdministrativeDomain . . . . . . . . . . . . . . . . 48
8.1. Graph Model for Detection of Posture Deviation . . . . . 49 7.83. superInterfaceLabel . . . . . . . . . . . . . . . . . . . 49
8.1.1. Components . . . . . . . . . . . . . . . . . . . . . 49 7.84. teAssessmentState . . . . . . . . . . . . . . . . . . . . 49
8.1.2. Identifiers . . . . . . . . . . . . . . . . . . . . . 50 7.85. teLabel . . . . . . . . . . . . . . . . . . . . . . . . . 49
8.1.3. Metadata . . . . . . . . . . . . . . . . . . . . . . 50 7.86. teId . . . . . . . . . . . . . . . . . . . . . . . . . . 49
8.1.4. Relationships between Identifiers and Metadata . . . 51 7.87. timestampType . . . . . . . . . . . . . . . . . . . . . . 49
8.2. Workflow . . . . . . . . . . . . . . . . . . . . . . . . 51 7.88. unitsReceived . . . . . . . . . . . . . . . . . . . . . . 50
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 52 7.89. unitsSent . . . . . . . . . . . . . . . . . . . . . . . . 50
9.1. Contributors . . . . . . . . . . . . . . . . . . . . . . 52 7.90. username . . . . . . . . . . . . . . . . . . . . . . . . 50
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 52 7.91. userDirectory . . . . . . . . . . . . . . . . . . . . . . 50
11. Operational Considerations . . . . . . . . . . . . . . . . . 53 7.92. userId . . . . . . . . . . . . . . . . . . . . . . . . . 51
12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 53 7.93. webSite . . . . . . . . . . . . . . . . . . . . . . . . . 51
13. Security Considerations . . . . . . . . . . . . . . . . . . . 53 7.94. WGS84Longitude . . . . . . . . . . . . . . . . . . . . . 51
14. References . . . . . . . . . . . . . . . . . . . . . . . . . 54 7.95. WGS84Latitude . . . . . . . . . . . . . . . . . . . . . . 51
14.1. Normative References . . . . . . . . . . . . . . . . . . 54 7.96. WGS84Altitude . . . . . . . . . . . . . . . . . . . . . . 51
14.2. Informative References . . . . . . . . . . . . . . . . . 54 7.97. hardwareSerialNumber . . . . . . . . . . . . . . . . . . 52
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 55 7.98. interfaceName . . . . . . . . . . . . . . . . . . . . . . 52
A.1. Changes in Revision 01 . . . . . . . . . . . . . . . . . 55 7.99. interfaceIndex . . . . . . . . . . . . . . . . . . . . . 52
A.2. Changes in Revision 02 . . . . . . . . . . . . . . . . . 56 7.100. interfaceMacAddress . . . . . . . . . . . . . . . . . . 52
A.3. Changes in Revision 03 . . . . . . . . . . . . . . . . . 56 7.101. interfaceType . . . . . . . . . . . . . . . . . . . . . 53
A.4. Changes in Revision 04 . . . . . . . . . . . . . . . . . 57 7.102. interfaceFlags . . . . . . . . . . . . . . . . . . . . . 53
A.5. Changes in Revision 05 . . . . . . . . . . . . . . . . . 57 7.103. networkInterface . . . . . . . . . . . . . . . . . . . . 53
A.6. Changes in Revision 06 . . . . . . . . . . . . . . . . . 57 7.104. softwareIdentifier . . . . . . . . . . . . . . . . . . . 54
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 58 7.105. softwareTitle . . . . . . . . . . . . . . . . . . . . . 54
7.106. softwareCreator . . . . . . . . . . . . . . . . . . . . 54
7.107. simpleSoftwareVersion . . . . . . . . . . . . . . . . . 54
7.108. rpmSoftwareVersion . . . . . . . . . . . . . . . . . . . 54
7.109. ciscoTrainSoftwareVersion . . . . . . . . . . . . . . . 55
7.110. softwareVersion . . . . . . . . . . . . . . . . . . . . 55
7.111. lastUpdated . . . . . . . . . . . . . . . . . . . . . . 55
7.112. softwareInstance . . . . . . . . . . . . . . . . . . . . 55
7.113. globallyUniqueIdentifier . . . . . . . . . . . . . . . . 56
7.114. dataOrigin . . . . . . . . . . . . . . . . . . . . . . . 56
7.115. dataSource . . . . . . . . . . . . . . . . . . . . . . . 56
7.116. creationTimestamp . . . . . . . . . . . . . . . . . . . 56
7.117. collectionTimestamp . . . . . . . . . . . . . . . . . . 56
7.118. publicationTimestamp . . . . . . . . . . . . . . . . . . 57
7.119. relayTimestamp . . . . . . . . . . . . . . . . . . . . . 57
7.120. storageTimestamp . . . . . . . . . . . . . . . . . . . . 57
7.121. type . . . . . . . . . . . . . . . . . . . . . . . . . . 57
7.122. protocolIdentifier . . . . . . . . . . . . . . . . . . . 57
7.123. sourceTransportPort . . . . . . . . . . . . . . . . . . 58
7.124. sourceIPv4PrefixLength . . . . . . . . . . . . . . . . . 58
7.125. ingressInterface . . . . . . . . . . . . . . . . . . . . 58
7.126. destinationTransportPort . . . . . . . . . . . . . . . . 59
7.127. sourceIPv6PrefixLength . . . . . . . . . . . . . . . . . 59
7.128. sourceIPv4Prefix . . . . . . . . . . . . . . . . . . . . 59
7.129. destinationIPv4Prefix . . . . . . . . . . . . . . . . . 59
7.130. sourceMacAddress . . . . . . . . . . . . . . . . . . . . 60
7.131. ipVersion . . . . . . . . . . . . . . . . . . . . . . . 60
7.132. interfaceDescription . . . . . . . . . . . . . . . . . . 60
7.133. applicationDescription . . . . . . . . . . . . . . . . . 60
7.134. applicationId . . . . . . . . . . . . . . . . . . . . . 60
7.135. applicationName . . . . . . . . . . . . . . . . . . . . 61
7.136. exporterIPv4Address . . . . . . . . . . . . . . . . . . 61
7.137. exporterIPv6Address . . . . . . . . . . . . . . . . . . 61
7.138. portId . . . . . . . . . . . . . . . . . . . . . . . . . 61
7.139. templateId . . . . . . . . . . . . . . . . . . . . . . . 61
7.140. collectorIPv4Address . . . . . . . . . . . . . . . . . . 62
7.141. collectorIPv6Address . . . . . . . . . . . . . . . . . . 62
7.142. informationElementIndex . . . . . . . . . . . . . . . . 62
7.143. informationElementId . . . . . . . . . . . . . . . . . . 63
7.144. informationElementDataType . . . . . . . . . . . . . . . 63
7.145. informationElementDescription . . . . . . . . . . . . . 63
7.146. informationElementName . . . . . . . . . . . . . . . . . 64
7.147. informationElementRangeBegin . . . . . . . . . . . . . . 64
7.148. informationElementRangeEnd . . . . . . . . . . . . . . . 64
7.149. informationElementSemantics . . . . . . . . . . . . . . 65
7.150. informationElementUnits . . . . . . . . . . . . . . . . 65
7.151. userName . . . . . . . . . . . . . . . . . . . . . . . . 66
7.152. applicationCategoryName . . . . . . . . . . . . . . . . 66
7.153. mibObjectValueInteger . . . . . . . . . . . . . . . . . 66
7.154. mibObjectValueOctetString . . . . . . . . . . . . . . . 67
7.155. mibObjectValueOID . . . . . . . . . . . . . . . . . . . 67
7.156. mibObjectValueBits . . . . . . . . . . . . . . . . . . . 68
7.157. mibObjectValueIPAddress . . . . . . . . . . . . . . . . 68
7.158. mibObjectValueCounter . . . . . . . . . . . . . . . . . 69
7.159. mibObjectValueGauge . . . . . . . . . . . . . . . . . . 69
7.160. mibObjectValueTimeTicks . . . . . . . . . . . . . . . . 70
7.161. mibObjectValueUnsigned . . . . . . . . . . . . . . . . . 70
7.162. mibObjectValueTable . . . . . . . . . . . . . . . . . . 70
7.163. mibObjectValueRow . . . . . . . . . . . . . . . . . . . 71
7.164. mibObjectIdentifier . . . . . . . . . . . . . . . . . . 71
7.165. mibSubIdentifier . . . . . . . . . . . . . . . . . . . . 72
7.166. mibIndexIndicator . . . . . . . . . . . . . . . . . . . 72
7.167. mibCaptureTimeSemantics . . . . . . . . . . . . . . . . 73
7.168. mibContextEngineID . . . . . . . . . . . . . . . . . . . 74
7.169. mibContextName . . . . . . . . . . . . . . . . . . . . . 75
7.170. mibObjectName . . . . . . . . . . . . . . . . . . . . . 75
7.171. mibObjectDescription . . . . . . . . . . . . . . . . . . 75
7.172. mibObjectSyntax . . . . . . . . . . . . . . . . . . . . 75
7.173. mibModuleName . . . . . . . . . . . . . . . . . . . . . 75
7.174. interface . . . . . . . . . . . . . . . . . . . . . . . 76
7.175. interfaceName . . . . . . . . . . . . . . . . . . . . . 76
7.176. iflisteners . . . . . . . . . . . . . . . . . . . . . . 76
7.177. physicalProtocol . . . . . . . . . . . . . . . . . . . . 76
7.178. hwAddress . . . . . . . . . . . . . . . . . . . . . . . 78
7.179. programName . . . . . . . . . . . . . . . . . . . . . . 78
7.180. userId . . . . . . . . . . . . . . . . . . . . . . . . . 78
7.181. inetlisteningserver . . . . . . . . . . . . . . . . . . 78
7.182. transportProtocol . . . . . . . . . . . . . . . . . . . 78
7.183. localAddress . . . . . . . . . . . . . . . . . . . . . . 79
7.184. localPort . . . . . . . . . . . . . . . . . . . . . . . 79
7.185. localFullAddress . . . . . . . . . . . . . . . . . . . . 79
7.186. foreignAddress . . . . . . . . . . . . . . . . . . . . . 79
7.187. foreignFullAddress . . . . . . . . . . . . . . . . . . . 79
7.188. selinuxboolean . . . . . . . . . . . . . . . . . . . . . 80
7.189. selinuxName . . . . . . . . . . . . . . . . . . . . . . 80
7.190. currentStatus . . . . . . . . . . . . . . . . . . . . . 80
7.191. pendingStatus . . . . . . . . . . . . . . . . . . . . . 80
7.192. selinuxsecuritycontext . . . . . . . . . . . . . . . . . 80
7.193. filepath . . . . . . . . . . . . . . . . . . . . . . . . 81
7.194. path . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.195. filename . . . . . . . . . . . . . . . . . . . . . . . . 81
7.196. pid . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.197. role . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.198. domainType . . . . . . . . . . . . . . . . . . . . . . . 82
7.199. lowSensitivity . . . . . . . . . . . . . . . . . . . . . 82
7.200. lowCategory . . . . . . . . . . . . . . . . . . . . . . 82
7.201. highSensitivity . . . . . . . . . . . . . . . . . . . . 82
7.202. highCategory . . . . . . . . . . . . . . . . . . . . . . 83
7.203. rawlowSensitivity . . . . . . . . . . . . . . . . . . . 83
7.204. rawlowCategory . . . . . . . . . . . . . . . . . . . . . 83
7.205. rawhighSensitivity . . . . . . . . . . . . . . . . . . . 83
7.206. rawhighCategory . . . . . . . . . . . . . . . . . . . . 83
7.207. systemdunitdependency . . . . . . . . . . . . . . . . . 84
7.208. unit . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.209. dependency . . . . . . . . . . . . . . . . . . . . . . . 84
7.210. systemdunitproperty . . . . . . . . . . . . . . . . . . 84
7.211. property . . . . . . . . . . . . . . . . . . . . . . . . 84
7.212. systemdunitValue . . . . . . . . . . . . . . . . . . . . 85
7.213. file . . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.214. fileType . . . . . . . . . . . . . . . . . . . . . . . . 85
7.215. groupId . . . . . . . . . . . . . . . . . . . . . . . . 85
7.216. aTime . . . . . . . . . . . . . . . . . . . . . . . . . 85
7.217. changeTime . . . . . . . . . . . . . . . . . . . . . . . 86
7.218. mTime . . . . . . . . . . . . . . . . . . . . . . . . . 86
7.219. size . . . . . . . . . . . . . . . . . . . . . . . . . . 86
7.220. suid . . . . . . . . . . . . . . . . . . . . . . . . . . 86
7.221. sgid . . . . . . . . . . . . . . . . . . . . . . . . . . 86
7.222. sticky . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.223. hasExtendedAcl . . . . . . . . . . . . . . . . . . . . . 87
7.224. inetd . . . . . . . . . . . . . . . . . . . . . . . . . 87
7.225. serverProgram . . . . . . . . . . . . . . . . . . . . . 87
7.226. endpointType . . . . . . . . . . . . . . . . . . . . . . 88
7.227. execAsUser . . . . . . . . . . . . . . . . . . . . . . . 88
7.228. waitStatus . . . . . . . . . . . . . . . . . . . . . . . 88
7.229. inetAddr . . . . . . . . . . . . . . . . . . . . . . . . 89
7.230. netmask . . . . . . . . . . . . . . . . . . . . . . . . 89
7.231. passwordInfo . . . . . . . . . . . . . . . . . . . . . . 89
7.232. username . . . . . . . . . . . . . . . . . . . . . . . . 90
7.233. password . . . . . . . . . . . . . . . . . . . . . . . . 90
7.234. gcos . . . . . . . . . . . . . . . . . . . . . . . . . . 90
7.235. homeDir . . . . . . . . . . . . . . . . . . . . . . . . 90
7.236. loginShell . . . . . . . . . . . . . . . . . . . . . . . 90
7.237. lastLogin . . . . . . . . . . . . . . . . . . . . . . . 91
7.238. process . . . . . . . . . . . . . . . . . . . . . . . . 91
7.239. commandLine . . . . . . . . . . . . . . . . . . . . . . 91
7.240. ppid . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.241. priority . . . . . . . . . . . . . . . . . . . . . . . . 92
7.242. startTime . . . . . . . . . . . . . . . . . . . . . . . 92
7.243. routingtable . . . . . . . . . . . . . . . . . . . . . . 92
7.244. destination . . . . . . . . . . . . . . . . . . . . . . 92
7.245. gateway . . . . . . . . . . . . . . . . . . . . . . . . 92
7.246. runlevelInfo . . . . . . . . . . . . . . . . . . . . . . 93
7.247. runlevel . . . . . . . . . . . . . . . . . . . . . . . . 93
7.248. start . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.249. kill . . . . . . . . . . . . . . . . . . . . . . . . . . 93
7.250. shadowItem . . . . . . . . . . . . . . . . . . . . . . . 93
7.251. chgLst . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.252. chgAllow . . . . . . . . . . . . . . . . . . . . . . . . 94
7.253. chgReq . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.254. expWarn . . . . . . . . . . . . . . . . . . . . . . . . 94
7.255. expInact . . . . . . . . . . . . . . . . . . . . . . . . 94
7.256. expDate . . . . . . . . . . . . . . . . . . . . . . . . 95
7.257. encryptMethod . . . . . . . . . . . . . . . . . . . . . 95
7.258. symlink . . . . . . . . . . . . . . . . . . . . . . . . 95
7.259. symlinkFilepath . . . . . . . . . . . . . . . . . . . . 95
7.260. canonicalPath . . . . . . . . . . . . . . . . . . . . . 96
7.261. sysctl . . . . . . . . . . . . . . . . . . . . . . . . . 96
7.262. kernelParameterName . . . . . . . . . . . . . . . . . . 96
7.263. kernelParameterValue . . . . . . . . . . . . . . . . . . 96
7.264. uname . . . . . . . . . . . . . . . . . . . . . . . . . 97
7.265. machineClass . . . . . . . . . . . . . . . . . . . . . . 97
7.266. nodeName . . . . . . . . . . . . . . . . . . . . . . . . 97
7.267. osName . . . . . . . . . . . . . . . . . . . . . . . . . 97
7.268. osRelease . . . . . . . . . . . . . . . . . . . . . . . 97
7.269. osVersion . . . . . . . . . . . . . . . . . . . . . . . 98
7.270. processorType . . . . . . . . . . . . . . . . . . . . . 98
7.271. internetService . . . . . . . . . . . . . . . . . . . . 98
7.272. serviceProtocol . . . . . . . . . . . . . . . . . . . . 98
7.273. serviceName . . . . . . . . . . . . . . . . . . . . . . 98
7.274. flags . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.275. noAccess . . . . . . . . . . . . . . . . . . . . . . . . 99
7.276. onlyFrom . . . . . . . . . . . . . . . . . . . . . . . . 99
7.277. port . . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.278. server . . . . . . . . . . . . . . . . . . . . . . . . . 99
7.279. serverArguments . . . . . . . . . . . . . . . . . . . . 100
7.280. socketType . . . . . . . . . . . . . . . . . . . . . . . 100
7.281. registeredServiceType . . . . . . . . . . . . . . . . . 100
7.282. wait . . . . . . . . . . . . . . . . . . . . . . . . . . 101
7.283. disabled . . . . . . . . . . . . . . . . . . . . . . . . 101
7.284. windowsView . . . . . . . . . . . . . . . . . . . . . . 101
7.285. fileauditedpermissions . . . . . . . . . . . . . . . . . 101
7.286. trusteeName . . . . . . . . . . . . . . . . . . . . . . 102
7.287. auditStandardDelete . . . . . . . . . . . . . . . . . . 102
7.288. auditStandardReadControl . . . . . . . . . . . . . . . . 103
7.289. auditStandardWriteDac . . . . . . . . . . . . . . . . . 103
7.290. auditStandardWriteOwner . . . . . . . . . . . . . . . . 104
7.291. auditStandardSynchronize . . . . . . . . . . . . . . . . 104
7.292. auditAccessSystemSecurity . . . . . . . . . . . . . . . 105
7.293. auditGenericRead . . . . . . . . . . . . . . . . . . . . 105
7.294. auditGenericWrite . . . . . . . . . . . . . . . . . . . 106
7.295. auditGenericExecute . . . . . . . . . . . . . . . . . . 106
7.296. auditGenericAll . . . . . . . . . . . . . . . . . . . . 107
7.297. auditFileReadData . . . . . . . . . . . . . . . . . . . 107
7.298. auditFileWriteData . . . . . . . . . . . . . . . . . . . 108
7.299. auditFileAppendData . . . . . . . . . . . . . . . . . . 108
7.300. auditFileReadEa . . . . . . . . . . . . . . . . . . . . 109
7.301. auditFileWriteEa . . . . . . . . . . . . . . . . . . . . 109
7.302. auditFileExecute . . . . . . . . . . . . . . . . . . . . 110
7.303. auditFileDeleteChild . . . . . . . . . . . . . . . . . . 110
7.304. auditFileReadAttributes . . . . . . . . . . . . . . . . 111
7.305. auditFileWriteAttributes . . . . . . . . . . . . . . . . 111
7.306. fileeffectiverights . . . . . . . . . . . . . . . . . . 112
7.307. standardDelete . . . . . . . . . . . . . . . . . . . . . 112
7.308. standardReadControl . . . . . . . . . . . . . . . . . . 113
7.309. standardWriteDac . . . . . . . . . . . . . . . . . . . . 113
7.310. standardWriteOwner . . . . . . . . . . . . . . . . . . . 113
7.311. standardSynchronize . . . . . . . . . . . . . . . . . . 113
7.312. accessSystemSecurity . . . . . . . . . . . . . . . . . . 113
7.313. genericRead . . . . . . . . . . . . . . . . . . . . . . 114
7.314. genericWrite . . . . . . . . . . . . . . . . . . . . . . 114
7.315. genericExecute . . . . . . . . . . . . . . . . . . . . . 114
7.316. genericAll . . . . . . . . . . . . . . . . . . . . . . . 114
7.317. fileReadData . . . . . . . . . . . . . . . . . . . . . . 114
7.318. fileWriteData . . . . . . . . . . . . . . . . . . . . . 114
7.319. fileAppendData . . . . . . . . . . . . . . . . . . . . . 115
7.320. fileReadEa . . . . . . . . . . . . . . . . . . . . . . . 115
7.321. fileWriteEa . . . . . . . . . . . . . . . . . . . . . . 115
7.322. fileExecute . . . . . . . . . . . . . . . . . . . . . . 115
7.323. fileDeleteChild . . . . . . . . . . . . . . . . . . . . 115
7.324. fileReadAttributes . . . . . . . . . . . . . . . . . . . 116
7.325. fileWriteAttributes . . . . . . . . . . . . . . . . . . 116
7.326. groupInfo . . . . . . . . . . . . . . . . . . . . . . . 116
7.327. group . . . . . . . . . . . . . . . . . . . . . . . . . 116
7.328. user . . . . . . . . . . . . . . . . . . . . . . . . . . 117
7.329. subgroup . . . . . . . . . . . . . . . . . . . . . . . . 117
7.330. groupSidInfo . . . . . . . . . . . . . . . . . . . . . . 117
7.331. userSidInfo . . . . . . . . . . . . . . . . . . . . . . 117
7.332. userSid . . . . . . . . . . . . . . . . . . . . . . . . 117
7.333. subgroupSid . . . . . . . . . . . . . . . . . . . . . . 118
7.334. lockoutpolicy . . . . . . . . . . . . . . . . . . . . . 118
7.335. forceLogoff . . . . . . . . . . . . . . . . . . . . . . 118
7.336. lockoutDuration . . . . . . . . . . . . . . . . . . . . 118
7.337. lockoutObservationWindow . . . . . . . . . . . . . . . . 119
7.338. lockoutThreshold . . . . . . . . . . . . . . . . . . . . 119
7.339. passwordpolicy . . . . . . . . . . . . . . . . . . . . . 119
7.340. maxPasswdAge . . . . . . . . . . . . . . . . . . . . . . 119
7.341. minPasswdAge . . . . . . . . . . . . . . . . . . . . . . 120
7.342. minPasswdLen . . . . . . . . . . . . . . . . . . . . . . 120
7.343. passwordHistLen . . . . . . . . . . . . . . . . . . . . 120
7.344. passwordComplexity . . . . . . . . . . . . . . . . . . . 120
7.345. reversibleEncryption . . . . . . . . . . . . . . . . . . 120
7.346. portInfo . . . . . . . . . . . . . . . . . . . . . . . . 121
7.347. foreignPort . . . . . . . . . . . . . . . . . . . . . . 121
7.348. printereffectiverights . . . . . . . . . . . . . . . . . 121
7.349. printerName . . . . . . . . . . . . . . . . . . . . . . 122
7.350. printerAccessAdminister . . . . . . . . . . . . . . . . 122
7.351. printerAccessUse . . . . . . . . . . . . . . . . . . . . 122
7.352. jobAccessAdminister . . . . . . . . . . . . . . . . . . 122
7.353. jobAccessRead . . . . . . . . . . . . . . . . . . . . . 122
7.354. registry . . . . . . . . . . . . . . . . . . . . . . . . 122
7.355. hive . . . . . . . . . . . . . . . . . . . . . . . . . . 123
7.356. registryKey . . . . . . . . . . . . . . . . . . . . . . 123
7.357. registryKeyName . . . . . . . . . . . . . . . . . . . . 124
7.358. lastWriteTime . . . . . . . . . . . . . . . . . . . . . 124
7.359. registryKeyType . . . . . . . . . . . . . . . . . . . . 124
7.360. registryKeyValue . . . . . . . . . . . . . . . . . . . . 125
7.361. regkeyauditedpermissions . . . . . . . . . . . . . . . . 126
7.362. auditKeyQueryValue . . . . . . . . . . . . . . . . . . . 127
7.363. auditKeySetValue . . . . . . . . . . . . . . . . . . . . 127
7.364. auditKeyCreateSubKey . . . . . . . . . . . . . . . . . . 128
7.365. auditKeyEnumerateSubKeys . . . . . . . . . . . . . . . . 128
7.366. auditKeyNotify . . . . . . . . . . . . . . . . . . . . . 129
7.367. auditKeyCreateLink . . . . . . . . . . . . . . . . . . . 129
7.368. auditKeyWow6464Key . . . . . . . . . . . . . . . . . . . 130
7.369. auditKeyWow6432Key . . . . . . . . . . . . . . . . . . . 130
7.370. auditKeyWow64Res . . . . . . . . . . . . . . . . . . . . 131
7.371. regkeyeffectiverights . . . . . . . . . . . . . . . . . 131
7.372. keyQueryValue . . . . . . . . . . . . . . . . . . . . . 132
7.373. keySetValue . . . . . . . . . . . . . . . . . . . . . . 132
7.374. keyCreateSubKey . . . . . . . . . . . . . . . . . . . . 132
7.375. keyEnumerateSubKeys . . . . . . . . . . . . . . . . . . 133
7.376. keyNotify . . . . . . . . . . . . . . . . . . . . . . . 133
7.377. keyCreateLink . . . . . . . . . . . . . . . . . . . . . 133
7.378. keyWow6464Key . . . . . . . . . . . . . . . . . . . . . 133
7.379. keyWow6432Key . . . . . . . . . . . . . . . . . . . . . 133
7.380. keyWow64Res . . . . . . . . . . . . . . . . . . . . . . 133
7.381. service . . . . . . . . . . . . . . . . . . . . . . . . 134
7.382. displayName . . . . . . . . . . . . . . . . . . . . . . 134
7.383. description . . . . . . . . . . . . . . . . . . . . . . 134
7.384. serviceType . . . . . . . . . . . . . . . . . . . . . . 134
7.385. startType . . . . . . . . . . . . . . . . . . . . . . . 135
7.386. currentState . . . . . . . . . . . . . . . . . . . . . . 136
7.387. controlsAccepted . . . . . . . . . . . . . . . . . . . . 137
7.388. startName . . . . . . . . . . . . . . . . . . . . . . . 139
7.389. serviceFlag . . . . . . . . . . . . . . . . . . . . . . 139
7.390. dependencies . . . . . . . . . . . . . . . . . . . . . . 139
7.391. serviceeffectiverights . . . . . . . . . . . . . . . . . 139
7.392. trusteeSid . . . . . . . . . . . . . . . . . . . . . . . 140
7.393. serviceQueryConf . . . . . . . . . . . . . . . . . . . . 140
7.394. serviceChangeConf . . . . . . . . . . . . . . . . . . . 140
7.395. serviceQueryStat . . . . . . . . . . . . . . . . . . . . 140
7.396. serviceEnumDependents . . . . . . . . . . . . . . . . . 140
7.397. serviceStart . . . . . . . . . . . . . . . . . . . . . . 141
7.398. serviceStop . . . . . . . . . . . . . . . . . . . . . . 141
7.399. servicePause . . . . . . . . . . . . . . . . . . . . . . 141
7.400. serviceInterrogate . . . . . . . . . . . . . . . . . . . 141
7.401. serviceUserDefined . . . . . . . . . . . . . . . . . . . 141
7.402. sharedresourceauditedpermissions . . . . . . . . . . . . 142
7.403. netname . . . . . . . . . . . . . . . . . . . . . . . . 142
7.404. sharedresourceeffectiverights . . . . . . . . . . . . . 142
7.405. user . . . . . . . . . . . . . . . . . . . . . . . . . . 143
7.406. enabled . . . . . . . . . . . . . . . . . . . . . . . . 143
7.407. lastLogon . . . . . . . . . . . . . . . . . . . . . . . 143
7.408. groupSid . . . . . . . . . . . . . . . . . . . . . . . . 143
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 143
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 144
10. Security Considerations . . . . . . . . . . . . . . . . . . . 144
11. Operational Considerations . . . . . . . . . . . . . . . . . 145
11.1. Endpoint Designation . . . . . . . . . . . . . . . . . . 145
11.2. Timestamp Accuracy . . . . . . . . . . . . . . . . . . . 146
12. Privacy Considerations . . . . . . . . . . . . . . . . . . . 147
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 147
13.1. Normative References . . . . . . . . . . . . . . . . . . 147
13.2. Informative References . . . . . . . . . . . . . . . . . 148
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 149
A.1. Changes in Revision 01 . . . . . . . . . . . . . . . . . 149
A.2. Changes in Revision 02 . . . . . . . . . . . . . . . . . 150
A.3. Changes in Revision 03 . . . . . . . . . . . . . . . . . 150
A.4. Changes in Revision 04 . . . . . . . . . . . . . . . . . 151
A.5. Changes in Revision 05 . . . . . . . . . . . . . . . . . 151
A.6. Changes in Revision 06 . . . . . . . . . . . . . . . . . 151
A.7. Changes in Revision 07 . . . . . . . . . . . . . . . . . 152
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 152
1. Introduction 1. Introduction
The SACM Information Model (IM) serves multiple purposes: The SACM Information Model (IM) serves multiple purposes:
o to ensure interoperability between SACM data models that are used o to ensure interoperability between SACM data models that are used
as transport encodings, as transport encodings,
o to provide a standardized set of Information Elements - the SACM o to provide a standardized set of Information Elements - the SACM
Vocabulary - to enable the exchange of content vital to automated Vocabulary - to enable the exchange of content vital to automated
skipping to change at page 10, line 8 skipping to change at page 16, line 50
Information Elements have "current" Information Elements have "current"
status. The process for moving status. The process for moving
Information Elements to the Information Elements to the
"deprecated" status is TBD. "deprecated" status is TBD.
description (required): Describes the meaning of the description (required): Describes the meaning of the
Information Element, how it is Information Element, how it is
derived, conditions for its use, derived, conditions for its use,
etc. etc.
For Information Elements that structure (optional): A parsable property that provides
represent flags, please include details about the definition of
a table that lists each flag value structured Information Elements as
(hexadecimal) and description. The described in Section 5.2.
following is a template for that
table.
+-------+-----------------------+
| Value | Description |
+-------+-----------------------+
| | |
+-------+-----------------------+
references (optional): Identifies other RFCs or documents references (optional): Identifies other RFCs or documents
outside the IETF which provide outside the IETF which provide
additional information or context additional information or context
about the Information Element. about the Information Element.
Figure 2: Information Element Specification Template Figure 2: Information Element Specification Template
4.1. SACM Content Elements 4.1. Information Element Naming Convention
SACM Information Elements must adhere to the following naming
conventions.
o Names SHOULD be descriptive
o Names MUST be unique within the SACM registry. Enterprise-
specific names SHOULD be prefixed with a Private Enterprise Number
[PEN].
o Names MUST start with lowercase letters unless it begins with a
Private Enterprise Number
o Composed names MUST use capital letters for the first letter of
each part
4.2. SACM Content Elements
Every piece of information that is provided by a SACM component is Every piece of information that is provided by a SACM component is
always associated with a set of metadata, for example, the timestamp always associated with a set of metadata, for example, the timestamp
at which this set of information was produced (e.g. by a collection at which this set of information was produced (e.g. by a collection
task) or what target endpoint this set of information is about (e.g. task) or what target endpoint this set of information is about (e.g.
the data-source or a target endpoint identifier, respectively). The the data-source or a target endpoint identifier, respectively). The
subject that associates content IE with content-metadata IE is called subject that associates content IE with content-metadata IE is called
a content-element. Content metadata can also include relationships a content-element. Content metadata can also include relationships
that express associations with other content-elements. that express associations with other content-elements.
skipping to change at page 11, line 20 skipping to change at page 18, line 20
hostname = "arbutus", hostname = "arbutus",
coordinates = ( coordinates = (
latitude = N27.99619, latitude = N27.99619,
longitude = E86.92761 longitude = E86.92761
) )
) )
Figure 3: Example set of IEs associated with a timestamp and a target Figure 3: Example set of IEs associated with a timestamp and a target
endpoint label. endpoint label.
4.2. SACM Statements 4.3. SACM Statements
One or more SACM content elements are bundled in a SACM statement. One or more SACM content elements are bundled in a SACM statement.
In contrast to content-metadata, statement-metatdata focuses on the In contrast to content-metadata, statement-metadata focuses on the
providing SACM component instead of the target endpoint that the providing SACM component instead of the target endpoint that the
content is about. The only content-specific metadata included in the content is about. The only content-specific metadata included in the
SACM statement is the content-type IE. Therefore, multiple content- SACM statement is the content-type IE. Therefore, multiple content-
elements that share the same statement metadata and are of the same elements that share the same statement metadata and are of the same
content-type can be included in a single SACM statement. A SACM content-type can be included in a single SACM statement. A SACM
statement functions similar to an envelope or a header. Its purpose statement functions similar to an envelope or a header. Its purpose
is to enable the tracking of the origin of data inside a SACM domain is to enable the tracking of the origin of data inside a SACM domain
and more importantly to enable the mitigation of conflicting and more importantly to enable the mitigation of conflicting
information that my originate from different SACM components. How a information that may originate from different SACM components. How a
consuming SACM component actually deals with conflicting information consuming SACM component actually deals with conflicting information
is out-of-scope of the SACM IM. Semantically, the term statement is out-of-scope of the SACM IM. Semantically, the term statement
implies that the SACM content provided by a SACM component might not implies that the SACM content provided by a SACM component might not
be correct in every context, but rather is the result of an best- be correct in every context, but rather is the result of a best-
effort to produce correct information. effort to produce correct information.
sacm-statement = ( sacm-statement = (
statement-metadata = ( statement-metadata = (
publish-timestamp = 1461934031, publish-timestamp = 1461934031,
data-origin = 24e67957-3d31-4878-8892-da2b35e121c2, data-origin = 24e67957-3d31-4878-8892-da2b35e121c2,
content-type = observation content-type = observation
), ),
content-element = ( content-element = (
content-metadata = ( content-metadata = (
skipping to change at page 13, line 44 skipping to change at page 20, line 44
coordinates = ( coordinates = (
latitude = N16.67622, latitude = N16.67622,
longitude = E141.55321 longitude = E141.55321
) )
) )
) )
Figure 5: Example of conflicting information originating from Figure 5: Example of conflicting information originating from
different SACM components. different SACM components.
4.3. Relationships 4.4. Relationships
An IE can be associated with another IE, e.g. a user-name attribute An IE can be associated with another IE, e.g. a user-name attribute
can be associated with a content-authorization subject. These can be associated with a content-authorization subject. These
references are expressed via the relationships subject, which can be references are expressed via the relationships subject, which can be
included in a corresponding content-metadata subject. The included in a corresponding content-metadata subject. The
relationships subject includes a list of one or more references. The relationships subject includes a list of one or more references. The
SACM IM does not enforce a SACM domain to use unique identifiers as SACM IM does not enforce a SACM domain to use unique identifiers as
references. Therefore, there are at least two ways to reference references. Therefore, there are at least two ways to reference
another content-element: another
o The value of a reference represents a specific content-label that o The value of a reference represents a specific content-label that
is unique in a SACM domain (and has to be included in the is unique in a SACM domain (and has to be included in the
corresponding content-element metadata in order to be referenced), corresponding content-element metadata in order to be referenced),
or or
o The reference is a subject that includes an appropriate number of o The reference is a subject that includes an appropriate number of
IEs in order to identify the referenced content-element by its IEs in order to identify the referenced content-element by its
actual content. actual content.
It is recommended to provide unique identifiers in a SACM domain and It is recommended to provide unique identifiers in a SACM domain and
the SACM IM provides a corresponding naming-convention as a reference the SACM IM provides a corresponding naming-convention as a reference
in section FIXME. The alternative highlighted above summarizes a in Section 4.1. The alternative highlighted above summarizes a valid
valid approach that does not require unique identifiers and is approach that does not require unique identifiers and is similar to
similar to the approach of referencing target endpoints via the approach of referencing target endpoints via identifying
identifying attributes included in a characterization record (FIXME attributes included in a characterization record.
REF arch).
content-element = ( content-element = (
content-metadata = ( content-metadata = (
collection-timestamp = 1461934031, collection-timestamp = 1461934031,
te-label = te-label =
fb02e551-7101-4e68-8dec-1fde6bd10981 fb02e551-7101-4e68-8dec-1fde6bd10981
relationships = ( relationships = (
associated-with-user-account = associated-with-user-account =
f3d70ef4-7e18-42af-a894-8955ba87c95d f3d70ef4-7e18-42af-a894-8955ba87c95d
) )
skipping to change at page 15, line 5 skipping to change at page 22, line 5
), ),
user-account = ( user-account = (
username = romeo username = romeo
authentication = local authentication = local
) )
) )
Figure 6: Example instance of a content-element subject associated Figure 6: Example instance of a content-element subject associated
with another subject via its content metadata. with another subject via its content metadata.
4.4. Event 4.5. Event
Event subjects provide a structure to represent the change of IE Event subjects provide a structure to represent the change of IE
values that was detected by a collection task at a specific point of values that was detected by a collection task at a specific point of
time. It is mandatory to include the new values and the collection time. It is mandatory to include the new values and the collection
timestamp in an event subject and it is recommended to include the timestamp in an event subject and it is recommended to include the
past values and a collection timestamp that were replaced by the new past values and a collection timestamp that were replaced by the new
IE values. Every event can also be associated with a subject- IE values. Every event can also be associated with a subject-
specific event-timestamp and a lastseen-timestamp that might differ specific event-timestamp and a lastseen-timestamp that might differ
from the corresponding collection-timestamps. If these are omitted from the corresponding collection-timestamps. If these are omitted
the collection-timestamp that is included in the content-metadata the collection-timestamp that is included in the content-metadata
skipping to change at page 16, line 5 skipping to change at page 23, line 5
fb02e551-7101-4e68-8dec-1fde6bd10981, fb02e551-7101-4e68-8dec-1fde6bd10981,
event-component = current-state event-component = current-state
), ),
hostname = "lilac" hostname = "lilac"
) )
) )
) )
Figure 7: Example of a SACM statement containing an event. Figure 7: Example of a SACM statement containing an event.
4.5. Categories 4.6. Categories
Categories are special IEs that enable to refer to multiple types of Categories are special IEs that enable to refer to multiple types of
IE via just one name. Therefore, they are similar to a type-choice. IE via just one name. Therefore, they are similar to a type-choice.
A prominent example of a category is network-address. Network- A prominent example of a category is network-address. Network-
address is a category that every kind of network address is address is a category that every kind of network address is
associated with, e.g. mac-address, ipv4-address, ipv6-address, or associated with, e.g. mac-address, ipv4-address, ipv6-address, or
typed-network-address. If a subject includes network-address as one typed-network-address. If a subject includes network-address as one
of its components, any of the category members are valid to be used of its components, any of the category members are valid to be used
in its place. in its place.
Another prominent example is EndpointIdentifier. Some IEs can be Another prominent example is EndpointIdentifier. Some IEs can be
used to identify (and over time re-recognize) target endpoints - used to identify (and over time re-recognize) target endpoints -
those are associated with the category endpoint-identifier. those are associated with the category endpoint-identifier.
4.6. Designation
TODO: In the IETF, there are privacy concerns with respect to
endpoint identity and monitoring. As a result, the Endpoint ID
Design Team proposes that "endpoint identity" be changed to "endpoint
designation". Designation attributes can be used to correlate
endpoints, information about endpoints, events, etc. NOTE:
Designation attributes are just those that are mandatory-to-
implement. In practice, organizations may need to select additional
attributes beyond the mandatory-to-implement attributes to
successfully identify an endpoint on their network. Operational and
privacy concerns will be covered in Operational Considerations and
Privacy Considerations sections respectively. A proposal outlining
various options for representing designation attributes/objects in
the IPFIX syntax is being discussed on the mailing list. See IM
issue #39 at https://github.com/sacmwg/draft-ietf-sacm-information-
model/issues/39 for more information. Also, consider inserting table
that discusses the various properties of designation attributes and
include it in this section to help others determine whether or not a
new Information Element should be considered a designation attribute.
Lastly, explain how designation attributes can be used. For example,
letting a consumer identify an endpoint, for two purposes:
o To tell whether two endpoint attribute assertions concern the same
endpoint
o To respond to compliance measurements, for example by reporting,
remediating, and quarantining (SACM does not specify these
responses, but SACM exists to enable them.)
4.7. Privacy
TODO: In the IETF, there are privacy concerns with respect to
endpoint identity and monitoring. As a result, it was proposed that
a privacy property be included to denote when a Information Element
represents a privacy concern. A proposal outlining various options
for representing privacy attributes/objects in the IPFIX syntax is
being discussed on the mailing list. See IM issue #39 at
https://github.com/sacmwg/draft-ietf-sacm-information-model/issues/39
for more information.
5. Abstract Data Types 5. Abstract Data Types
This section describes the set of valid abstract data types that can This section describes the set of valid abstract data types that can
be used for the specification of the SACM Information Elements in be used for the specification of the SACM Information Elements in
Section 7. SACM currently supports two classes of datatypes that can Section 7. SACM currently supports two classes of datatypes that can
be used to define Information Elements. be used to define Information Elements.
o Simple: Datatypes that are atomic and are used to define the type o Simple: Datatypes that are atomic and are used to define the type
of data represented by an attribute Information Element. of data represented by an attribute Information Element.
skipping to change at page 17, line 48 skipping to change at page 24, line 4
o unsigned8, unsigned16, unsigned32, unsigned64 o unsigned8, unsigned16, unsigned32, unsigned64
o signed8, signed16, signed32, signed64 o signed8, signed16, signed32, signed64
o float32, float64 o float32, float64
o boolean o boolean
o macAddress o macAddress
o octetArray o octetArray
o string o string
o dateTimeSeconds, dateTimeMilliseconds, dateTimeMicroseconds, o dateTimeSeconds, dateTimeMilliseconds, dateTimeMicroseconds,
dateTimeNanoSeconds dateTimeNanoSeconds
o ipv4Address, ipv6Address o ipv4Address, ipv6Address
5.1.2. ciscoTrainSoftwareVersion
The type "ciscoTrainSoftwareVersion" represents a software version
that conforms to the Cisco IOS Train string format.
5.1.3. rpmSoftwareVersion
The type "rpmSoftwareVersion" represents a software version that
conforms to the EPOCH:VERSION-RELEASE format.
5.1.4. simpleSoftwareVersion
The type "simpleSoftwareVersion" represents a software version that
is a hierarchical list of non-negative integers separated by a single
character delimiter.
5.2. Structured Datatypes 5.2. Structured Datatypes
5.2.1. List Datatypes 5.2.1. List Datatypes
SACM defines the following abstract list data types that are used to SACM defines the following abstract list data types that are used to
represent the structured data associated with subjects. represent the structured data associated with subjects.
o list: indicates that the Information Element order is not o list: indicates that the Information Element order is not
significant but MAY be preserved. significant but MAY be preserved.
skipping to change at page 20, line 27 skipping to change at page 25, line 42
personInfo = (middleNames(middleName="Ronald", middleName=" Reuel"), personInfo = (middleNames(middleName="Ronald", middleName=" Reuel"),
lastName="Tolkien", firstName="John") lastName="Tolkien", firstName="John")
The instance below is not legal with respect to the definition The instance below is not legal with respect to the definition
of personInfo because the order in middleNames is not preserved. of personInfo because the order in middleNames is not preserved.
personInfo = (firstName="John", middleNames(middleName=" Reuel", personInfo = (firstName="John", middleNames(middleName=" Reuel",
middleName="Ronald"), lastName="Tolkien") middleName="Ronald"), lastName="Tolkien")
Figure 10: Example of Defining a Structured Datatype Figure 10: Example of Defining a Structured List Datatype
5.2.2. Enumeration Datatype
SACM defines the following abstract enumeration datatype that is used
to represent the restriction of an attribute value to a set of
values.
name, hex-value, description
<enumeration-def> -> -> <name> ";" <hex-value> ";" <description>
<name> -> [0-9a-zA-Z]+
<hex-value> -> 0x[0-9a-fA-F]+
<description> -> [0-9a-zA-Z\.\,]+
Figure 11: Syntax for Defining an Enumeration Datatype
Below is an example of a structured Information Element definition
for an enumeration.
Red ; 0x1 ; The color is red.
Orange ; 0x2 ; The color is orange.
Yellow ; 0x3 ; The color is yellow.
Green ; 0x4 ; The color is green.
...
Figure 12: Example of Defining a Structured Enumeration Datatype
6. Information Model Assets 6. Information Model Assets
In order to represent the Information Elements related to the areas In order to represent the Information Elements related to the areas
listed in Section 3.1, the information model defines the information listed in Section 3.1, the information model defines the information
needs (or metadata about those information needs) related to needs (or metadata about those information needs) related to
following types of assets which arse defined in following types of assets which are defined in
[I-D.ietf-sacm-terminology] (and included below for convenience) [I-D.ietf-sacm-terminology] (and included below for convenience)
which are of interest to SACM. Specifically: which are of interest to SACM. Specifically:
o Endpoint o Endpoint
o Software Component o Software Component
o Hardware Component o Hardware Component
o Identity o Identity
skipping to change at page 21, line 31 skipping to change at page 27, line 27
|! !| |! !|
|! !| |! !|
|! !| |! !|
|! !|____ |! !|____
|! !|0..1| |! !|0..1|
+-----+ | +-----+ |
|* | |* |
|_______| |_______|
in> in>
Figure 11: Model of an Endpoint Figure 13: Model of an Endpoint
6.1. Asset 6.1. Asset
As defined in [RFC4949], an asset is a system resource that is (a) As defined in [RFC4949], an asset is a system resource that is (a)
required to be protected by an information system's security policy, required to be protected by an information system's security policy,
(b) intended to be protected by a countermeasure, or (c) required for (b) intended to be protected by a countermeasure, or (c) required for
a system's mission. a system's mission.
In the scope of SACM, an asset can be composed of other assets. In the scope of SACM, an asset can be composed of other assets.
Examples of Assets include: Endpoints, Software, Guidance, or Examples of Assets include: Endpoints, Software, Guidance, or
skipping to change at page 23, line 15 skipping to change at page 29, line 7
6.4.1. Software Instance 6.4.1. Software Instance
A running instance of the software component (e.g. on a multi-user A running instance of the software component (e.g. on a multi-user
system, one logged-in user has one instance of a text editor running system, one logged-in user has one instance of a text editor running
and another logged-in user has another instance of the same text and another logged-in user has another instance of the same text
editor running, or on a single-user system, a user could have editor running, or on a single-user system, a user could have
multiple independent instances of the same text editor running). multiple independent instances of the same text editor running).
6.5. Identity 6.5. Identity
TODO: Define an Asset Identity asset. NOTE: Make sure it is clear Any mechanism that can be used to identify an asset during an
that this is not identity in the sense of what we have been saying authentication process. Examples include usernames, user and device
endpoint identity (now designation). certificates, etc. Note, that this is different than the identity of
assets in the context of designation as described in Section 11.1.
Examples of an identity include: username, user and device
certificates, etc.
6.6. Guidance 6.6. Guidance
TODO: Need to resolve the forms of Guidance in the terminology and
those listed as sub-sections below.
Guidance is input instructions to processes and tasks, such as Guidance is input instructions to processes and tasks, such as
collection or evaluation. Guidance influences the behavior of a SACM collection or evaluation. Guidance influences the behavior of a SACM
component and is considered content of the management plane. component and is considered content of the management plane.
Guidance can be manually or automatically generated or provided. Guidance can be manually or automatically generated or provided.
Typically, the tasks that provide guidance to SACM components have a Typically, the tasks that provide guidance to SACM components have a
low-frequency and tend to be be sporadic. A prominent example of low-frequency and tend to be sporadic. A prominent example of
guidance are target endpoint profiles, but guidance can have many guidance are target endpoint profiles,but guidance can have many
forms, including: forms, including:
Configuration, e.g. a SACM component's name, or a CMDB's IPv6 Configuration, e.g. a SACM component's name, or a CMDB's IPv6
address. address.
Profiles, e.g. a set of expected states for network behavior Profiles, e.g. a set of expected states for network behavior
associated with target endpoints employed by specific users. associated with target endpoints employed by specific users.
Policies, e.g. an interval to refresh the registration of a SACM Policies, e.g. an interval to refresh the registration of a SACM
component, or a list of required capabilities for SACM components component, or a list of required capabilities for SACM components
in a specific location. in a specific location.
6.6.1. Internal Collection Guidance 6.6.1. Collection Guidance
An internal collector may need guidance to govern what it collects A collector may need guidance to govern what it collects and when.
and when. Collection Guidance provides instructions for a Collector that
specifies which endpoint attributes to collect, when to collect them,
and how to collect them. Collection Guidance is composed of Target
Endpoint Attribute Guidance, Frequency Guidance, and Method Guidance.
6.6.2. External Collection Guidance o Target Endpoint Attribute Guidance: Set of endpoint attributes
that are supposed to be collected from a target endpoint. The
definition of the set of endpoint attributes is typically based on
an endpoint characterization record.
An external collector may need guidance to govern what it collects o Frequency Guidance: Specifies when endpoint attributes are to be
and when. collected.
6.6.3. Evaluation Guidance o Method Guidance: Indicates how endpoint attributes are to be
collected.
An evaluator typically needs Evaluation Guidance to govern what it 6.6.2. Evaluation Guidance
considers to be a good or bad security posture.
6.6.4. Retention Guidance An evaluator typically needs guidance to govern what it considers to
be a good or bad security posture. Evaluation Guidance provides
instructions for an Evaluator that specifies which endpoint
attributes to evaluate, the desired state of those endpoint
attributes, and any special requirements that enable an Evaluator to
determine if the endpoint attributes can be used in the evaluation
(e.g. freshness of data, how it was collected, etc.). Evaluation
Guidance is composed of Target Endpoint Attribute Guidance, Expected
Endpoint Attribute Value Guidance, and Frequency Guidance.
A SACM deployment may retain posture attributes, events, or o Target Endpoint Attribute Guidance: Set of target endpoint
evaluation results for some time. Retention supports ad hoc attributes that are supposed to be used in an evaluation as well
reporting and other use cases. as any requirements on the endpoint attributes. The definition of
the set of endpoint attributes is typically based on an endpoint
characterization record.
If information is retained, retention guidance controls what is o Expected Endpoint Attribute Value Guidance: The expected values of
retained and for how long. the endpoint attributes described in the Target Endpoint Attribute
Guidance.
If two or more pieces of retention guidance apply to a piece of o Frequency Guidance: Specifies when endpoint attributes are to be
information, the guidance calling for the longest retention should evaluated.
take precedence.
6.7. Evaluation Results o Method Guidance: Indicates how endpoint attributes are to be
collected.
Evaluation results are the resulting values from having evaluated a 6.6.3. Classification Guidance
set of posture attributes.
An example is: a NEA access recommendation [RFC5793]. A SACM Component carrying out the Target Endpoint Classification Task
may need guidance on how to classify an endpoint. Specifically, how
to associate endpoint classes with a specific target endpoint
characterization record. Target Endpoint Classes function as
guidance for collection, evaluation, remediation and security posture
assessment in general. Classification Guidance is composed of Target
Endpoint Attribute Guidance and Class Guidance.
An evaluator may be able to evaluate better if history is available. o Target Endpoint Attribute Guidance: Set of target endpoint
This is a use case for retaining Endpoint Attribute Assertions for a attributes that are supposed to be used to identify the endpoint
time. characterization record.
An Evaluation Result may be retained longer than the Endpoint o Class Guidance: A list of target endpoint classes that are to be
Attribute Assertions from which it derives (Figure 11 does not show associated with the identified target endpoint characterization
this). In the limiting case, Endpoint Attribute Assertions are not record.
retained. When an Endpoint Attribute Assertion arrives, an evaluator
produces an Evaluation Result. These mechanics are out of the scope 6.6.4. Storage Guidance
of the Information Model.
An SACM Component typically needs guidance to govern what information
it should store and where. Storage Guidance provides instructions
for a SACM Component that specifies which security automation
information should be stored, for how long, and on which endpoint.
Storage Guidance is composed of Target Endpoint Attribute Guidance,
Expected Security Automation Information Guidance, and Retention
Guidance.
o Target Endpoint Attribute Guidance: Set of target endpoint
attributes that are supposed to be used to identify the endpoint
where the security automation information is to be stored.
o Expected Security Automation Information Guidance: The security
automation information that is expected to be stored (guidance,
collected posture attributes, results, etc.).
o Retention Guidance: Specifies how long the security automation
information should be stored.
6.6.5. Evaluation Results
Evaluation Results are the output of comparing the actual state of an
endpoint against the expected state of an endpoint. In addition to
the actual results of the comparison, Evaluation Results should
include the Evaluation Guidance and actual target endpoint attributes
values used to perform the evaluation.
7. Information Model Elements 7. Information Model Elements
TODO: Define specific subjects, attributes, and metadata. We may This section defines the specific Information Elements and
want to consider adding small diagrams showing the relationships relationships that will be implemented by data models and transported
between each (see Lisa's notes: between SACM Components.
https://mailarchive.ietf.org/arch/msg/sacm/
kWxlnboHAXD87cned9WavwPZy5w). This may be too much work, but, not
sure yet.
7.1. hardwareSerialNumber 7.1. accessPrivilegeType
elementId: TBD
name: accessPrivilegeType
dataType: string
status: current
description: A set of types that represent access
privileges (read, write, none, etc.).
7.2. accountName
elementId: TBD
name: accountName
dataType: string
status: current
description: A label that uniquely identifies an account
that can require some form of (user) authentication to
access.
7.3. administrativeDomainType
elementId: TBD
name: accessPrivilegeType
dataType: string
status: current
description: A label the is supposed to uniquely
identify an administrative domain.
7.4. addressAssociationType
elementId: TBD
name: accessPrivilegeType
dataType: string
status: current
description: A label the is supposed to uniquely
identify an administrative domain.
7.5. addressMaskValue
elementId: TBD
name: addressMaskValue
dataType: string
status: current
description: A value that expresses a generic address
subnetting bitmask.
7.6. addressType
elementId: TBD
name: addressType
dataType: string
status: current
description: A set of types that specifies the type
of address that is expressed in an address subject
(e.g. ethernet, modbus, zigbee).
7.7. addressValue
elementId: TBD
name: addressValue
dataType: string
status: current
description: A value that expresses a generic network
address.
7.8. applicationComponent
elementId: TBD
name: applicationComponent
dataType: string
status: current
description: A label that references a "sub"-application
that is part of the application (e.g. an add-on, a
cipher-suite, a library).
7.9. applicationLabel
elementId: TBD
name: applicationLabel
dataType: string
status: current
description: A label that is supposed to uniquely
reference an application.
7.10. applicationType
elementId: TBD
name: applicationType
dataType: string
status: current
description: A set of types (FIXME maybe a finite set
is not realistic here - value not enumerator?) that
identifies the type of (user-space) application
(e.g. text-editor, policy-editor, service-client,
service-server, calender, rouge-like RPG).
7.11. applicationManufacturer
elementId: TBD
name: applicationManufacturer
dataType: string
status: current
description: The name of the vendor that created the
application.
7.12. authenticator
elementId: TBD
name: authenticator
dataType: string
status: current
description: A label that references a SACM component
that can authenticate target endpoints (can be used in
a target-endpoint subject to express that the target
endpoint was authenticated by that SACM component.
7.13. authenticationType
elementId: TBD
name: authenticationType
dataType: string
status: current
description: A set of types that expresses which type
of authentication was used to enable a network
interaction/connection.
7.14. birthdate
elementId: TBD
name: birthdate
dataType: string
status: current
description: A label for the registered day of birth
of a natural person (e.g. the date of birth of a person
as an ISO date string).
references: http://rs.tdwg.org/ontology/voc/Person#birthdate
7.15. bytesReceived
elementId: TBD
name: bytesReceived
dataType: string
status: current
description: A value that represents a number of octets
received on a network interface.
7.16. bytesSent
elementId: TBD
name: bytesSent
dataType: string
status: current
description: A value that represents the number of
octets received on a network interface.
7.17. bytesSent
elementId: TBD
name: bytesSent
dataType: string
status: current
description: A value that represents the number of
octets sent on a network interface.
7.18. certificate
elementId: TBD
name: certificate
dataType: string
status: current
description: A value that expresses a certificate that
can be collected from a target endpoint.
7.19. collectionTaskType
elementId: TBD
name: collectionTaskType
dataType: string
status: current
description: A set of types that defines how collected
SACM content was acquired (e.g. network-observation,
remote-acquisition, self-reported).
7.20. confidence
elementId: TBD
name: confidence
dataType: string
status: current
description: A representation of the subjective probability
that the assessed value is correct. If no confidence value
is given, it is assumed that the confidence is 1. Acceptable
values are between 0 and 1.
7.21. contentAction
elementId: TBD
name: contentAction
dataType: string
status: current
description: A set of types that express a type of
action (e.g. add, delete, update). It can be associated,
for instance, with an event subject or with a network
observation.
7.22. countryCode
elementId: TBD
name: countryCode
dataType: string
status: current
description: A set of types according to ISO 3166-1.
7.23. dataOrigin
elementId: TBD
name: dataOrigin
dataType: string
status: current
description: A label that uniquely identifies a SACM
component in and across SACM domains.
7.24. dataSource
elementId: TBD
name: dataSource
dataType: string
status: current
description: A label that is supposed to uniquely
identify the data source (e.g. a target endpoint or
sensor) that provided an initial endpoint attribute
record.
7.25. default-depth
elementId: TBD
name: default-depth
dataType: string
status: current
description: A value that expresses how often a circular
reference of subject is allowed to repeat, or how deep
a recursive nesting may occur, respectively.
7.26. discoverer
elementId: TBD
name: contentAction
dataType: string
status: current
description: A label that refers to the SACM component
that discovered a target endpoint (can be used in a
target-endpoint subject to express, for example, that
the target endpoint was authenticated by that SACM
component).
7.27. emailAddress
elementId: TBD
name: countryCode
dataType: string
status: current
description: A value that expresses an email-address.
7.28. eventType
elementId: TBD
name: eventType
dataType: string
status: current
description: a set of types that define the categories
of an event (e.g. access-level-change,
change-of-priviledge, change-of-authorization,
environmental-event, or provisioning-event).
7.29. eventThreshold
elementId: TBD
name: eventThreshold
dataType: string
status: current
description: if applicable, a value that can be
included in an event subject to indicate what numeric
threshold value was crossed to trigger that event.
7.30. eventThresholdName
elementId: TBD
name: eventThresholdName
dataType: string
status: current
description: If an event is created due to a crossed
threshold, the threshold might have a name associated
with it that can be expressed via this value.
7.31. eventTrigger
elementId: TBD
name: eventTrigger
dataType: string
status: current
description: This value is used to express more
complex trigger conditions that may cause the creation
of an event.
7.32. eventTrigger
elementId: TBD
name: eventTrigger
dataType: string
status: current
description: This value is used to express more
complex trigger conditions that may cause the creation
of an event.
7.33. firmwareId
elementId: TBD
name: firmwareId
dataType: string
status: current
description: A label that represents the BIOS or
firmware ID of a specific target endpoint.
7.34. hostName
elementId: TBD
name: hostName
dataType: string
status: current
description: A label typically associated with an
endpoint, but, not always intended to be unique given
scope.
7.35. interfaceLabel
elementId: TBD
name: interfaceLabel
dataType: string
status: current
description: A unique label that can be used to
reference a network interface.
7.36. ipv6AddressSubnetMask
elementId: TBD
name: ipv6AddressSubnetMask
dataType: string
status: current
description: An IPv6 subnet bitmask.
7.37. ipv6AddressSubnetMaskCidrNotation
elementId: TBD
name: ipv6AddressSubnetMaskCidrNotation
dataType: string
status: current
description: An IPv6 subnet bitmask in CIDR notation.
7.38. ipv6AddressValue
elementId: TBD
name: ipv6AddressValue
dataType: ipv6Address
status: current
description: An IPv6 subnet bitmask in CIDR notation.
a network interface.
7.39. ipv4AddressSubnetMask
elementId: TBD
name: ipv4AddressSubnetMask
dataType: string
status: current
description: An IPv4 subnet bitmask.
7.40. ipv4AddressSubnetMaskCidrNotation
elementId: TBD
name: ipv4AddressSubnetMaskCidrNotation
dataType: string
status: current
description: An IPv4 subnet bitmask in CIDR notation.
7.41. ipv4AddressValue
elementId: TBD
name: ipv4AddressValue
dataType: ipv4Address
status: current
description: An IPv4 address value.
7.42. layer2InterfaceType
elementId: TBD
name: layer2InterfaceType
dataType: string
status: current
description: A set of types referenced by IANA ifType.
7.43. layer4PortAddress
elementId: TBD
name: layer4PortAddress
dataType: unsigned32
status: current
description: A layer 4 port address
typically associated with TCP and UDP
protocols.
7.44. layer4Protocol
elementId: TBD
name: layer4Protocol
dataType: string
status: current
description: A set of types that express a layer 4
protocol (e.g. UDP or TCP).
7.45. locationName
elementId: TBD
name: locationName
dataType: string
status: current
description: A value that represents a named region of
physical space.
7.46. macAddressValue
elementId: TBD
name: macAddressValue
dataType: string
status: current
description: A value that expresses an Ethernet address.
7.47. methodLabel
elementId: TBD
name: methodLabel
dataType: string
status: current
description: A label that references a specific method
registered and used in a SACM domain (e.g. method to
match and re-identify target endpoints via identifying
attributes).
7.48. methodRepository
elementId: TBD
name: methodRepository
dataType: string
status: current
description: A label that references a SACM component
methods can be registered at and that can provide
guidance in the form of registered methods to other
SACM components.
7.49. networkAccessLevelType
elementId: TBD
name: networkAccessLevelType
dataType: string
status: current
description: A set of types that expresses categories
of network access-levels (e.g. block, quarantine, etc.).
7.50. networkId
elementId: TBD
name: networkId
dataType: string
status: current
description: Most networks such as AS, OSBF domains,
or VLANs can have an ID.
7.51. networkInterfaceName
elementId: TBD
name: networkInterfaceName
dataType: string
status: current
description: A label that uniquely identifies an interface
associated with a distinguishable endpoint.
7.52. networkLayer
elementId: TBD
name: networkLayer
dataType: string
status: current
description: A set of layers that expresses the specific
network layer an interface operates on.
7.53. networkName
elementId: TBD
name: networkName
dataType: string
status: current
description: A label that is associated with a network.
Some networks, for example, effetive layer2-broadcast-domains
are difficult to "grasp" and therefore quite difficult to name.
7.54. organizationId
elementId: TBD
name: organizationId
dataType: string
status: current
description: A label that uniquely identifies an
organization via a PEN.
7.55. osComponent
elementId: TBD
name: osComponent
dataType: string
status: current
description: A label that references a "sub-component"
that is part of the operating system (e.g. a kernel
module, microcode, or ACPI table).
7.56. osLabel
elementId: TBD
name: osLabel
dataType: string
status: current
description: A label that references a specific version
of an operating system, including patches and hotfixes.
7.57. osName
elementId: TBD
name: osName
dataType: string
status: current
description: The name of an operating system.
7.58. osType
elementId: TBD
name: osType
dataType: string
status: current
description: A set of types that identifies the type
of an operating system (e.g. real-time,
security-enhanced, consumer, server).
7.59. osVersion
elementId: TBD
name: osVersion
dataType: string
status: current
description: A value that represents the version of
an operating-system.
7.60. patchId
elementId: TBD
name: patchId
dataType: string
status: current
description: A label the uniquely identifies a specific
software patch.
7.61. patchName
elementId: TBD
name: osVersion
dataType: string
status: current
description: The vendor's name of a software patch.
7.62. personFirstName
elementId: TBD
name: patchId
dataType: string
status: current
description: The first name of a natural person.
7.63. personLastName
elementId: TBD
name: personLastName
dataType: string
status: current
description: The last name of a natural person.
7.64. personMiddleName
elementId: TBD
name: personMiddleName
dataType: string
status: current
description: The middle name of a natural person.
7.65. phoneNumber
elementId: TBD
name: phoneNumber
dataType: string
status: current
description: A label that expresses the U.S. national
phone number (e.g. pattern value="((\d{3}) )?\d{3}-\d{4}").
7.66. phoneNumberType
elementId: TBD
name: phoneNumberType
dataType: string
status: current
description: A set of types that express the type of
a phone number (e.g. DSN, Fax, Home, Mobile, Pager,
Secure, Unsecure, Work, Other).
7.67. privilegeName
elementId: TBD
name: privilegeName
dataType: string
status: current
description: The attribute name of the privilege
represented as an AVP.
7.68. privilegeValue
elementId: TBD
name: privilegeValue
dataType: string
status: current
description: The value content of the privilege
represented as an AVP.
7.69. protocol
elementId: TBD
name: protocol
dataType: string
status: current
description: A set of types that defines specific
protocols above layer 4 (e.g. http, https, dns, ipp,
or unknown).
7.70. publicKey
elementId: TBD
name: publicKey
dataType: string
status: current
description: The value of a public key (regardless of its
method of creation, crypto-system, or signature scheme)
that can be collected from a target endpoint.
7.71. relationshipContentElementGuid
elementId: TBD
name: relationshipContentElementGuid
dataType: string
status: current
description: A reference to a specific content element
used in a relationship subject.
7.72. relationshipStatementElementGuid
elementId: TBD
name: relationshipStatementElementGuid
dataType: string
status: current
description: A reference to a specific SACM statement
used in a relationship subject.
7.73. relationshipObjectLabel
elementId: TBD
name: relationshipObjectLabel
dataType: string
status: current
description: A reference to a specific label used in
content (e.g. a te-label or a user-id). This
reference is typically used if matching content
attribute can be done efficiantly and can also be
included in addition to a relationship-content-element-guid
reference.
7.74. relationshipType
elementId: TBD
name: relationshipType
dataType: string
status: current
description: A set of types that is in every instance
of a relationship subject to highlight what kind of
relationship exists between the subject the relationship
is included in (e.g. associated_with_user,
applies_to_session, seen_on_interface, associated_with_flow,
contains_virtual_device).
7.75. roleName
elementId: TBD
name: roleName
dataType: string
status: current
description: A label that references a collection of
privileges assigned to a specific entity (identity?
FIXME).
7.76. sessionStateType
elementId: TBD
name: sessionStateType
dataType: string
status: current
description: A set of types a discernible session (an
ongoing network interaction) can be in (e.g.
Authenticating, Authenticated, Postured, Started,
Disconnected).
7.77. statementGuid
elementId: TBD
name: statementGuid
dataType: string
status: current
description: A label that expresses a global unique
ID referencing a specific SACM statement that was
produced by a SACM component.
7.78. statementType
elementId: TBD
name: statementType
dataType: string
status: current
description: A set of types that define the type of
content that is included in a SACM statement (e.g.
Observation, DirectoryContent, Correlation, Assessment,
Guidance).
7.79. status
elementId: TBD
name: status
dataType: string
status: current
description: A set of types that defines possible
result values for a finding in general (e.g. true,
false, error, unknown, not applicable, not evaluated).
7.80. subAdministrativeDomain
elementId: TBD
name: subAdministrativeDomain
dataType: string
status: current
description: A label for related child domains an
administrative domain can be composed of (used in the
subject administrative-domain)
7.81. subInterfaceLabel
elementId: TBD
name: subInterfaceLabel
dataType: string
status: current
description: A unique label a sub network interface
(e.g. a tagged vlan on a trunk) can be referenced
with.
7.82. superAdministrativeDomain
elementId: TBD
name: superAdministrativeDomain
dataType: string
status: current
description: a label for related parent domains an
administrative domain is part of (used
in the subject s.administrative-domain).
7.83. superInterfaceLabel
elementId: TBD
name: superInterfaceLabel
dataType: string
status: current
description: a unique label a super network interface
(e.g. a physical interface a tunnel
interface terminates on) can be referenced
with.
7.84. teAssessmentState
elementId: TBD
name: teAssessmentState
dataType: string
status: current
description: a set of types that defines the state of
assessment of a target-endpoint (e.g.
in-discovery, discovered, in-classification,
classified, in-assessment, assessed).
7.85. teLabel
elementId: TBD
name: teLabel
dataType: string
status: current
description: an identifying label created from a set
of identifying attributes used to reference
a specific target endpoint.
7.86. teId
elementId: TBD
name: teId
dataType: string
status: current
description: an identifying label that is created
randomly, is supposed to be unique, and
used to reference a specific target
endpoint.
7.87. timestampType
elementId: TBD
name: timestampType
dataType: string
status: current
description: a set of types that express what type of
action or event happened at that point
of time (e.g. discovered, classified,
collected, published). Can be included in
a generic s.timestamp subject.
7.88. unitsReceived
elementId: TBD
name: unitsReceived
dataType: string
status: current
description: a value that represents a number of units
(e.g. frames, packets, cells or segments)
received on a network interface.
7.89. unitsSent
elementId: TBD
name: unitsSent
dataType: string
status: current
description: a value that represents a number of units
(e.g. frames, packets, cells or segments)
sent on a network interface.
7.90. username
elementId: TBD
name: username
dataType: string
status: current
description: a part of the credentials required to
access an account that can be collected from a target
endpoint.
7.91. userDirectory
elementId: TBD
name: userDirectory
dataType: string
status: current
description: a label that identifies a specific type
of user-directory (e.g. ldap, active-directory,
local-user).
7.92. userId
elementId: TBD
name: userId
dataType: string
status: current
description: a label that references a specific user
known in a SACM domain.
7.93. webSite
elementId: TBD
name: webSite
dataType: string
status: current
description: a URI that references a web-site.
7.94. WGS84Longitude
elementId: TBD
name: WGS84Longitude
dataType: float
status: current
description: a label that represents WGS 84 rev 2004
longitude.
7.95. WGS84Latitude
elementId: TBD
name: WGS84Latitude
dataType: float
status: current
description: a label that represents WGS 84 rev 2004
latitude.
7.96. WGS84Altitude
elementId: TBD
name: WGS84Altitude
dataType: float
status: current
description: a label that represents WGS 84 rev 2004
altitude.
7.97. hardwareSerialNumber
elementId: TBD elementId: TBD
name: hardwareSerialNumber name: hardwareSerialNumber
dataType: string dataType: string
status: current status: current
description: A globally unique identifier for a particular description: A globally unique identifier for a particular
piece of hardware assigned by the vendor. piece of hardware assigned by the vendor.
7.2. interfaceName 7.98. interfaceName
elementId: TBD elementId: TBD
name: interfaceName name: interfaceName
dataType: string dataType: string
status: current status: current
description: A short name uniquely describing an interface, description: A short name uniquely describing an interface,
eg "Eth1/0". See [RFC2863] for the definition eg "Eth1/0". See [RFC2863] for the definition
of the ifName object. of the ifName object.
7.3. interfaceIndex 7.99. interfaceIndex
elementId: TBD elementId: TBD
name: interfaceIndex name: interfaceIndex
dataType: unsigned32 dataType: unsigned32
status: current status: current
description: The index of an interface installed on an endpoint. description: The index of an interface installed on an endpoint.
The value matches the value of managed object The value matches the value of managed object
'ifIndex' as defined in [RFC2863]. Note that ifIndex 'ifIndex' as defined in [RFC2863]. Note that ifIndex
values are not assigned statically to an interface values are not assigned statically to an interface
and that the interfaces may be renumbered every time and that the interfaces may be renumbered every time
the device's management system is re-initialized, the device's management system is re-initialized,
as specified in [RFC2863]. as specified in [RFC2863].
7.4. interfaceMacAddress 7.100. interfaceMacAddress
elementId: TBD elementId: TBD
name: interfaceMacAddress name: interfaceMacAddress
dataType: macAddress dataType: macAddress
status: current status: current
description: The IEEE 802 MAC address associated with a network description: The IEEE 802 MAC address associated with a network
interface on an endpoint. interface on an endpoint.
7.5. interfaceType 7.101. interfaceType
elementId: TBD elementId: TBD
name: interfaceType name: interfaceType
dataType: unsigned32 dataType: unsigned32
status: current status: current
description: The type of a network interface. The value matches description: The type of a network interface. The value matches
the value of managed object 'ifType' as defined in the value of managed object 'ifType' as defined in
[IANA registry ianaiftype-mib]. [IANA registry ianaiftype-mib].
7.6. interfaceFlags 7.102. interfaceFlags
elementId: TBD
name: interfaceFlags
dataType: unsigned16
status: current
description: This information element specifies the flags
associated with a network interface. Possible
values include:
+-------+----------------------------------+ elementId: TBD
| Value | Description | name: interfaceFlags
+-------+----------------------------------+ dataType: unsigned16
| 0x1 | interface is up | status: current
| 0x2 | broadcast address valid | description: This information element specifies the flags
| 0x4 | turn on debugging | associated with a network interface. Possible
| 0x8 | is a loopback net | values include:
| 0x10 | interface is point-to-point link | structure: Up ; 0x1 ; Interface is up.
| 0x20 | avoid use of trailers | Broadcast ; 0x2 ; Broadcast address valid.
| 0x40 | resources allocated | Debug ; 0x4 ; Turn on debugging.
| 0x80 | no address resolution protocol | Loopback ; 0x8 ; Is a loopback net.
| 0x100 | receive all packets | Point-to-point ; 0x10 ; Interface is point-to-point link.
+-------+----------------------------------+ No trailers ; 0x20 ; Avoid use of trailers.
Resources allocated ; 0x40 ; Resources allocated.
No ARP ; 0x80 ; No address resolution protocol.
Receive all ; 0x100 ; Receive all packets.
7.7. networkInterface 7.103. networkInterface
elementId: TBD elementId: TBD
name: networkInterface name: networkInterface
dataType: orderedList(interfaceName, interfaceIndex, macAddress, dataType: orderedList
ifType, flags)
status: current status: current
description: Information about a network interface description: Information about a network interface
installed on an endpoint. The installed on an endpoint. The
following high-level digram following high-level digram
describes the structure of describes the structure of
networkInterface information networkInterface information
element. element.
structure: orderedList(interfaceName, interfaceIndex, macAddress,
ifType, flags)
7.8. softwareIdentifier 7.104. softwareIdentifier
elementId: TBD elementId: TBD
name: softwareIdentifier name: softwareIdentifier
dataType: string dataType: string
status: current status: current
description: A globally unique identifier for a particular description: A globally unique identifier for a particular
software application. software application.
7.9. softwareTitle 7.105. softwareTitle
elementId: TBD elementId: TBD
name: softwareTitle name: softwareTitle
dataType: string dataType: string
status: current status: current
description: The title of the software application. description: The title of the software application.
7.10. softwareCreator 7.106. softwareCreator
elementId: TBD elementId: TBD
name: softwareCreator name: softwareCreator
dataType: string dataType: string
status: current status: current
description: The software developer (e.g., vendor or author). description: The software developer (e.g., vendor or author).
7.11. simpleSoftwareVersion 7.107. simpleSoftwareVersion
elementId: TBD elementId: TBD
name: simpleSoftwareVersion name: simpleSoftwareVersion
dataType: simpleVersion dataType: string
status: current status: current
description: The version string for a software application that description: The version string for a software application that
follows the simple versioning scheme. conforms to the format of a list of hierarchical
non-negative integers separated by a single character
delimiter format.
7.12. rpmSoftwareVersion 7.108. rpmSoftwareVersion
elementId: TBD elementId: TBD
name: rpmSoftwareVersion name: rpmSoftwareVersion
dataType: rpmVersion dataType: string
status: current status: current
description: The version string for a software application that description: The version string for a software application that
follows the RPM versioning scheme. conforms to the EPOCH:VERSION-RELEASE format.
7.109. ciscoTrainSoftwareVersion
7.13. ciscoTrainSoftwareVersion
elementId: TBD elementId: TBD
name: ciscoTrainSoftwareVersion name: ciscoTrainSoftwareVersion
dataType: ciscoTrainVersion dataType: string
status: current status: current
description: The version string for a software application that description: The version string for a software application that
follows the Cisco Train Release versioning scheme. conforms to the Cisco IOS Train string format.
7.14. softwareVersion 7.110. softwareVersion
elementId: TBD elementId: TBD
name: softwareVerison name: softwareVerison
dataType: list(simpleSoftwareVersion | rpmSoftwareVersion | dataType: list
ciscoTrainSoftwareVersion)
status: current status: current
description: The version of the software application. Software description: The version of the software application. Software
applications may be versioned using a number of applications may be versioned using a number of
schemas. The following high-level digram describes schemas. The following high-level digram describes
the structure of the softwareVersion information the structure of the softwareVersion information
element. element.
structure: list(simpleSoftwareVersion | rpmSoftwareVersion |
ciscoTrainSoftwareVersion)
7.15. lastUpdated 7.111. lastUpdated
elementId: TBD elementId: TBD
name: lastUpdated name: lastUpdated
dataType: dateTimeSeconds dataType: dateTimeSeconds
status: current status: current
description: The date and time when the software instance description: The date and time when the software instance
was last updated on the system (e.g., new was last updated on the system (e.g., new
version instlalled or patch applied) version instlalled or patch applied)
7.16. softwareInstance 7.112. softwareInstance
elementId: TBD elementId: TBD
name: softwareInstance name: softwareInstance
dataType: orderedList(softwareIdentifier, title, creator, dataType: orderedList
softwareVersion, lastUpdated)
status: current status: current
description: Information about an instance of software description: Information about an instance of software
installed on an endpoint. The following installed on an endpoint. The following
high-level digram describes the structure of high-level digram describes the structure of
softwareInstance information element. softwareInstance information element.
structure: orderedList(softwareIdentifier, title, creator,
softwareVersion, lastUpdated)
7.113. globallyUniqueIdentifier
7.17. globallyUniqueIdentifier
elementId: TBD elementId: TBD
name: globallyUniqueIdentifier name: globallyUniqueIdentifier
dataType: unsigned8 dataType: unsigned8
status: current status: current
metadata: true metadata: true
description: TODO. description: TODO.
7.18. dataOrigin 7.114. dataOrigin
elementId: TBD elementId: TBD
name: dataOrigin name: dataOrigin
dataType: string dataType: string
status: current status: current
metadata: true metadata: true
description: The origin of the data. TODO make a better description: The origin of the data.
description.
7.19. dataSource 7.115. dataSource
elementId: TBD elementId: TBD
name: dataSource name: dataSource
dataType: string dataType: string
status: current status: current
metadata: true metadata: true
description: The source of the data. TODO make a better description: The source of the data.
description.
7.20. creationTimestamp 7.116. creationTimestamp
elementId: TBD elementId: TBD
name: creationTimestamp name: creationTimestamp
dataType: dateTimeSeconds dataType: dateTimeSeconds
status: current status: current
metadata: true metadata: true
description: The date and time when the posture description: The date and time when the posture
information was created by a SACM Component. information was created by a SACM Component.
7.21. collectionTimestamp 7.117. collectionTimestamp
elementId: TBD elementId: TBD
name: collectionTimestamp name: collectionTimestamp
dataType: dateTimeSeconds dataType: dateTimeSeconds
status: current status: current
metadata: true metadata: true
description: The date and time when the posture description: The date and time when the posture
information was collected or observed by a SACM information was collected or observed by a SACM
Component. Component.
7.22. publicationTimestamp 7.118. publicationTimestamp
elementId: TBD elementId: TBD
name: publicationTimestamp name: publicationTimestamp
dataType: dateTimeSeconds dataType: dateTimeSeconds
status: current status: current
metadata: true metadata: true
description: The date and time when the posture description: The date and time when the posture
information was published. information was published.
7.23. relayTimestamp 7.119. relayTimestamp
elementId: TBD elementId: TBD
name: relayTimestamp name: relayTimestamp
dataType: dateTimeSeconds dataType: dateTimeSeconds
status: current status: current
metadata: true metadata: true
description: The date and time when the posture description: The date and time when the posture
information was relayed to another SACM Component. information was relayed to another SACM Component.
7.24. storageTimestamp 7.120. storageTimestamp
elementId: TBD elementId: TBD
name: storageTimestamp name: storageTimestamp
dataType: dateTimeSeconds dataType: dateTimeSeconds
status: current status: current
metadata: true metadata: true
description: The date and time when the posture description: The date and time when the posture
information was stored in a Repository. information was stored in a Repository.
7.25. type 7.121. type
elementId: TBD elementId: TBD
name: type name: type
dataType: unsigned16 dataType: enumeration
status: current status: current
metadata: true metadata: true
description: The type of data model use to represent description: The type of data model use to represent
some set of endpoint information. The following some set of endpoint information. The following
table lists the set of data models supported by SACM. table lists the set of data models supported by SACM.
structure: TBD
+-------+----------------------------------+ 7.122. protocolIdentifier
| Value | Description |
+-------+----------------------------------+
| 0x00 | Data Model 1 |
+-------+----------------------------------+
| 0x01 | Data Model 2 |
+-------+----------------------------------+
| 0x02 | Data Model 3 |
+-------+----------------------------------+
|... | ... |
+-------+----------------------------------+
7.26. protocolIdentifier
elementId: TBD elementId: TBD
name: protocolIdentifier name: protocolIdentifier
dataType: unsigned8 dataType: unsigned8
status: current status: current
description: The value of the protocol number in the IP packet description: The value of the protocol number in the IP packet
header. The protocol number identifies the IP packet header. The protocol number identifies the IP packet
payload type. Protocol numbers are defined in the payload type. Protocol numbers are defined in the
IANA Protocol Numbers registry. IANA Protocol Numbers registry.
In Internet Protocol version 4 (IPv4), this is In Internet Protocol version 4 (IPv4), this is
carried in the Protocol field. In Internet Protocol carried in the Protocol field. In Internet Protocol
version 6 (IPv6), this is carried in the Next Header version 6 (IPv6), this is carried in the Next Header
field in the last extension header of the packet. field in the last extension header of the packet.
7.27. sourceTransportPort 7.123. sourceTransportPort
elementId: TBD elementId: TBD
name: sourceTransportPort name: sourceTransportPort
dataType: unsigned16 dataType: unsigned16
status: current status: current
description: The source port identifier in the transport header. description: The source port identifier in the transport header.
For the transport protocols UDP, TCP, and SCTP, this For the transport protocols UDP, TCP, and SCTP, this
is the source port number given in the respective is the source port number given in the respective
header. This field MAY also be used for future header. This field MAY also be used for future
transport protocols that have 16-bit source port transport protocols that have 16-bit source port
identifiers. identifiers.
7.28. sourceIPv4PrefixLength 7.124. sourceIPv4PrefixLength
elementId: TBD elementId: TBD
name: sourceIPv4PrefixLength name: sourceIPv4PrefixLength
dataType: unsigned8 dataType: unsigned8
status: current status: current
description: The number of contiguous bits that are relevant in description: The number of contiguous bits that are relevant in
the sourceIPv4Prefix Information Element. the sourceIPv4Prefix Information Element.
7.29. ingressInterface 7.125. ingressInterface
elementId: TBD elementId: TBD
name: ingressInterface name: ingressInterface
dataType: unsigned32 dataType: unsigned32
status: current status: current
description: The index of the IP interface where packets of this description: The index of the IP interface where packets of this
Flow are being received. The value matches the Flow are being received. The value matches the
value of managed object 'ifIndex' as defined in value of managed object 'ifIndex' as defined in
[RFC2863]. Note that ifIndex values are not assigned [RFC2863]. Note that ifIndex values are not assigned
statically to an interface and that the interfaces statically to an interface and that the interfaces
may be renumbered every time the device's management may be renumbered every time the device's management
system is re-initialized, as specified in [RFC2863]. system is re-initialized, as specified in [RFC2863].
7.30. destinationTransportPort 7.126. destinationTransportPort
elementId: TBD elementId: TBD
name: destinationTransportPort name: destinationTransportPort
dataType: unsigned16 dataType: unsigned16
status: current status: current
description: The destination port identifier in the transport description: The destination port identifier in the transport
header. For the transport protocols UDP, TCP, and header. For the transport protocols UDP, TCP, and
SCTP, this is the destination port number given in SCTP, this is the destination port number given in
the respective header. This field MAY also be used the respective header. This field MAY also be used
for future transport protocols that have 16-bit for future transport protocols that have 16-bit
destination port identifiers. destination port identifiers.
7.31. sourceIPv6PrefixLength 7.127. sourceIPv6PrefixLength
elementId: TBD elementId: TBD
name: sourceIPv6PrefixLength name: sourceIPv6PrefixLength
dataType: unsigned8 dataType: unsigned8
status: current status: current
description: The number of contiguous bits that are relevant in description: The number of contiguous bits that are relevant in
the sourceIPv6Prefix Information Element. the sourceIPv6Prefix Information Element.
7.32. sourceIPv4Prefix 7.128. sourceIPv4Prefix
elementId: TBD elementId: TBD
name: sourceIPv4Prefix name: sourceIPv4Prefix
dataType: ipv4Address dataType: ipv4Address
status: current status: current
description: IPv4 source address prefix. description: IPv4 source address prefix.
7.33. destinationIPv4Prefix 7.129. destinationIPv4Prefix
elementId: TBD elementId: TBD
name: destinationIPv4Prefix name: destinationIPv4Prefix
dataType: ipv4Address dataType: ipv4Address
status: current status: current
description: IPv4 destination address prefix. description: IPv4 destination address prefix.
7.34. sourceMacAddress 7.130. sourceMacAddress
elementId: TBD elementId: TBD
name: sourceMacAddress name: sourceMacAddress
dataType: macAddress dataType: macAddress
status: current status: current
description: The IEEE 802 source MAC address field. description: The IEEE 802 source MAC address field.
7.35. ipVersion 7.131. ipVersion
elementId: TBD elementId: TBD
name: ipVersion name: ipVersion
dataType: unsigned8 dataType: unsigned8
status: current status: current
description: The IP version field in the IP packet header. description: The IP version field in the IP packet header.
7.36. interfaceDescription 7.132. interfaceDescription
elementId: TBD elementId: TBD
name: interfaceDescription name: interfaceDescription
dataType: string dataType: string
status: current status: current
description: The description of an interface, eg "FastEthernet description: The description of an interface, eg "FastEthernet
1/0" or "ISP 1/0" or "ISP
connection". connection".
7.37. applicationDescription 7.133. applicationDescription
elementId: TBD elementId: TBD
name: applicationDescription name: applicationDescription
dataType: string dataType: string
status: current status: current
description: Specifies the description of an application. description: Specifies the description of an application.
7.38. applicationId 7.134. applicationId
elementId: TBD elementId: TBD
name: applicationId name: applicationId
dataType: octetArray dataType: octetArray
status: current status: current
description: Specifies an Application ID per [RFC6759]. description: Specifies an Application ID per [RFC6759].
7.39. applicationName 7.135. applicationName
elementId: TBD elementId: TBD
name: applicationName name: applicationName
dataType: string dataType: string
status: current status: current
description: Specifies the name of an application. description: Specifies the name of an application.
7.40. exporterIPv4Address 7.136. exporterIPv4Address
elementId: TBD elementId: TBD
name: exporterIPv4Address name: exporterIPv4Address
dataType: ipv4Address dataType: ipv4Address
status: current status: current
description: The IPv4 address used by the Exporting Process. description: The IPv4 address used by the Exporting Process.
This is used by the Collector to identify the This is used by the Collector to identify the
Exporter in cases where the identity of the Exporter Exporter in cases where the identity of the Exporter
may have been obscured by the use of a proxy. may have been obscured by the use of a proxy.
7.41. exporterIPv6Address 7.137. exporterIPv6Address
elementId: TBD elementId: TBD
name: exporterIPv6Address name: exporterIPv6Address
dataType: ipv6Address dataType: ipv6Address
status: current status: current
description: The IPv6 address used by the Exporting Process. description: The IPv6 address used by the Exporting Process.
This is used by the Collector to identify the This is used by the Collector to identify the
Exporter in cases where the identity of the Exporter in cases where the identity of the
Exporter may have been obscured by the use of a Exporter may have been obscured by the use of a
proxy. proxy.
7.42. portId 7.138. portId
elementId: TBD elementId: TBD
name: portId name: portId
dataType: unsigned32 dataType: unsigned32
status: current status: current
description: An identifier of a line port that is unique per description: An identifier of a line port that is unique per
IPFIX Device hosting an Observation Point. IPFIX Device hosting an Observation Point.
Typically, this Information Element is used for Typically, this Information Element is used for
limiting the scope of other Information Elements. limiting the scope of other Information Elements.
7.43. templateId 7.139. templateId
elementId: TBD elementId: TBD
name: templateId name: templateId
dataType: unsigned16 dataType: unsigned16
status: current status: current
description: An identifier of a Template that is locally unique description: An identifier of a Template that is locally unique
within a combination of a Transport session and an within a combination of a Transport session and an
Observation Domain. Observation Domain.
Template IDs 0-255 are reserved for Template Sets, Template IDs 0-255 are reserved for Template Sets,
Options Template Sets, and other reserved Sets yet Options Template Sets, and other reserved Sets yet
to be created. Template IDs of Data Sets are to be created. Template IDs of Data Sets are
numbered from 256 to 65535. numbered from 256 to 65535.
Typically, this Information Element is used for Typically, this Information Element is used for
limiting the scope of other Information Elements. limiting the scope of other Information Elements.
Note that after a re-start of the Exporting Process Note that after a re-start of the Exporting Process
Template identifiers may be re-assigned. Template identifiers may be re-assigned.
7.44. collectorIPv4Address 7.140. collectorIPv4Address
elementId: TBD elementId: TBD
name: collectorIPv4Address name: collectorIPv4Address
dataType: ipv4Address dataType: ipv4Address
status: current status: current
description: An IPv4 address to which the Exporting Process sends description: An IPv4 address to which the Exporting Process sends
Flow information. Flow information.
7.45. collectorIPv6Address 7.141. collectorIPv6Address
elementId: TBD elementId: TBD
name: collectorIPv6Address name: collectorIPv6Address
dataType: ipv6Address dataType: ipv6Address
status: current status: current
description: An IPv6 address to which the Exporting Process sends description: An IPv6 address to which the Exporting Process sends
Flow information. Flow information.
7.46. informationElementIndex 7.142. informationElementIndex
elementId: TBD elementId: TBD
name: informationElementIndex name: informationElementIndex
dataType: unsigned16 dataType: unsigned16
status: current status: current
description: A zero-based index of an Information Element description: A zero-based index of an Information Element
referenced by informationElementId within a Template referenced by informationElementId within a Template
referenced by templateId; used to disambiguate referenced by templateId; used to disambiguate
scope for templates containing multiple identical scope for templates containing multiple identical
Information Elements. Information Elements.
7.47. informationElementId 7.143. informationElementId
elementId: TBD elementId: TBD
name: informationElementId name: informationElementId
dataType: unsigned16 dataType: unsigned16
status: current status: current
description: This Information Element contains the ID of another description: This Information Element contains the ID of another
Information Element. Information Element.
7.48. informationElementDataType 7.144. informationElementDataType
elementId: TBD elementId: TBD
name: informationElementDataType name: informationElementDataType
dataType: unsigned8 dataType: unsigned8
status: current status: current
description: A description of the abstract data type of an IPFIX description: A description of the abstract data type of an IPFIX
information element.These are taken from the information element.These are taken from the
abstract data types defined in section 3.1 of the abstract data types defined in section 3.1 of the
IPFIX Information Model [RFC5102]; see that section IPFIX Information Model [RFC5102]; see that section
for more information on the types described in the for more information on the types described in the
informationElementDataType sub-registry. informationElementDataType sub-registry.
These types are registered in the IANA IPFIX These types are registered in the IANA IPFIX
Information Element Data Type subregistry. This Information Element Data Type subregistry. This
subregistry is intended to assign numbers for type subregistry is intended to assign numbers for type
names, not to provide a mechanism for adding data names, not to provide a mechanism for adding data
types to the IPFIX Protocol, and as such requires a types to the IPFIX Protocol, and as such requires a
Standards Action [RFC5226] to modify. Standards Action [RFC5226] to modify.
7.49. informationElementDescription 7.145. informationElementDescription
elementId: TBD elementId: TBD
name: informationElementDescription name: informationElementDescription
dataType: string dataType: string
status: current status: current
description: A UTF-8 [RFC3629] encoded Unicode string containing description: A UTF-8 [RFC3629] encoded Unicode string containing
a human-readable description of an Information a human-readable description of an Information
Element. The content of the Element. The content of the
informationElementDescription MAY be annotated with informationElementDescription MAY be annotated with
one or more language tags [RFC4646], encoded one or more language tags [RFC4646], encoded
in-line [RFC2482] within the UTF-8 string, in order in-line [RFC2482] within the UTF-8 string, in order
to specify the language in which the description is to specify the language in which the description is
written. Description text in multiple languages MAY written. Description text in multiple languages MAY
tag each section with its own language tag; in this tag each section with its own language tag; in this
case, the description information in each language case, the description information in each language
SHOULD have equivalent meaning. In the absence of SHOULD have equivalent meaning. In the absence of
any language tag, the "i-default" [RFC2277] language any language tag, the "i-default" [RFC2277] language
SHOULD be assumed. See the Security Considerations SHOULD be assumed. See the Security Considerations
section for notes on string handling for Information section for notes on string handling for Information
Element type records. Element type records.
7.50. informationElementName 7.146. informationElementName
elementId: TBD elementId: TBD
name: informationElementName name: informationElementName
dataType: string dataType: string
status: current status: current
description: A UTF-8 [RFC3629] encoded Unicode string containing description: A UTF-8 [RFC3629] encoded Unicode string containing
the name of an Information Element, intended as a the name of an Information Element, intended as a
simple identifier. See the Security Considerations simple identifier. See the Security Considerations
section for notes on string handling for Information section for notes on string handling for Information
Element type records. Element type records.
7.51. informationElementRangeBegin 7.147. informationElementRangeBegin
elementId: TBD elementId: TBD
name: informationElementRangeBegin name: informationElementRangeBegin
dataType: unsigned64 dataType: unsigned64
status: current status: current
description: Contains the inclusive low end of the range of description: Contains the inclusive low end of the range of
acceptable values for an Information Element. acceptable values for an Information Element.
7.52. informationElementRangeEnd 7.148. informationElementRangeEnd
elementId: TBD elementId: TBD
name: informationElementRangeEnd name: informationElementRangeEnd
dataType: unsigned64 dataType: unsigned64
status: current status: current
description: Contains the inclusive high end of the range of description: Contains the inclusive high end of the range of
acceptable values for an Information Element. acceptable values for an Information Element.
7.53. informationElementSemantics 7.149. informationElementSemantics
elementId: TBD elementId: TBD
name: informationElementSemantics name: informationElementSemantics
dataType: unsigned8 dataType: unsigned8
status: current status: current
description: A description of the semantics of an IPFIX description: A description of the semantics of an IPFIX
Information Element. These are taken from the data Information Element. These are taken from the data
type semantics defined in section 3.2 of the IPFIX type semantics defined in section 3.2 of the IPFIX
Information Model [RFC5102]; see that section for Information Model [RFC5102]; see that section for
more information on the types defined in the more information on the types defined in the
informationElementSemantics sub-registry. This informationElementSemantics sub-registry. This
skipping to change at page 39, line 27 skipping to change at page 65, line 36
manipulated by a Collecting Process or File Reader manipulated by a Collecting Process or File Reader
that does not understand it a priori. that does not understand it a priori.
These semantics are registered in the IANA IPFIX These semantics are registered in the IANA IPFIX
Information Element Semantics subregistry. This Information Element Semantics subregistry. This
subregistry is intended to assign numbers for subregistry is intended to assign numbers for
semantics names, not to provide a mechanism for semantics names, not to provide a mechanism for
adding semantics to the IPFIX Protocol, and as such adding semantics to the IPFIX Protocol, and as such
requires a Standards Action [RFC5226] to modify. requires a Standards Action [RFC5226] to modify.
7.54. informationElementUnits 7.150. informationElementUnits
elementId: TBD elementId: TBD
name: informationElementUnits name: informationElementUnits
dataType: unsigned16 dataType: unsigned16
status: current status: current
description: A description of the units of an IPFIX Information description: A description of the units of an IPFIX Information
Element. These correspond to the units implicitly Element. These correspond to the units implicitly
defined in the Information Element definitions in defined in the Information Element definitions in
section 5 of the IPFIX Information Model [RFC5102]; section 5 of the IPFIX Information Model [RFC5102];
see that section for more information on the types see that section for more information on the types
described in the informationElementsUnits described in the informationElementsUnits
sub-registry. This field may take the values in sub-registry. This field may take the values in
Table 3 below; the special value 0x00 (none) is Table 3 below; the special value 0x00 (none) is
used to note that the field is unitless. used to note that the field is unitless.
These types are registered in the IANA IPFIX These types are registered in the IANA IPFIX
Information Element Units subregistry; new types Information Element Units subregistry; new types
may be added on a First Come First Served [RFC5226] may be added on a First Come First Served [RFC5226]
basis. basis.
7.55. userName 7.151. userName
elementId: TBD elementId: TBD
name: userName name: userName
dataType: string dataType: string
status: current status: current
description: User name associated with the flow. description: User name associated with the flow.
7.56. applicationCategoryName 7.152. applicationCategoryName
elementId: TBD elementId: TBD
name: applicationCategoryName name: applicationCategoryName
dataType: string dataType: string
status: current status: current
description: An attribute that provides a first level description: An attribute that provides a first level
categorization for each Application ID. categorization for each Application ID.
7.57. mibObjectValueInteger 7.153. mibObjectValueInteger
elementId: TBD elementId: TBD
name: mibObjectValueInteger name: mibObjectValueInteger
dataType: signed64 dataType: signed64
status: current status: current
description: An IPFIX Information Element which denotes that the description: An IPFIX Information Element which denotes that the
integer value of a MIB object will be exported. integer value of a MIB object will be exported.
The MIB Object Identifier ("mibObjectIdentifier") The MIB Object Identifier ("mibObjectIdentifier")
for this field MUST be exported in a MIB Field for this field MUST be exported in a MIB Field
Option or via another means. This Information Option or via another means. This Information
Element is used for MIB objects with the Base Element is used for MIB objects with the Base
Syntax of Integer32 and INTEGER with IPFIX Reduced Syntax of Integer32 and INTEGER with IPFIX Reduced
Size Encoding used as required. The value is Size Encoding used as required. The value is
encoded as per the standard IPFIX Abstract Data Type encoded as per the standard IPFIX Abstract Data Type
of signed64. of signed64.
7.58. mibObjectValueOctetString 7.154. mibObjectValueOctetString
elementId: TBD elementId: TBD
name: mibObjectValueOctetString name: mibObjectValueOctetString
dataType: octetArray dataType: octetArray
status: current status: current
description: An IPFIX Information Element which denotes that an description: An IPFIX Information Element which denotes that an
Octet String or Opaque value of a MIB object will Octet String or Opaque value of a MIB object will
be exported. The MIB Object Identifier be exported. The MIB Object Identifier
("mibObjectIdentifier") for this field MUST be ("mibObjectIdentifier") for this field MUST be
exported in a MIB Field Option or via another means. exported in a MIB Field Option or via another means.
This Information Element is used for MIB objects This Information Element is used for MIB objects
with the Base Syntax of OCTET STRING and Opaque. The with the Base Syntax of OCTET STRING and Opaque. The
value is encoded as per the standard IPFIX Abstract value is encoded as per the standard IPFIX Abstract
Data Type of octetArray. Data Type of octetArray.
7.59. mibObjectValueOID 7.155. mibObjectValueOID
elementId: TBD elementId: TBD
name: mibObjectValueOID name: mibObjectValueOID
dataType: octetArray dataType: octetArray
status: current status: current
description: An IPFIX Information Element which denotes that an description: An IPFIX Information Element which denotes that an
Object Identifier or OID value of a MIB object will Object Identifier or OID value of a MIB object will
be exported. The MIB Object Identifier be exported. The MIB Object Identifier
("mibObjectIdentifier") for this field MUST be ("mibObjectIdentifier") for this field MUST be
exported in a MIB Field Option or via another means. exported in a MIB Field Option or via another means.
This Information Element is used for MIB objects This Information Element is used for MIB objects
with the Base Syntax of OBJECT IDENTIFIER. Note - with the Base Syntax of OBJECT IDENTIFIER. Note -
In this case the "mibObjectIdentifier" will define In this case the "mibObjectIdentifier" will define
which MIB object is being exported while the value which MIB object is being exported while the value
contained in this Information Element will be an contained in this Information Element will be an
OID as a value. The mibObjectValueOID Information OID as a value. The mibObjectValueOID Information
Element is encoded as ASN.1/BER [BER] in an Element is encoded as ASN.1/BER [BER] in an
octetArray. octetArray.
7.60. mibObjectValueBits 7.156. mibObjectValueBits
elementId: TBD elementId: TBD
name: mibObjectValueBits name: mibObjectValueBits
dataType: octetArray dataType: octetArray
status: current status: current
description: An IPFIX Information Element which denotes that a description: An IPFIX Information Element which denotes that a
set of Enumerated flags or bits from a MIB object set of Enumerated flags or bits from a MIB object
will be exported. The MIB Object Identifier will be exported. The MIB Object Identifier
("mibObjectIdentifier") for this field MUST be ("mibObjectIdentifier") for this field MUST be
exported in a MIB Field Option or via another means. exported in a MIB Field Option or via another means.
This Information Element is used for MIB objects This Information Element is used for MIB objects
with the Base Syntax of BITS. The flags or bits are with the Base Syntax of BITS. The flags or bits are
encoded as per the standard IPFIX Abstract Data Type encoded as per the standard IPFIX Abstract Data Type
of octetArray, with sufficient length to accommodate of octetArray, with sufficient length to accommodate
the required number of bits. If the number of bits the required number of bits. If the number of bits
is not an integer multiple of octets then the most is not an integer multiple of octets then the most
significant bits at end of the octetArray MUST be significant bits at end of the octetArray MUST be
set to zero. set to zero.
7.61. mibObjectValueIPAddress 7.157. mibObjectValueIPAddress
elementId: TBD elementId: TBD
name: mibObjectValueIPAddress name: mibObjectValueIPAddress
dataType: ipv4Address dataType: ipv4Address
status: current status: current
description: An IPFIX Information Element which denotes that the description: An IPFIX Information Element which denotes that the
IPv4 Address of a MIB object will be exported. The IPv4 Address of a MIB object will be exported. The
MIB Object Identifier ("mibObjectIdentifier") for MIB Object Identifier ("mibObjectIdentifier") for
this field MUST be exported in a MIB Field Option this field MUST be exported in a MIB Field Option
or via another means. This Information Element is or via another means. This Information Element is
used for MIB objects with the Base Syntax of used for MIB objects with the Base Syntax of
IPaddress. The value is encoded as per the standard IPaddress. The value is encoded as per the standard
IPFIX Abstract Data Type of ipv4Address. IPFIX Abstract Data Type of ipv4Address.
7.62. mibObjectValueCounter 7.158. mibObjectValueCounter
elementId: TBD elementId: TBD
name: mibObjectValueCounter name: mibObjectValueCounter
dataType: unsigned64 dataType: unsigned64
status: current status: current
description: An IPFIX Information Element which denotes that the description: An IPFIX Information Element which denotes that the
counter value of a MIB object will be exported. counter value of a MIB object will be exported.
The MIB Object Identifier ("mibObjectIdentifier") The MIB Object Identifier ("mibObjectIdentifier")
for this field MUST be exported in a MIB Field for this field MUST be exported in a MIB Field
Option or via another means. This Information Option or via another means. This Information
Element is used for MIB objects with the Base Element is used for MIB objects with the Base
Syntax of Counter32 or Counter64 with IPFIX Reduced Syntax of Counter32 or Counter64 with IPFIX Reduced
Size Encoding used as required. The value is encoded Size Encoding used as required. The value is encoded
as per the standard IPFIX Abstract Data Type as per the standard IPFIX Abstract Data Type
of unsigned64. of unsigned64.
7.63. mibObjectValueGauge 7.159. mibObjectValueGauge
elementId: TBD elementId: TBD
name: mibObjectValueGauge name: mibObjectValueGauge
dataType: unsigned32 dataType: unsigned32
status: current status: current
description: An IPFIX Information Element which denotes that the description: An IPFIX Information Element which denotes that the
Gauge value of a MIB object will be exported. The Gauge value of a MIB object will be exported. The
MIB Object Identifier ("mibObjectIdentifier") for MIB Object Identifier ("mibObjectIdentifier") for
this field MUST be exported in a MIB Field Option this field MUST be exported in a MIB Field Option
or via another means. This Information Element is or via another means. This Information Element is
used for MIB objects with the Base Syntax of Gauge32. used for MIB objects with the Base Syntax of Gauge32.
The value is encoded as per the standard IPFIX The value is encoded as per the standard IPFIX
Abstract Data Type of unsigned64. This value will Abstract Data Type of unsigned64. This value will
represent a non-negative integer, which may increase represent a non-negative integer, which may increase
or decrease, but shall never exceed a maximum or decrease, but shall never exceed a maximum
value, nor fall below a minimum value. value, nor fall below a minimum value.
7.64. mibObjectValueTimeTicks 7.160. mibObjectValueTimeTicks
elementId: TBD elementId: TBD
name: mibObjectValueTimeTicks name: mibObjectValueTimeTicks
dataType: unsigned32 dataType: unsigned32
status: current status: current
description: An IPFIX Information Element which denotes that the description: An IPFIX Information Element which denotes that the
TimeTicks value of a MIB object will be exported. TimeTicks value of a MIB object will be exported.
The MIB Object Identifier ("mibObjectIdentifier") The MIB Object Identifier ("mibObjectIdentifier")
for this field MUST be exported in a MIB Field for this field MUST be exported in a MIB Field
Option or via another means. This Information Option or via another means. This Information
Element is used for MIB objects with the Base Element is used for MIB objects with the Base
Syntax of TimeTicks. The value is encoded as per Syntax of TimeTicks. The value is encoded as per
the standard IPFIX Abstract Data Type of unsigned32. the standard IPFIX Abstract Data Type of unsigned32.
7.65. mibObjectValueUnsigned 7.161. mibObjectValueUnsigned
elementId: TBD elementId: TBD
name: mibObjectValueUnsigned name: mibObjectValueUnsigned
dataType: unsigned64 dataType: unsigned64
status: current status: current
description: An IPFIX Information Element which denotes that an description: An IPFIX Information Element which denotes that an
unsigned integer value of a MIB object will be unsigned integer value of a MIB object will be
exported. The MIB Object Identifier exported. The MIB Object Identifier
("mibObjectIdentifier") for this field MUST be ("mibObjectIdentifier") for this field MUST be
exported in a MIB Field Option or via another means. exported in a MIB Field Option or via another means.
This Information Element is used for MIB objects This Information Element is used for MIB objects
with the Base Syntax of unsigned64 with IPFIX with the Base Syntax of unsigned64 with IPFIX
Reduced Size Encoding used as required. The value is Reduced Size Encoding used as required. The value is
encoded as per the standard IPFIX Abstract Data Type encoded as per the standard IPFIX Abstract Data Type
of unsigned64. of unsigned64.
7.66. mibObjectValueTable 7.162. mibObjectValueTable
elementId: TBD elementId: TBD
name: mibObjectValueTable name: mibObjectValueTable
dataType: orderedList dataType: orderedList
status: current status: current
description: An IPFIX Information Element which denotes that a description: An IPFIX Information Element which denotes that a
complete or partial conceptual table will be complete or partial conceptual table will be
exported. The MIB Object Identifier exported. The MIB Object Identifier
("mibObjectIdentifier") for this field MUST be ("mibObjectIdentifier") for this field MUST be
exported in a MIB Field Option or via another means. exported in a MIB Field Option or via another means.
This Information Element is used for MIB objects This Information Element is used for MIB objects
with a SYNTAX of SEQUENCE. This is encoded as a with a SYNTAX of SEQUENCE. This is encoded as a
subTemplateList of mibObjectValue Information subTemplateList of mibObjectValue Information
Elements. The template specified in the Elements. The template specified in the
subTemplateList MUST be an Options Template and subTemplateList MUST be an Options Template and
MUST include all the Objects listed in the INDEX MUST include all the Objects listed in the INDEX
clause as Scope Fields. clause as Scope Fields.
structure: orderedList(mibObjectValueRow+)
7.163. mibObjectValueRow
7.67. mibObjectValueRow
elementId: TBD elementId: TBD
name: mibObjectValueRow name: mibObjectValueRow
dataType: orderedList dataType: orderedList
status: current status: current
description: An IPFIX Information Element which denotes that a description: An IPFIX Information Element which denotes that a
single row of a conceptual table will be exported. single row of a conceptual table will be exported.
The MIB Object Identifier ("mibObjectIdentifier") The MIB Object Identifier ("mibObjectIdentifier")
for this field MUST be exported in a MIB Field for this field MUST be exported in a MIB Field
Option or via another means. This Information Option or via another means. This Information
Element is used for MIB objects with a SYNTAX of Element is used for MIB objects with a SYNTAX of
SEQUENCE. This is encoded as a subTemplateList of SEQUENCE. This is encoded as a subTemplateList of
mibObjectValue Information Elements. The mibObjectValue Information Elements. The
subTemplateList exported MUST contain exactly one subTemplateList exported MUST contain exactly one
row (i.e., one instance of the subtemplate). The row (i.e., one instance of the subtemplate). The
template specified in the subTemplateList MUST be template specified in the subTemplateList MUST be
an Options Template and MUST include all the an Options Template and MUST include all the
Objects listed in the INDEX clause as Scope Fields. Objects listed in the INDEX clause as Scope Fields.
structure: orderedList(mibObjectValue+)
7.68. mibObjectIdentifier 7.164. mibObjectIdentifier
elementId: TBD elementId: TBD
name: mibObjectIdentifier name: mibObjectIdentifier
dataType: octetArray dataType: octetArray
status: current status: current
description: An IPFIX Information Element which denotes that a description: An IPFIX Information Element which denotes that a
MIB Object Identifier (MIB OID) is exported in the MIB Object Identifier (MIB OID) is exported in the
(Options) Template Record. The mibObjectIdentifier (Options) Template Record. The mibObjectIdentifier
Information Element contains the OID assigned to Information Element contains the OID assigned to
the MIB Object Type Definition encoded as the MIB Object Type Definition encoded as
ASN.1/BER [BER]. ASN.1/BER [BER].
7.69. mibSubIdentifier 7.165. mibSubIdentifier
elementId: TBD elementId: TBD
name: mibSubIdentifier name: mibSubIdentifier
dataType: unsigned32 dataType: unsigned32
status: current status: current
description: A non-negative sub-identifier of an Object description: A non-negative sub-identifier of an Object
Identifier (OID). Identifier (OID).
7.70. mibIndexIndicator 7.166. mibIndexIndicator
elementId: TBD elementId: TBD
name: mibIndexIndicator name: mibIndexIndicator
dataType: unsigned64 dataType: unsigned64
status: current status: current
description: This set of bit fields is used for marking the description: This set of bit fields is used for marking the
Information Elements of a Data Record that serve as Information Elements of a Data Record that serve as
INDEX MIB objects for an indexed Columnar MIB INDEX MIB objects for an indexed Columnar MIB
object. Each bit represents an Information Element object. Each bit represents an Information Element
in the Data Record with the n-th bit representing in the Data Record with the n-th bit representing
the n-th Information Element. A bit set to value 1 the n-th Information Element. A bit set to value 1
skipping to change at page 46, line 32 skipping to change at page 73, line 32
Fields are among the first 64 Information Elements, Fields are among the first 64 Information Elements,
because the mibIndexIndicator only contains 64 bits. because the mibIndexIndicator only contains 64 bits.
If the Data Record contains less than 64 If the Data Record contains less than 64
Information Elements, then the extra bits in the Information Elements, then the extra bits in the
mibIndexIndicator for which no corresponding mibIndexIndicator for which no corresponding
Information Element exists MUST have the value 0, Information Element exists MUST have the value 0,
and must be disregarded by the Collector. This and must be disregarded by the Collector. This
Information Element may be exported with Information Element may be exported with
IPFIX Reduced Size Encoding. IPFIX Reduced Size Encoding.
7.71. mibCaptureTimeSemantics 7.167. mibCaptureTimeSemantics
elementId: TBD elementId: TBD
name: mibCaptureTimeSemantics name: mibCaptureTimeSemantics
dataType: unsigned8 dataType: unsigned8
status: current status: current
description: Indicates when in the lifetime of the flow the MIB description: Indicates when in the lifetime of the flow the MIB
value was retrieved from the MIB for a value was retrieved from the MIB for a
mibObjectIdentifier. This is used to indicate if mibObjectIdentifier. This is used to indicate if
the value exported was collected from the MIB the value exported was collected from the MIB
closer to flow creation or flow export time and closer to flow creation or flow export time and
will refer to the Timestamp fields included in the will refer to the Timestamp fields included in the
skipping to change at page 47, line 41 skipping to change at page 74, line 41
1. begin - The value for the MIB object is captured 1. begin - The value for the MIB object is captured
from the MIB when the Flow is first observed from the MIB when the Flow is first observed
2. end - The value for the MIB object is captured 2. end - The value for the MIB object is captured
from the MIB when the Flow ends from the MIB when the Flow ends
3. export - The value for the MIB object is 3. export - The value for the MIB object is
captured from the MIB at export time captured from the MIB at export time
4. average - The value for the MIB object is an 4. average - The value for the MIB object is an
average of multiple captures from the MIB over the average of multiple captures from the MIB over the
observed life of the Flow observed life of the Flow
7.72. mibContextEngineID 7.168. mibContextEngineID
elementId: TBD elementId: TBD
name: mibContextEngineID name: mibContextEngineID
dataType: octetArray dataType: octetArray
status: current status: current
description: A mibContextEngineID that specifies the SNMP engine description: A mibContextEngineID that specifies the SNMP engine
ID for a MIB field being exported over IPFIX. ID for a MIB field being exported over IPFIX.
Definition as per [RFC3411] section 3.3. Definition as per [RFC3411] section 3.3.
7.73. mibContextName 7.169. mibContextName
elementId: TBD elementId: TBD
name: mibContextName name: mibContextName
dataType: string dataType: string
status: current status: current
description: This Information Element denotes that a MIB Context description: This Information Element denotes that a MIB Context
Name is specified for a MIB field being exported Name is specified for a MIB field being exported
over IPFIX. Reference [RFC3411] section 3.3. over IPFIX. Reference [RFC3411] section 3.3.
7.74. mibObjectName 7.170. mibObjectName
elementId: TBD elementId: TBD
name: mibObjectName name: mibObjectName
dataType: string dataType: string
status: current status: current
description: The name (called a descriptor in [RFC2578] description: The name (called a descriptor in [RFC2578]
of an object type definition. of an object type definition.
7.75. mibObjectDescription 7.171. mibObjectDescription
elementId: TBD elementId: TBD
name: mibObjectDescription name: mibObjectDescription
dataType: string dataType: string
status: current status: current
description: The value of the DESCRIPTION clause of an MIB object description: The value of the DESCRIPTION clause of an MIB object
type definition. type definition.
7.76. mibObjectSyntax 7.172. mibObjectSyntax
elementId: TBD elementId: TBD
name: mibObjectSyntax name: mibObjectSyntax
dataType: string dataType: string
status: current status: current
description: The value of the SYNTAX clause of an MIB object type description: The value of the SYNTAX clause of an MIB object type
definition, which may include a Textual Convention definition, which may include a Textual Convention
or Subtyping. See [RFC2578]. or Subtyping. See [RFC2578].
7.77. mibModuleName 7.173. mibModuleName
elementId: TBD elementId: TBD
name: mibModuleName name: mibModuleName
dataType: string dataType: string
status: current status: current
description: The textual name of the MIB module that defines a MIB description: The textual name of the MIB module that defines a MIB
Object. Object.
8. SACM Usage Scenario Example 7.174. interface
TODO: this section needs to refer out to wherever the operations / elementId: TBD
generalized workflow content ends up name: interface
dataType: list
structure: list (InterfaceName, hwAddress, inetAddr, netmask)
status: current
description: Represents an interface and its configuration
options.
TODO: revise to eliminate graph references 7.175. interfaceName
This section illustrates the proposed SACM Information Model as elementId: TBD
applied to SACM Usage Scenario 2.2.3, Detection of Posture Deviations name: interfaceName
[RFC7632]. The following subsections describe the elements dataType: string
(components and elements), graph model, and operations (sample status: current
workflow) required to support the Detection of Posture Deviations description: The interface
scenario. name.
The Detection of Posture Deviations scenario involves multiple 7.176. iflisteners
elements interacting to accomplish the goals of the scenario.
Figure 11 illustrates those elements along with their major
communication paths.
8.1. Graph Model for Detection of Posture Deviation elementId: TBD
name: iflisteners
dataType: list
structure: list (interfaceName, physicalProtocol, hwAddress,
programName, pid, userId)
status: current
description: Stores the results of checking for applications that
are bound to an ethernet interface on the system.
The following subsections contain examples of identifiers and 7.177. physicalProtocol
metadata which would enable detection of posture deviation. These
lists are by no means exhaustive - many other types of metadata would
be enumerated in a data model that fully addressed this usage
scenario.
8.1.1. Components elementId: TBD
name: physicalProtocol
dataType: enumeration
structure:
ETH_P_LOOP ; 0x1 ; Ethernet loopback packet.
ETH_P_PUP ; 0x2 ; Xerox PUP packet.
ETH_P_PUPAT ; 0x3 ; Xerox PUP Address Transport packet.
ETH_P_IP ; 0x4 ; Internet protocol packet.
ETH_P_X25 ; 0x5 ; CCITT X.25 packet.
ETH_P_ARP ; 0x6 ; Address resolution packet.
ETH_P_BPQ ; 0x7 ; G8BPQ AX.25 ethernet packet.
ETH_P_IEEEPUP ; 0x8 ; Xerox IEEE802.3 PUP packet.
ETH_P_IEEEPUPAT ; 0x9 ; Xerox IEEE802.3 PUP address transport
packet.
ETH_P_DEC ; 0xA ; DEC assigned protocol.
ETH_P_DNA_DL ; 0xB ; DEC DNA Dump/Load.
The proposed SACM Information Model contains three components, as ETH_P_DNA_RC ; 0xC ; DEC DNA Remote Console.
defined in the SACM Architecture [I-D.ietf-sacm-architecture]: ETH_P_DNA_RT ; 0xD ; DEC DNA Routing.
Posture Attribute Information Provider, Posture Attribute Information ETH_P_LAT ; 0xE ; DEC LAT.
Consumer, and Control Plane. ETH_P_DIAG ; 0xF ; DEC Diagnostics.
ETH_P_CUST ; 0x10 ; DEC Customer use.
ETH_P_SCA ; 0x11 ; DEC Systems Comms Arch.
ETH_P_RARP ; 0x12 ; Reverse address resolution packet.
ETH_P_ATALK ; 0x13 ; Appletalk DDP.
ETH_P_AARP ; 0x14 ; Appletalk AARP.
ETH_P_8021Q ; 0x15 ; 802.1Q VLAN Extended Header.
ETH_P_IPX ; 0x16 ; IPX over DIX.
ETH_P_IPV6 ; 0x17 ; IPv6 over bluebook.
ETH_P_SLOW ; 0x18 ; Slow Protocol. See 802.3ad 43B.
ETH_P_WCCP ; 0x19 ; Web-cache coordination protocol.
ETH_P_PPP_DISC ; 0x1A ; PPPoE discovery messages.
ETH_P_PPP_SES ; 0x1B ; PPPoE session messages.
ETH_P_MPLS_UC ; 0x1C ; MPLS Unicast traffic.
ETH_P_MPLS_MC ; 0x1D ; MPLS Multicast traffic.
ETH_P_ATMMPOA ; 0x1E ; MultiProtocol Over ATM.
ETH_P_ATMFATE ; 0x1F ; Frame-based ATM Transport over Ethernet.
ETH_P_AOE ; 0x20 ; ATA over Ethernet.
ETH_P_TIPC ; 0x21 ; TIPC.
ETH_P_802_3 ; 0x22 ; Dummy type for 802.3 frames.
ETH_P_AX25 ; 0x23 ; Dummy protocol id for AX.25.
ETH_P_ALL ; 0x24 ; Every packet.
ETH_P_802_2 ; 0x25 ; 802.2 frames.
ETH_P_SNAP ; 0x26 ; Internal only.
ETH_P_DDCMP ; 0x27 ; DEC DDCMP: Internal only
ETH_P_WAN_PPP ; 0x28 ; Dummy type for WAN PPP frames.
ETH_P_PPP_MP ; 0x29 ; Dummy type for PPP MP frames.
ETH_P_PPPTALK ; 0x2A ; Dummy type for Atalk over PPP.
ETH_P_LOCALTALK ; 0x2B ; Localtalk pseudo type.
ETH_P_TR_802_2 ; 0x2C ; 802.2 frames.
ETH_P_MOBITEX ; 0x2D ; Mobitex.
ETH_P_CONTROL ; 0x2E ; Card specific control frames.
ETH_P_IRDA ; 0x2F ; Linux-IrDA.
ETH_P_ECONET ; 0x30 ; Acorn Econet.
ETH_P_HDLC ; 0x31 ; HDLC frames.
ETH_P_ARCNET ; 0x32 ; 1A for ArcNet.
; 0x33 ; The empty string value is permitted here
to allow for detailed error reporting.
status: current
description: The physical layer protocol used by the AF_PACKET
socket.
In this example, the components are instantiated as follows: 7.178. hwAddress
o The Posture Attribute Information Provider is an endpoint security elementId: TBD
service which monitors the compliance state of the endpoint and name: hwAddress
reports any deviations for the expected posture. dataType: string
status: current
description: The hardware address associated
with the interface.
o The Posture Attribute Information Consumer is an analytics engine 7.179. programName
which absorbs information from around the network and generates a
"heat map" of which areas in the network are seeing unusually high
rates of posture deviations.
o The Control Plane is a security automation broker which receives elementId: TBD
subscription requests from the analytics engine and authorizes name: programName
access to appropriate information from the endpoint security dataType: string
service. status: current
description: The name of the communicating
program.
8.1.2. Identifiers 7.180. userId
To represent the elements listed above, the set of identifiers might elementId: TBD
include (but is not limited to): name: userId
dataType: integer
status: current
description: The numeric user id.
o Identity - a device itself, or a user operating a device, 7.181. inetlisteningserver
categorized by type of identity (e.g. username or X.509
certificate [RFC5280])
o Software asset elementId: TBD
name: inetlisteningserver
dataType: list
structure: list (transportProtocol, localAddress,
localPort, localFullAddress, programName, foreignAddress,
foreignPort, foreignFullAddress, pid, userId)
status:
current
description: Stores the results of checking for network servers
currently active on a system. It holds information pertaining to
a specific protocol-address-port combination.
o Network Session 7.182. transportProtocol
o Address - categorized by type of address (e.g. MAC address, IP elementId: TBD
address, Host Identity Protocol (HIP) Host Identity Tag (HIT) name: transportProtocol
[RFC5201], etc.) dataType: string
status: current
description: The transport-layer
protocol (tcp or udp).
o Task - categorized by type of task (e.g. internal collector, 7.183. localAddress
external collector, evaluator, or reporting task)
o Result - categorized by type of result (e.g. evaluation result or elementId: TBD
report) name: localAddress
dataType: ipAddress
status: current
description: This is the IP address being listened to. Note that
the IP address can be IPv4 or IPv6.
o Guidance 7.184. localPort
8.1.3. Metadata elementId: TBD
name: localPort
dataType: integer
status: current
description: This is the TCP or UDP port
being listened to.
To characterize the elements listed above, the set of metadata types 7.185. localFullAddress
might include (but is not limited to):
o Authorization metadata attached to an identity identifier, or to a elementId: TBD
link between a network session identifier and an identity name: localFullAddress
identifier, or to a link between a network session identifier and dataType: string
an address identifier. status: current
description: The IP address and network port on which the program
listens, including the local address and the local port. Note
that the IP address can be IPv4 or IPv6.
o Location metadata attached to a link between a network session 7.186. foreignAddress
identifier and an address identifier.
o Event metadata attached to an address identifier or an identity elementId: TBD
identifier of an endpoint, which would be made available to name: foreignAddress
interested parties at the time of publication, but not stored dataType: ipAddresss
long-term. For example, when a user disables required security status: current
software, an internal collector associated with an endpoint description: The IP address with which the program is
security service might publish guidance violation event metadata communicating, or with which it will communicate. Note that the
attached to the identity identifier of the endpoint, to notify IP address can be IPv4 or IPv6.
consumers of the change in endpoint state.
o Posture attribute metadata attached to an identity identifier of 7.187. foreignFullAddress
an endpoint. For example, when required security software is not
running, an internal collector associated with an endpoint
security service might publish posture attribute metadata attached
to the identity identifier of the endpoint, to notify consumers of
the current state of the endpoint.
8.1.4. Relationships between Identifiers and Metadata elementId: TBD
name: foreignFullAddress
dataType: ipAddresss
status: current
description: The IP address and network port to which the program
is communicating or will accept communications from, including
the foreign address and foreign port. Note that the IP address
can be IPv4 or IPv6.
Interaction between multiple sets of identifiers and metadata lead to 7.188. selinuxboolean
some fairly common patterns, or "constellations", of metadata. For
example, an authenticated-session metadata constellation might
include a central network session with authorizations and location
attached, and links to a user identity, an endpoint identity, a MAC
address, an IP address, and the identity of the policy server that
authorized the session, for the duration of the network session.
These constellations may be independent of each other, or one elementId: TBD
constellation may be connected to another. For example, an name: selinuxboolean
authenticated-session metadata constellation may be created when a dataType: list
user connects an endpoint to the network; separately, an endpoint- structure: list (selinuxName, currentStatus,
posture metadata constellation may be created when an endpoint pendingStatus)
security system and other collectors gather and publish posture status: current
information related to an endpoint. These two constellations are not description: Describes the current and pending status of a
necessarily connected to each other, but may be joined if the SELinux boolean.
component publishing the authenticated-session metadata constellation
is able to link the network session identifier to the identity
identifier of the endpoint.
8.2. Workflow 7.189. selinuxName
The workflow for exchange of information supporting detection of elementId: TBD
posture deviation, using a standard publish/subscribe/query transport name: selinuxName
model such as available with IF-MAP [TNC-IF-MAP-SOAP-Binding] or dataType: string
XMPP-Grid [I-D.salowey-sacm-xmpp-grid], is as follows: status: current
description: The name of the SELinux
boolean.
1. The analytics engine (Posture Assessment Information Consumer) 7.190. currentStatus
establishes connectivity and authorization with the transport
fabric, and subscribes to updates on posture deviations.
2. The endpoint security service (Posture Assessment Information elementId: TBD
Provider) requests connection to the transport fabric. name: currentStatus
dataType: boolean
status: current
description: Indicates current state of
the specified SELinux boolean.
3. Transport fabric authenticates and establishes authorized 7.191. pendingStatus
privileges (e.g. privilege to publish and/or subscribe to
security data) for the requesting components.
4. The endpoint security service evaluates the endpoint, detects elementId: TBD
posture deviation, and publishes information on the posture name: pendingStatus
deviation. dataType: boolean
status: current
description: Indicates the pending
state of the specified SELinux boolean.
5. The transport fabric notifies the analytics engine, based on its 7.192. selinuxsecuritycontext
subscription of the new posture deviation information. elementId: TBD
name: selinuxsecuritycontext
dataType: list
structure: list (filepath, path, filename, pid,
username, role, domainType, lowSensitivity, lowCategory,
highSensitivity, highCategory, rawlowSensitivity,
rawlowCategory, rawhighSensitivity, rawhighCategory)
status: current
description: Describes the SELinux security
context of a file or process on the local system.
Other components, such as access control policy servers or 7.193. filepath
remediation systems, may also consume the posture deviation
information provided by the endpoint security service.
9. Acknowledgements elementId: TBD
name: filepath
dataType: string
status: current
description: Specifies the absolute path for a file on the
machine. A directory cannot be specified as a filepath.
7.194. path
elementId: TBD
name: path
dataType: string
status: current
description: Specifies the directory component of
the absolute path to a file on the machine.
7.195. filename
elementId: TBD
name: filename
dataType: string
status: current
description: The name of the file.
7.196. pid
elementId: TBD
name: pid
dataType: integer
status: current
description: The process ID of the
process.
7.197. role
elementId: TBD
name: role
dataType: string
status: current
description: Specifies the types that a process
may transition to (domain transitions).
7.198. domainType
elementId: TBD
name: domainType
dataType: string
status: current
description: Specifies the domain in which the file is accessible
or the domain in which a process executes.
7.199. lowSensitivity
elementId: TBD
name: lowSensitivity
dataType: string
status: current
description: Specifies the current sensitivity of a file or
process.
7.200. lowCategory
elementId: TBD
name: lowCategory
dataType: string
status: current
description: Specifies the set of
categories associated with the low sensitivity.
7.201. highSensitivity
elementId: TBD
name: highSensitivity
dataType: string
status: current
description: Specifies the maximum
range for a file or the clearance for a process.
7.202. highCategory
elementId: TBD
name: highCategory
dataType: string
status: current
description: Specifies the set of
categories associated with the high sensitivity.
7.203. rawlowSensitivity
elementId: TBD
name: rawlowSensitivity
dataType: string
status: current
description: Specifies the current sensitivity of a file or
process but in its raw context.
7.204. rawlowCategory
elementId: TBD
name: rawlowCategory
dataType: string
status: current
description: Specifies the set of categories associated with the
low sensitivity but in its raw context.
7.205. rawhighSensitivity
elementId: TBD
name: rawhighSensitivity
dataType: string
status: current
description: Specifies the maximum range for a file or the
clearance for a process but in its raw context.
7.206. rawhighCategory
elementId: TBD
name: rawhighCategory
dataType: string
status: current
description: Specifies the set of categories associated with the
high sensitivity but in its raw context.
7.207. systemdunitdependency
elementId: TBD
name: systemdunitdependency
dataType: list
structure: list (unit, dependency)
status: current
description: Stores the dependencies of the systemd
unit.
7.208. unit
elementId: TBD
name: unit
dataType: string
status: current
description: Refers to the full systemd unit name, which has a
form of "$name.$type". For example "cupsd.service". This name is
usually also the filename of the unit configuration file.
7.209. dependency
elementId: TBD
name: dependency
dataType: string
status: current
description: Refers to the name of a unit that was confirmed to
be a dependency of the given unit.
7.210. systemdunitproperty
elementId: TBD
name: systemdunitproperty
dataType: list
structure: list (unit, property, systemdunitValue)
status: current
description: Stores the properties and values of a systemd unit.
7.211. property
elementId: TBD
name: property
dataType: string
status: current
description: The property associated with a
systemd unit.
7.212. systemdunitValue
elementId: TBD
name: systemdunitValue
dataType: string
status: current
description: The value of the property associated with a systemd
unit. Exactly one value shall be used for all property types
except dbus arrays - each array element shall be represented by
one value.
7.213. file
elementId: TBD
name: file
dataType: list
structure: list (filepath, path, filename, fileType, userId,
aTime, changeTime, mTime, size)
status: current
description: The metadata associated with a file on the endpoint.
7.214. fileType
elementId: TBD
name: fileType
dataType: string
status: current
description: The file's type (e.g., regular file (regular),
directory, named pipe (fifo), symbolic link, socket or block
special.)
7.215. groupId
elementId: TBD
name: groupId
dataType: integer
status: current
description: The group owner of the file, by
group number.
7.216. aTime
elementId: TBD
name: aTime
dataType: timeStamp
status: current
description: The time that the file was last
accessed.
7.217. changeTime
elementId: TBD
name: changeTime
dataType: timeStamp
status: current
description: The time of the last change
to the file's inode.
7.218. mTime
elementId: TBD
name: mTime
dataType: timeStamp
status: current
description: The time of the last change to
the file's contents.
7.219. size
elementId: TBD
name: size
dataType: integer
status: current
description: This is the size of the file in
bytes.
7.220. suid
elementId: TBD
name: suid
dataType: boolean
status: current
description: Indicates whether the program runs with the uid
(thus privileges) of the file's owner, rather than the calling
user.
7.221. sgid
elementId: TBD
name: sgid
dataType: boolean
status: current
description: Indicates whether the program runs with the gid
(thus privileges) of the file's group owner, rather than the
calling user's group.
7.222. sticky
elementId: TBD
name: sticky
dataType: boolean
status: current
description: Indicates whether users can delete each other's
files in this directory, when said directory is writable by
those users.
7.223. hasExtendedAcl
elementId: TBD
name: hasExtendedAcl
dataType: boolean
status: current
description: Indicates whether the file or directory hasACL
permissions applied to it. If a system supports ACLs and the
file or directory doesn't have an ACL, or it matches the standard
UNIX permissions, the entity will have a status of 'exists' and
a value of 'false'. If the system supports ACLs and the file or
directory has an ACL, the entity will have a status of 'exists'
and a value of 'true'. Lastly, if a system doesn't support ACLs,
the entity will have a status of 'does not exist'.
7.224. inetd
elementId: TBD
name: inetd
dataType: list
structure: list (serviceProtocol, serviceName, serverProgram,
serverArguments, endpointType, execAsUser, waitStatus)
status: current
description: Holds information associated
with different Internet services.
7.225. serverProgram
elementId: TBD
name: serverProgram
dataType: string
status: current
description: Either the pathname of a server program to be
invoked by inetd to perform the requested service, or the value
internal if inetd itself provides the service.
7.226. endpointType
elementId: TBD
name: endpointType
dataType: enumeration
structure:
stream ; 0x1 ; The stream value is used to describe a stream
socket.
dgram ; 0x2 ; The dgram value is used to describe a datagram
socket.
raw ; 0x3 ; The raw value is used to describe a raw socket.
seqpacket ; 0x4 ; The seqpacket value is used to describe a
sequenced packet socket.
tli ; 0x5 ; The tli value is used to describe all TLI endpoints.
sunrpc_tcp ; 0x6 ; The sunrpc_tcp value is used to describe all
SUNRPC TCP endpoints.
sunrpc_udp ; 0x7 ; The sunrpc_udp value is used to describe all
SUNRPC UDP endpoints.
; 0x8 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: The endpoint type (aka, socket type) associated with
the service.
7.227. execAsUser
elementId: TBD
name: execAsUser
dataType: string
status: current
description: The user id of the user the
server program should run under.
7.228. waitStatus
elementId: TBD
name: waitStatus
dataType: enumeration
structure: wait ; 0x1 ; The value of 'wait' specifies that the
server that is invoked by inetd will take over the listening
socket associated with the service, and once launched, inetd will
wait for that server to exit, if ever, before it resumes
listening for new service requests.
nowait ; 0x2 ; The value of 'nowait' specifies that the server
that is invoked by inetd will not wait for any existing server
to finish before taking over the listening socket associated with
the service.
; 0x3 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Specifies whether the server that is invoked by
inetd will take over the listening socket associated with the
service, and whether once launched, inetd will wait for that
server to exit, if ever, before it resumes listening for new
service requests. The legal values are "wait" or "nowait".
7.229. inetAddr
elementId: TBD
name: inetAddr
dataType: ipAddress
status: current
description: The IP address of the specific interface. Note that
the IP address can be IPv4 or IPv6.
7.230. netmask
elementId: TBD
name: netmask
dataType: ipAddress
status: current
description: The bitmask used to calculate
the interface's IP network.
7.231. passwordInfo
elementId: TBD
name: passwordInfo
dataType: list
structure: list (username, password, userId, groupId, gcos,
homeDir, loginShell, lastLogin)
status: current
description: Describes user account information for a
system.
7.232. username
elementId: TBD
name: username
dataType: string
status: current
description: The name of the user.
7.233. password
elementId: TBD
name: password
dataType: string
status: current
description: The encrypted version of the
user's password.
7.234. gcos
elementId: TBD
name: gcos
dataType: string
status: current
description:
7.235. homeDir
elementId: TBD
name: homeDir
dataType: string
status: current
description: The user's home
directory.
7.236. loginShell
elementId: TBD
name: loginShell
dataType: string
status: current
description: The user's shell
program.
7.237. lastLogin
elementId: TBD
name: lastLogin
dataType: integer
status: current
description: The date and time when the
last login occurred.
7.238. process
elementId: TBD
name: process
dataType: list
structure: list (commandLine, pid, ppid, priority, startTime)
status: current
description: Information about a process running on an endpoint.
7.239. commandLine
elementId: TBD
name: commandLine
dataType: string
status: current
description: The string used to start the
process. This includes any parameters that are part of the
command line.
7.240. ppid
elementId: TBD
name: ppid
dataType: integer
status: current
description: The process ID of the process's
parent process.
7.241. priority
elementId: TBD
name: priority
dataType: integer
status: current
description: The scheduling priority with
which the process runs.
7.242. startTime
elementId: TBD
name: startTime
dataType: string
status: current
description: The time of day the process
started.
7.243. routingtable
elementId: TBD
name: routingtable
dataType: list
structure: list (destination, gateway, flags,
interfaceName)
status: current
description: Holds information about an individual routing table
entry found in a system's primary routing table.
7.244. destination
elementId: TBD
name: destination
dataType: ipaddress
status: current
description: The destination IP address
prefix of the routing table entry.
7.245. gateway
elementId: TBD
name: gateway
dataType: ipaddress
status: current
description: The gateway of the specified
routing table entry.
7.246. runlevelInfo
elementId: TBD
name: runlevelInfo
dataType: list
structure: list (serviceName, runlevel, start, kill)
status: current
description: Information about the start or kill state of a
specified service at a given runlevel.
7.247. runlevel
elementId: TBD
name: runlevel
dataType: string
status: current
description: Specifies the system runlevel
associated with a service.
7.248. start
elementId: TBD
name: start
dataType: boolean
status: current
description: Specifies whether the service is
scheduled to start at the runlevel.
7.249. kill
elementId: TBD
name: kill
dataType: boolean
status: current
description: Specifies whether the service is
scheduled to be killed at the runlevel.
7.250. shadowItem
elementId: TBD
name: shadowItem
dataType: list
structure: list (username, password, chgLst, chgAllow,
chgReq, expWarn, expInact, expDate, flags, encryptMethod)
status: current
description:
7.251. chgLst
elementId: TBD
name: chgLst
dataType: timeStamp
status: current
description: The date of the last password
change.
7.252. chgAllow
elementId: TBD
name: chgAllow
dataType: integer
status: current
description: Specifies how often in days a
user may change their password. It can also be thought of
as the minimum age of a password.
7.253. chgReq
elementId: TBD
name: chgReq
dataType: integer
status: current
description: Describes how long a user can
keep a password before the system forces her to change it.
7.254. expWarn
elementId: TBD
name: expWarn
dataType: integer
status: current
description: Describes how long before
password expiration the system begins warning the user.
7.255. expInact
elementId: TBD
name: expInact
dataType: integer
status: current
description: Describes how many days of
account inactivity the system will wait after a password
expires before locking the account.
7.256. expDate
elementId: TBD
name: expDate
dataType: timeStamp
status: current
description: Specifies when will the
account's password expire.
7.257. encryptMethod
elementId: TBD
name: encryptMethod
dataType: enumeration
structure: DES ; 0x1 ; The DES method corresponds to the (none)
prefix.
BSDi ; 0x2 ; The BSDi method corresponds to BSDi modified
DES or the '_' prefix.
MD5 ; 0x3 ; The MD5 method corresponds to MD5 for Linux/BSD
or the $1$ prefix.
Blowfish ; 0x4 ; The Blowfish method corresponds to Blowfish
(OpenBSD) or the $2$ or $2a$ prefixes.
Sun MD5 ; 0x5 ; The Sun MD5 method corresponds to the $md5$
prefix.
SHA-256 ; 0x6 ; The SHA-256 method corresponds to the $5$
prefix.
SHA-512 ; 0x7 ; The SHA-512 method corresponds to the $6$
prefix. ; 0x8 ; The empty string value is permitted here to
allow for empty elements associated with variable references.
status: current
description: Describes method that is used for hashing
passwords.
7.258. symlink
elementId: TBD
name: symlink
dataType: list
structure: list (symlinkFilepath, canonicalPath)
status: current
description: Identifies the result generated for a symlink.
7.259. symlinkFilepath
elementId: TBD
name: symlinkFilepath
dataType: string
status: current
description: Specifies the filepath to
the subject symbolic link file.
7.260. canonicalPath
elementId: TBD
name: canonicalPath
dataType: string
status: current
description: Specifies the canonical
path for the target of the symbolic link file specified by
the filepath.
7.261. sysctl
elementId: TBD
name: sysctl
dataType: list
structure: list (kernelParameterName, kernelParameterValue+,
uname, machineClass, nodeName, osName, osRelease,
osVersion, processorType)
status: current
description: Stores
information retrieved from the local system about a kernel
parameter and its respective value(s).
7.262. kernelParameterName
elementId: TBD
name: kernelParameterName
dataType: string
status: current
description: The name of a kernel
parameter that was collected from the local system.
7.263. kernelParameterValue
elementId: TBD
name: kernelParameterValue
dataType: string
status: current
description: The current value(s)
for the specified kernel parameter on the local system.
7.264. uname
elementId: TBD
name: uname
dataType: list
structure: list (machineClass, nodeName, osName, osRelease,
osVersion, processorType)
status: current
description: Information about the hardware the machine is running
on.
7.265. machineClass
elementId: TBD
name: machineClass
dataType: string
status: current
description: Specifies the machine
hardware name.
7.266. nodeName
elementId: TBD
name: nodeName
dataType: string
status: current
description: Specifies the host
name.
7.267. osName
elementId: TBD
name: osName
dataType: string
status: current
description: Specifies the operating system
name.
7.268. osRelease
elementId: TBD
name: osRelease
dataType: string
status: current
description: Specifies the build
version.
7.269. osVersion
elementId: TBD
name: osVersion
dataType: string
status: current
description: Specifies the operating system
version.
7.270. processorType
elementId: TBD
name: processorType
dataType: string
status: current
description: Specifies the processor
type.
7.271. internetService
elementId: TBD
name: internetService
dataType: list
structure: list (serviceProtocol, serviceName, flags,
noAccess, onlyFrom, port, server, serverArguments,
socketType, registeredServiceType, user, wait, disabled)
status: current
description: Holds information associated with Internet services.
7.272. serviceProtocol
elementId: TBD
name: serviceProtocol
dataType: string
status: current
description: Specifies the protocol
that is used by the service.
7.273. serviceName
elementId: TBD
name: serviceName
dataType: string
status: current
description: Specifies the name of the
service.
7.274. flags
elementId: TBD
name: flags
dataType: string
status: current
description: Specifies miscellaneous settings
associated with the service with executing a program.
7.275. noAccess
elementId: TBD
name: noAccess
dataType: string
status: current
description: Specifies the remote hosts to
which the service is unavailable.
7.276. onlyFrom
elementId: TBD
name: onlyFrom
dataType: ipAddress
status: current
description: Specifies the remote hosts to
which the service is available.
7.277. port
elementId: TBD
name: port
dataType: integer
status: current
description: The port entity specifies the port
used by the service.
7.278. server
elementId: TBD
name: server
dataType: string
status: current
description: Specifies the executable that is
used to launch the service.
7.279. serverArguments
elementId: TBD
name: serverArguments
dataType: string
status: current
description: Specifies the arguments
that are passed to the executable when launching the service.
7.280. socketType
elementId: TBD
name: socketType
dataType: string
status: current
description: Specifies the type of socket
that is used by the service. Possible values include: stream,
dgram, raw, or seqpacket.
7.281. registeredServiceType
elementId: TBD
name: registeredServiceType
dataType: enumeration
structure: INTERNAL ; 0x1 ; The INTERNAL type is used to describe
services like echo, chargen, and others whose functionality is
supplied by xinetd itself.
RPC ; 0x2 ; The RPC type is used to describe services that
use remote procedure call ala NFS.
UNLISTED ; 0x3 ; The UNLISTED type is used to describe
services that aren't listed in /etc/protocols or /etc/rpc.
TCPMUX ; 0x4 ; The TCPMUX type is used to describe services
that conform to RFC 1078. This type indiciates that the service
is responsible for handling the protocol handshake.
TCPMUXPLUS ; 0x5 ; The TCPMUXPLUS type is used to describe
services that conform to RFC 1078. This type indicates that
xinetd is responsible for handling the protocol
handshake.
; 0x6 ; The empty string value is permitted here to allow
for detailed error reporting.
status: current
description: Specifies the type of internet service.
7.282. wait
elementId: TBD
name: wait
dataType: boolean
status: current
description: Specifies whether or not the service is single-threaded
or multi-threaded and whether or not xinetd accepts the connection
or the service accepts the connection. A value of 'true' indicates
that the service is single-threaded and the service will accept the
connection. A value of 'false' indicates that the service is multi-
threaded and xinetd will accept the connection.
7.283. disabled
elementId: TBD
name: disabled
dataType: boolean
status: current
description: Specifies whether or not the
service is disabled. A value of 'true' indicates that the
service is disabled and will not start. A value of
'false' indicates that the service is not disabled.
7.284. windowsView
elementId: TBD
name: windowsView
dataType: enumeration
structure: 32_bit ; 0x1 ; Indicates the 32_bit windows view.
64_bit ; 0x2 ; Indicates the 64_bit windows view.
; 0x3 ; The empty string value is permitted here to allow for
empty elements associated with error conditions.
status: current
description: Indicates from which
view (32-bit or 64-bit), the information was collected.
A value of '32_bit' indicates the Item was collected from
the 32-bit view. A value of '64-bit' indicates the Item
was collected from the 64-bit view.
7.285. fileauditedpermissions
elementId: TBD
name: fileauditedpermissions
dataType: list
structure: list (filepath, path, filename,
trusteeSid, trusteeName, auditStandardDelete,
auditStandardReadControl, auditStandardWriteDac,
auditStandardWriteOwner, auditStandardSynchronize,
auditAccessSystemSecurity, auditGenericRead, auditGenericWrite,
auditGenericExecute, auditGenericAll, auditFileReadData,
auditFileWriteData, auditFileAppendData, auditFileReadEa,
auditFileWriteEa, auditFileExecute, auditFileDeleteChild,
auditFileReadAttributes, auditFileWriteAttributes,
windowsView)
status: current
description: Stores the audited access rights of a file that a
system access control list (SACL) structure grants to a specified
trustee. The trustee's audited access rights are determined checking
all access control entries (ACEs) in the SACL.
7.286. trusteeName
elementId: TBD
name: trusteeName
dataType: string
status: current
description: Specifies the trustee name. A
trustee can be a user, group, or program (such as a Windows
service).
7.287. auditStandardDelete
elementId: TBD
name: auditStandardDelete
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: The right to delete the object.
7.288. auditStandardReadControl
elementId: TBD
name: auditStandardReadControl
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: The right to read the information in the object's
security descriptor, not including the information in the SACL.
7.289. auditStandardWriteDac
elementId: TBD
name: auditStandardWriteDac
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: The right to modify the DACL in the object's security
descriptor.
7.290. auditStandardWriteOwner
elementId: TBD
name: auditStandardWriteOwner
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: The right to change the owner in the object's security
descriptor.
7.291. auditStandardSynchronize
elementId: TBD
name: auditStandardSynchronize
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: The right to use the object for synchronization.
This enables a thread to wait until the object is in the signaled
state. Some object types do not support this access right.
7.292. auditAccessSystemSecurity
elementId: TBD
name: auditAccessSystemSecurity
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Indicates access to a system access control list (SACL).
7.293. auditGenericRead
elementId: TBD
name: auditGenericRead
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Read access.
7.294. auditGenericWrite
elementId: TBD
name: auditGenericWrite
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Write access.
7.295. auditGenericExecute
elementId: TBD
name: auditGenericExecute
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Execute access.
7.296. auditGenericAll
elementId: TBD
name: auditGenericAll
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Read, write, and execute access.
7.297. auditFileReadData
elementId: TBD
name: auditFileReadData
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Grants the right to read data from the file.
7.298. auditFileWriteData
elementId: TBD
name: auditFileWriteData
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Grants the right to write data to the file.
7.299. auditFileAppendData
elementId: TBD
name: auditFileAppendData
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Grants the right to append data to the file.
7.300. auditFileReadEa
elementId: TBD
name: auditFileReadEa
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Grants the right to read extended attributes.
7.301. auditFileWriteEa
elementId: TBD
name: auditFileWriteEa
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Grants the right to write extended attributes.
7.302. auditFileExecute
elementId: TBD
name: auditFileExecute
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Grants the right to execute a file.
7.303. auditFileDeleteChild
elementId: TBD
name: auditFileDeleteChild
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Right to delete a directory and all the files it
contains (its children), even if the files are read-only.
7.304. auditFileReadAttributes
elementId: TBD
name: auditFileReadAttributes
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Grants the right to read file attributes.
7.305. auditFileWriteAttributes
elementId: TBD
name: auditFileWriteAttributes
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description: Grants the right to change file attributes.
7.306. fileeffectiverights
elementId: TBD
name: fileeffectiverights
dataType: list
structure: list (filepath, path, filename,
trusteeSid, trusteeName, standardDelete, standardReadControl,
standardWriteDac, standardWriteOwner,
standardSynchronize, accessSystemSecurity, genericRead,
genericWrite, genericExecute, genericAll, fileReadData,
fileWriteData, fileAppendData, fileReadEa, fileWriteEa,
fileExecute, fileDeleteChild, fileReadAttributes,
fileWriteAttributes, windowsView)
status: current
description: Stores the effective rights of a file that a
discretionary access control list (DACL) structure grants
to a specified trustee. The trustee's effective rights
are determined checking all access-allowed and access-denied
access control entries (ACEs) in the DACL.
7.307. standardDelete
elementId: TBD
name: standardDelete
dataType: boolean
status: current
description: The right to delete the
object.
7.308. standardReadControl
elementId: TBD
name: standardReadControl
dataType: boolean
status: current
description: The right to read
the information in the object's security descriptor, not
including the information in the SACL.
7.309. standardWriteDac
elementId: TBD
name: standardWriteDac
dataType: boolean
status: current
description: The right to modify the
DACL in the object's security descriptor.
7.310. standardWriteOwner
elementId: TBD
name: standardWriteOwner
dataType: boolean
status: current
description: The right to change
the owner in the object's security descriptor.
7.311. standardSynchronize
elementId: TBD
name: standardSynchronize
dataType: boolean
status: current
description: The right to use the
object for synchronization. This enables a thread to wait
until the object is in the signaled state. Some object
types do not support this access right.
7.312. accessSystemSecurity
elementId: TBD
name: accessSystemSecurity
dataType: boolean
status: current
description: Indicates access to
a system access control list (SACL).
7.313. genericRead
elementId: TBD
name: genericRead
dataType: boolean
status: current
description: Read access.
7.314. genericWrite
elementId: TBD
name: genericWrite
dataType: boolean
status: current
description: Write access.
7.315. genericExecute
elementId: TBD
name: genericExecute
dataType: boolean
status: current
description: Execute access.
7.316. genericAll
elementId: TBD
name: genericAll
dataType: boolean
status: current
description: Read, write, and execute
access.
7.317. fileReadData
elementId: TBD
name: fileReadData
dataType: boolean
status: current
description: Grants the right to read
data from the file
7.318. fileWriteData
elementId: TBD
name: fileWriteData
dataType: boolean
status: current
description: Grants the right to write
data to the file.
7.319. fileAppendData
elementId: TBD
name: fileAppendData
dataType: boolean
status: current
description: Grants the right to
append data to the file.
7.320. fileReadEa
elementId: TBD
name: fileReadEa
dataType: boolean
status: current
description: Grants the right to read
extended attributes.
7.321. fileWriteEa
elementId: TBD
name: fileWriteEa
dataType: boolean
status: current
description: Grants the right to write
extended attributes.
7.322. fileExecute
elementId: TBD
name: fileExecute
dataType: boolean
status: current
description: Grants the right to execute
a file.
7.323. fileDeleteChild
elementId: TBD
name: fileDeleteChild
dataType: boolean
status: current
description: Right to delete a
directory and all the files it contains (its children),
even if the files are read-only.
7.324. fileReadAttributes
elementId: TBD
name: fileReadAttributes
dataType: boolean
status: current
description: Grants the right to
read file attributes.
7.325. fileWriteAttributes
elementId: TBD
name: fileWriteAttributes
dataType: boolean
status: current
description: Grants the right to
change file attributes.
7.326. groupInfo
elementId: TBD
name: groupInfo
dataType: list
structure: list (group, username, subgroup)
status: current
description: Specifies the different users and subgroups, that
directly belong to specific groups.
7.327. group
elementId: TBD
name: group
dataType: string
status: current
description: Represents the name of a particular
group.
7.328. user
elementId: TBD
name: user
dataType: string
status: current
description: Represents the name of a particular
user.
7.329. subgroup
elementId: TBD
name: subgroup
dataType: string
status: current
description: Represents the name of a
particular subgroup in the specified group.
7.330. groupSidInfo
elementId: TBD
name: groupSidInfo
dataType: list
structure: list (groupSid, userSid, subgroupSid)
status:
current
description: Specifies the different users and subgroups, that
directly belong to specific groups
(identified by SID).
7.331. userSidInfo
elementId: TBD
name: userSidInfo
dataType: list
structure: list (userSid, enabled, groupSid, lastLogon)
status: current
description: Specifies the different groups (identified by SID)
that a user belongs to.
7.332. userSid
elementId: TBD
name: userSid
dataType: string
status: current
description: Represents the SID of a
particular user.
7.333. subgroupSid
elementId: TBD
name: subgroupSid
dataType: string
status: current
description: Represents the SID of a
particular subgroup.
7.334. lockoutpolicy
elementId: TBD
name: lockoutpolicy
dataType: list
structure: list (forceLogoff, lockoutDuration,
lockoutObservationWindow, lockoutThreshold)
status: current
description: Specifies various attributes associated
with lockout information for users and global groups in the
security database.
7.335. forceLogoff
elementId: TBD
name: forceLogoff
dataType: integer
status: current
description: Specifies, in seconds, the
amount of time between the end of the valid logon time and
the time when the user is forced to log off the
network.
7.336. lockoutDuration
elementId: TBD
name: lockoutDuration
dataType: integer
status: current
description: Specifies, in seconds,
how long a locked account remains locked before it is
automatically unlocked.
7.337. lockoutObservationWindow
elementId: TBD
name: lockoutObservationWindow
dataType: integer
status: current
description: Specifies the
maximum time, in seconds, that can elapse between any two
failed logon attempts before lockout occurs.
7.338. lockoutThreshold
elementId: TBD
name: lockoutThreshold
dataType: integer
status: current
description: Specifies the number of
invalid password authentications that can occur before an
account is marked "locked out."
7.339. passwordpolicy
elementId: TBD
name: passwordpolicy
dataType: list
structure: list (maxPasswdAge, minPasswdAge,
minPasswdLen, passwordHistLen, passwordComplexity,
reversibleEncryption)
status: current
description: Specifies
policy information associated with passwords.
7.340. maxPasswdAge
elementId: TBD
name: maxPasswdAge
dataType: integer
status: current
description: Specifies, in seconds (from
a DWORD), the maximum allowable password age. A value of
TIMEQ_FOREVER (max DWORD value, 4294967295) indicates
that the password never expires. The minimum valid value
for this element is ONE_DAY (86400). See the
USER_MODALS_INFO_0 structure returned by a call to
NetUserModalsGet().
7.341. minPasswdAge
elementId: TBD
name: minPasswdAge
dataType: integer
status: current
description: Specifies the minimum
number of seconds that can elapse between the time a password
changes and when it can be changed again. A value of
zero indicates that no delay is required between password
updates.
7.342. minPasswdLen
elementId: TBD
name: minPasswdLen
dataType: integer
status: current
description: Specifies the minimum
allowable password length. Valid values for this element are
zero through PWLEN.
7.343. passwordHistLen
elementId: TBD
name: passwordHistLen
dataType: integer
status: current
description: Specifies the length of
password history maintained. A new password cannot match any
of the previous usrmod0_password_hist_len passwords.
Valid values for this element are zero through DEF_MAX_PWHIST.
7.344. passwordComplexity
elementId: TBD
name: passwordComplexity
dataType: boolean
status: current
description: Indicates whether
passwords must meet the complexity requirements put forth
by the operating system.
7.345. reversibleEncryption
elementId: TBD
name: reversibleEncryption
dataType: boolean
status: current
description: Indicates whether
or not passwords are stored using reversible encryption.
7.346. portInfo
elementId: TBD
name: portInfo
dataType: list
structure: list (localAddress, localPort, transportProtocol,
pid, foreignAddress, foreignPort)
status: current
description: Information about open listening ports.
7.347. foreignPort
elementId: TBD
name: foreignPort
dataType: string
status: current
description: The TCP or UDP port to which
the program communicates.
7.348. printereffectiverights
elementId: TBD
name: printereffectiverights
dataType: list
structure: list (printerName, trusteeSid,
standardDelete, standardReadControl, standardWriteDac,
standardWriteOwner, standardSynchronize,
accessSystemSecurity, genericRead, genericWrite,
genericExecute, genericAll, printerAccessAdminister,
printerAccessUse, jobAccessAdminister, jobAccessRead)
status: current
description: Stores the effective rights of a printer that a
discretionary access control list (DACL) structure grants to a
specified trustee. The trustee's effective rights are determined
checking all access-allowed and access-denied access control
entries (ACEs) in the DACL.
7.349. printerName
elementId: TBD
name: printerName
dataType: string
status: current
description: Specifies the name of the
printer.
7.350. printerAccessAdminister
elementId: TBD
name: printerAccessAdminister
dataType: boolean
status: current
description:
7.351. printerAccessUse
elementId: TBD
name: printerAccessUse
dataType: boolean
status: current
description:
7.352. jobAccessAdminister
elementId: TBD
name: jobAccessAdminister
dataType: boolean
status: current
description:
7.353. jobAccessRead
elementId: TBD
name: jobAccessRead
dataType: boolean
status: current
description:
7.354. registry
elementId: TBD
name: registry
dataType: list
structure: list (hive, key, registryKeyName, lastWriteTime,
registryKeyType, registryKeyValue, windowsView)
status: current
description: Specifies information that can be
collected about a particular registry key.
7.355. hive
elementId: TBD
name: hive
dataType: enumeration
structure: HKEY_CLASSES_ROOT ; 0x1 ; This registry subtree
contains information that associates file types with programs
and configuration data for automation (e.g. COM
objects and Visual Basic Programs).
HKEY_CURRENT_CONFIG ; 0x2 ; This registry subtree contains
configuration data for the current hardware profile.
HKEY_CURRENT_USER ; 0x3 ; This registry subtree contains the
user profile of the user that is currently logged into the
system.
HKEY_LOCAL_MACHINE ; 0x4 ; This registry subtree contains
information about the local system.
HKEY_USERS ; 0x5 ; This registry subtree contains user-specific
data.
; 0x6 ; The empty string value is permitted here to allow
for detailed error reporting.
status: current
description: The
hive that the registry key belongs to.
7.356. registryKey
elementId: TBD
name: registryKey
dataType: string
status: current
description: Describes the registry key.
Note that the hive portion of the string should not be
included, as this data can be found under the hive
element.
7.357. registryKeyName
elementId: TBD
name: registryKeyName
dataType: string
status: current
description: Describes the name of a
registry key.
7.358. lastWriteTime
elementId: TBD
name: lastWriteTime
dataType: integer
status: current
description: The last time that the key or any of its value entries
were modified. The value of this entity represents the
FILETIME structure which is a 64-bit value representing the
number of 100-nanosecond intervals since January 1, 1601
(UTC). Last write time can be queried on any key, with hives
being classified as a type of key. When collecting only
information about a registry hive or key the last write time
will be the time the key or any of its entries were modified.
When collecting only information about a registry name the
last write time will be the time the containing key was
modified. Thus when collecting information about a registry
name, the last write time does not correlate directly
to the specified name. See the RegQueryInfoKey function
lpftLastWriteTime.
7.359. registryKeyType
elementId: TBD
name: registryKeyType
dataType: enumeration
structure: reg_binary ; 0x1 ; The reg_binary type
is used by registry keys that specify binary data in any
form.
reg_dword ; 0x2 ; The reg_dword type is used by
registry keys that specify an unsigned 32-bit integer.
reg_dword_little_endian ; 0x3 ; The reg_dword_little_endian
type is used by registry keys that specify an unsigned 32-bit
little-endian integer. It is designed to run on
little-endian computer architectures.
reg_dword_big_endian ; 0x4 ; The reg_dword_big_endian type
is used by registry keys that specify an unsigned 32-bit
big-endian integer. It is designed to run on big-endian
computer architectures.
reg_expand_sz ; 0x5 ; The reg_expand_sz type is used by
registry keys to specify a null-terminated
string that contains unexpanded references to environment
variables (for example, "%PATH%").
reg_link ; 0x6 ; The reg_link type is used by the registry
keys for null-terminated unicode strings. It is related to
target path of a symbolic link created by the
RegCreateKeyEx function.
reg_multi_sz ; 0x7 ; The reg_multi_sz type is used by
registry keys that specify an array of null-terminated
strings, terminated by two null characters.
reg_none; 0x8 ;
The reg_none type is used by registry keys that have no
defined value type.
reg_qword; 0x9 ; The reg_qword type is used by registry keys
that specify an unsigned 64-bit integer.
reg_qword_little_endian; 0xA ; The reg_qword_little_endian
type is used by registry keys that specify an unsigned
64-bit integer in little-endian computer architectures.
reg_sz; 0xB ; The reg_sz type is used by registry keys that
specify a single null-terminated string.
reg_resource_list; 0xC ; The reg_resource_list type is used
by registry keys that specify a resource list.
reg_full_resource_descriptor; 0xD ; The
reg_full_resource_descriptor type is used by registry
keys that specify a full resource descriptor.
reg_resource_requirements_list; 0xE ; The
reg_resource_requirements_list type is used by registry keys
that specify a resource requirements list.
; 0xF ; The empty string value is permitted here to allow
for detailed error reporting.
status: current
description:
Specifies the type of data stored by the registry key.
7.360. registryKeyValue
elementId: TBD
name: registryKeyValue
dataType: string
status: current
description: Holds the actual value
of the specified registry key. The representation of the
value as well as the associated datatype attribute
depends on type of data stored in the registry key. If the
value being tested is of type REG_BINARY, then the
datatype attribute should be set to 'binary' and the data
represented by the value entity should follow the
xsd:hexBinary form. (each binary octet is encoded as two hex
digits) If the value being tested is of type
REG_DWORD, REG_QWORD, REG_DWORD_LITTLE_ENDIAN,
REG_DWORD_BIG_ENDIAN, or REG_QWORD_LITTLE_ENDIAN then the
datatype attribute should be set to 'int' and the value
entity should represent the data as an unsigned integer.
DWORD and QWORD values represnt unsigned 32-bit and 64-bit
integers, respectively. If the value being tested is of type
REG_EXPAND_SZ, then the datatype attribute should be set to
'string' and the pre-expanded string should be
represented by the value entity. If the value being tested
is of type REG_MULTI_SZ, then only a single string (one
of the multiple strings) should be tested using the value
entity with the datatype attribute set to 'string'. In
order to test multiple values, multiple OVAL registry tests
should be used. If the specified registry key is of
type REG_SZ, then the datatype should be 'string' and the
value entity should be a copy of the string. If the
value being tested is of type REG_LINK, then the datatype
attribute should be set to 'string' and the
null-terminated Unicode string should be represented by the
value entity.
7.361. regkeyauditedpermissions
elementId: TBD
name: regkeyauditedpermissions
dataType: list
structure: list (key, trusteeSid, trusteeName,
standardDelete, standardReadControl, standardWriteDac,
standardWriteOwners, tandardSynchronize,
accessSystemSecurity, genericRead, genericWrite,
genericExecute, genericAll, keyQueryValue, keySetValue,
keyCreateSubKey, keyEnumerateSubKeys, keyNotify,
keyCreateLink, keyWow6464Key, keyWow6432Key, keyWow64Res,
windowsView)
status: current
description: Stores the audited access rights of a registry key
that a system access control list (SACL) structure grants to a
specified trustee. The trustee's audited access rights are
determined checking all access control entries (ACEs) in the SACL.
7.362. auditKeyQueryValue
elementId: TBD
name: auditKeyQueryValue
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description:
7.363. auditKeySetValue
elementId: TBD
name: auditKeySetValue
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description:
7.364. auditKeyCreateSubKey
elementId: TBD
name: auditKeyCreateSubKey
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.
; 0x5 ; The empty string value is permitted here to allow for
detailed error reporting.
status: current
description:
7.365. auditKeyEnumerateSubKeys
elementId: TBD
name: auditKeyEnumerateSubKeys
dataType: enumeration
structure: AUDIT_FAILURE ; 0x1 ; The audit type AUDIT_FAILURE is
used to perform audits on all unsuccessful occurrences of
specified events when auditing is enabled.
AUDIT_NONE ; 0x2 ; The audit type AUDIT_NONE is used to cancel
all auditing options for the specified events.
AUDIT_SUCCESS ; 0x3 ; The audit type AUDIT_SUCCESS is used to
perform audits on all successful occurrences of the specified
events when auditing is enabled.
AUDIT_SUCCESS_FAILURE ; 0x4 ; The audit type AUDIT_SUCCESS_FAILURE
is used to perform audits on all successful and unsuccessful
occurrences of the specified events when auditing is enabled.