You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The MacOS SystemProfiler object, state, and item data_type elements, we're running into a tangle. OVAL specifies a valid values list (enumeration) for each (EntityObjectDataTypeType, EntityStateDataTypeType, and EntityItemDataTypeType). This list is incomplete when compared to the data_types available on the OS. As has already happened, we should probably expect Apple to add more data_types to the SystemProfiler, over time. For content authors who wish to use data_types not supported by OVAL, this causes constant XML validation error noise.
'Seems there are two options. Continually update the valid values lists for the data_type elements as Apple changes them. --OR-- Change those three elements to simple strings.
I don't see any real benefit in controlling these values. The SCAP processor can retrieve the list of valid data_types from the system being scanned and control the querying of info from the system according to those system-supplied data_type values.
I suggest we change the data_type entities to be oval-def:EntityObjectStringType and oval-sc:EntityItemStringType.
Also, per Mr. Solin's suggestion we would need to modify the documentation to direct SCAP processors to use only those data_types actually found on the machine (via system_profiler --listDataTypes).
The text was updated successfully, but these errors were encountered:
@julmerII commented on Tue Aug 07 2018
The MacOS SystemProfiler object, state, and item data_type elements, we're running into a tangle. OVAL specifies a valid values list (enumeration) for each (EntityObjectDataTypeType, EntityStateDataTypeType, and EntityItemDataTypeType). This list is incomplete when compared to the data_types available on the OS. As has already happened, we should probably expect Apple to add more data_types to the SystemProfiler, over time. For content authors who wish to use data_types not supported by OVAL, this causes constant XML validation error noise.
'Seems there are two options. Continually update the valid values lists for the data_type elements as Apple changes them. --OR-- Change those three elements to simple strings.
I don't see any real benefit in controlling these values. The SCAP processor can retrieve the list of valid data_types from the system being scanned and control the querying of info from the system according to those system-supplied data_type values.
I suggest we change the data_type entities to be oval-def:EntityObjectStringType and oval-sc:EntityItemStringType.
Also, per Mr. Solin's suggestion we would need to modify the documentation to direct SCAP processors to use only those data_types actually found on the machine (via system_profiler --listDataTypes).
The text was updated successfully, but these errors were encountered: