forked from OVALProject/Sandbox
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathx-vmware-esxi-55-schema.xsd
2498 lines (2440 loc) · 148 KB
/
x-vmware-esxi-55-schema.xsd
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="utf-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:oval="http://oval.mitre.org/XMLSchema/oval-common-5" xmlns:oval-def="http://oval.mitre.org/XMLSchema/oval-definitions-5" xmlns:x-vmware-esxi55="http://oval.mitre.org/XMLSchema/oval-definitions-5#esxi" xmlns:sch="http://purl.oclc.org/dsdl/schematron" targetNamespace="http://oval.mitre.org/XMLSchema/oval-definitions-5#esxi" elementFormDefault="qualified" version="5.11">
<xsd:import namespace="http://oval.mitre.org/XMLSchema/oval-definitions-5" schemaLocation="oval-definitions-schema.xsd"/>
<xsd:annotation>
<xsd:documentation>The following is a proposal for the experimental x-vmware-esxi55-def tests and x-vmware-esxi55-sc: items that will support assessments of VMware ESXi hosts and VMs.</xsd:documentation>
<xsd:appinfo>
<schema>Experimental Schema for VMware ESXi 5.5 Tests</schema>
<version>5.11</version>
<date>8/11/2014 8:00:00 AM</date>
<terms_of_use>Copyright (c) 2002-2013, The MITRE Corporation. All rights reserved. The contents of this file are subject to the terms of the OVAL License located at http://oval.mitre.org/oval/about/termsofuse.html. See the OVAL License for the specific language governing permissions and limitations for use of this schema. When distributing copies of the OVAL Schema, this license header must be included.</terms_of_use>
<sch:ns prefix="oval-def" uri="http://oval.mitre.org/XMLSchema/oval-definitions-5"/>
<sch:ns prefix="x-vmware-esxi55-def" uri="http://oval.mitre.org/XMLSchema/x-vmware-esxi55"/>
<sch:ns prefix="xsi" uri="http://www.w3.org/2001/XMLSchema-instance"/>
</xsd:appinfo>
</xsd:annotation>
<!-- =============================================================================== -->
<!-- VMHost-Specific Object -->
<!-- =============================================================================== -->
<xsd:complexType name="VMHostObjectBaseType">
<xsd:annotation>
<xsd:documentation>Base type for VMHost-based Objects</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="oval-def:ObjectType">
<xsd:sequence>
<xsd:choice>
<xsd:element ref="oval-def:set"/>
<xsd:sequence>
<xsd:element name="connection_string" type="oval-def:EntityObjectStringType" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The connection_string element specifies the connection string to use in order to connect to the ESXi/vSphere host, and should take the form of user/pwd@host.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="vmhost_name" type="oval-def:EntityObjectStringType" nillable="true" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the ESXi host for which to collect configuration settings. If this element is set to xsi:nil="true", then all VMHost's information is collected.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<!--<xsd:element ref="oval-def:filter" minOccurs="0" maxOccurs="unbounded"/>-->
</xsd:sequence>
</xsd:choice>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="VMHostStateBaseType">
<xsd:annotation>
<xsd:documentation>Base type for VMHost-based States</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension base="oval-def:StateType">
<xsd:sequence>
<xsd:element name="connection_string" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The connection_string element specifies the connection string to use in order to connect to the ESXi/vSphere host, and should take the form of user/pwd@host.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="vmhost_name" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the ESXi host for which information is collected.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<!-- =============================================================================== -->
<!-- VMHost Acceptance Level Test -->
<!-- =============================================================================== -->
<xsd:element name="vmhost_acceptancelevel_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The vmhost_acceptancelevel_test is used to determine if the software installed for the VMHost represents untested code.
It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description
for more information. The required object element references a vmhost_acceptancelevel_object and the optional state element
specifies the data to check.
</xsd:documentation>
<xsd:documentation>
The ESXi image profile supports 4 acceptance levels:
1. VMwareCertified - created, tested and signed by VMware
2. VMwareAccepted - created by a VMware partner but tested and signed by VMware
3. PartnerSupported - created, tested and signed by a certified VMware partner
4. CommunitySupported - not been tested by VMware or a VMware partner
</xsd:documentation>
<xsd:documentation>
PowerCLI Equivalent:
Foreach ($VMHost in Get-VMHost ) {
$ESXCli = Get-EsxCli -VMHost $VMHost
$VMHost | Select Name, @{N="AcceptanceLevel";E={$ESXCli.software.acceptance.get()}}
}
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:TestType">
<xsd:sequence>
<xsd:element name="object" type="oval-def:ObjectRefType"/>
<xsd:element name="state" type="oval-def:StateRefType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_acceptancelevel_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The vmhost_acceptancelevel_object element is used by the vmhost_acceptancelevel_test to define the object to be evaluated.
Each object extends the standard ObjecType as defined in the oval-definitions-schema and one should refer to the ObjectType
description for more information. The common set element allows complex objects to be created using filters and set logic.
Again, please refer to the description of the set element in the oval-definitions-schema.
</xsd:documentation>
<xsd:documentation>
A vmhost_acceptancelevel_object consists of a connection string identifying the host connection information, and a VMHost name that
identifies the ESXi host for which one is collecting acceptance level information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostObjectBaseType">
<xsd:sequence>
<xsd:element ref="oval-def:filter" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_acceptancelevel_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The vmhost_acceptancelevel_state element defines the information that can be used to evaluate the specified ESXi hosts acceptance level information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostStateBaseType">
<xsd:sequence>
<xsd:element name="acceptance_level" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The software acceptance level for the associated ESXi host.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- VMHost VIB Test -->
<!-- =============================================================================== -->
<xsd:element name="vmhost_vib_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The vmhost_vib_test is used to test various properties of software installed for a vSphere Installation Bundle (VIB).
A VIB is a collection of files that are packaged into an archive. The VIB contains a signature
file that is used to verify the level of trust. It extends the standard TestType as defined in the oval-definitions-schema
and one should refer to the TestType description for more information. The required object element references a
vmhost_vib_object and the optional state element specifies the data to check.
</xsd:documentation>
<xsd:documentation>
PowerCLI Equivalent:
# List only the vibs which are not at "VMwareCertified" or "VMwareAccepted" or "PartnerSupported" acceptance level
Foreach ($VMHost in Get-VMHost ) {
$ESXCli = Get-EsxCli -VMHost $VMHost
$ESXCli.software.vib.list()
}
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:TestType">
<xsd:sequence>
<xsd:element name="object" type="oval-def:ObjectRefType"/>
<xsd:element name="state" type="oval-def:StateRefType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_vib_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The vmhost_vib_object element is used by the vmhost_vib_test to define the object to be evaluated.
Each object extends the standard ObjecType as defined in the oval-definitions-schema and one should refer to the ObjectType
description for more information. The common set element allows complex objects to be created using filters and set logic.
Again, please refer to the description of the set element in the oval-definitions-schema.
</xsd:documentation>
<xsd:documentation>
A vmhost_vib_object consists of a connection string identifying the host connection information, a VMHost
name that identifies the ESXi host for which one is collecting VIB information, and the name of a VIB to collect.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostObjectBaseType">
<xsd:sequence>
<xsd:element name="vib_name" type="oval-def:EntityObjectStringType" nillable="true" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the VIB to collect. If this element is set to xsi:nil="true", then all VIBs are collected.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="oval-def:filter" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_vib_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The vmhost_vibacceptancelevel_state element defines the information that can be used to evaluate the specified VIB acceptance level information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostStateBaseType">
<xsd:sequence>
<xsd:element name="vib_name" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The VIB name</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="acceptance_level" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The software acceptance level for the associated VIB</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="creation_date" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>VIB Creation Date</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="vib_id" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>VIB ID</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="install_date" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>VIB Installation Date</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="status" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>VIB Status</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="vendor" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>VIB Vendor</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="version" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>VIB Version</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- VMHost Module Test -->
<!-- =============================================================================== -->
<xsd:element name="vmhost_module_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The vmhost_modules_test is used to determine if any ESXi host's loaded kernel modules lack valid digital signatures.
It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description
for more information. The required object element references a vmhost_modules_object and the optional state element
specifies the data to check.
</xsd:documentation>
<xsd:documentation>
VMware provides digital signatures for kernel modules. By default the ESXi host does not permit loading of kernel modules
that lack a valid digital signature. However, this behavior can be overridden allowing unauthorized kernel modules to be loaded.
Untested or malicious kernel modules loaded on the ESXi host can put the host at risk for instability and/or exploitation.
</xsd:documentation>
<xsd:documentation>
PowerCLI Equivalent:
# List the system modules and Signature Info for each host
Foreach ($VMHost in Get-VMHost ) {
$ESXCli = Get-EsxCli -VMHost $VMHost
$ESXCli.system.module.list() | Foreach {
$ESXCli.system.module.get($_.Name) | Select @{N="VMHost";E={$VMHost}}, Module, License, Modulefile, Version, SignedStatus, SignatureDigest, SignatureFingerPrint
}
}
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:TestType">
<xsd:sequence>
<xsd:element name="object" type="oval-def:ObjectRefType"/>
<xsd:element name="state" type="oval-def:StateRefType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_module_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The vmhost_module_object element is used by the vmhost_module_test to define the object to be evaluated.
Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType
description for more information. The common set element allows complex objects to be created using filters and set logic.
Again, please refer to the description of the set element in the oval-definitions-schema.
</xsd:documentation>
<xsd:documentation>
A vmhost_module_object consists of a connection string identifying the host connection information, a VMHost name that
identifies the ESXi host for which one is collecting loaded kernel module information, and a module name identifying the
kernel module to collect.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostObjectBaseType">
<xsd:sequence>
<xsd:element name="module_name" type="oval-def:EntityObjectStringType" nillable="true" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the kernel module to collect. If this element is set to xsi:nil="true", then all kernel modules are collected.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="oval-def:filter" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_module_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The vmhost_module_state element defines the information that can be used to evaluate the specified ESXi hosts loaded kernel module information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostStateBaseType">
<xsd:sequence>
<xsd:element name="module_name" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the kernel module</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="license" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the license holder for the kernel module.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="module_file" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The path to the kernel module file.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="version" type="oval-def:EntityStateVersionType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The kernel module version information.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="signed_status" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The digital signature status of the kernel module.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="signature_digest" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Digest of the kernel module's digital signature</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="signature_fingerprint" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Fingerprint of the kernel module's digital signature</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- VMHost Core Dump Test -->
<!-- =============================================================================== -->
<xsd:element name="vmhost_coredump_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The vmhost_coredump_test is used to validate the configuration of a centralized location to collect ESXi host core dumps.
The VMware vSphere Network Dump Collector service allows for collecting diagnostic information from a host that experiences a critical fault.
It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description
for more information. The required object element references a vmhost_coredump_object and the optional state element
specifies the data to check.
</xsd:documentation>
<xsd:documentation>
PowerCLI Equivalent:
Foreach ($VMHost in Get-VMHost ) {
$ESXCli = Get-EsxCli -VMHost $VMHost;
$ESXCli.system.coredump.network.get() | Select @{N="VMHost";E={$VMHost}}, Enabled, HostVnic, NetworkServerIP, NetworkServerPort
}
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:TestType">
<xsd:sequence>
<xsd:element name="object" type="oval-def:ObjectRefType"/>
<xsd:element name="state" type="oval-def:StateRefType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_coredump_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The vmhost_coredump_object element is used by the vmhost_coredump_test to define the object to be evaluated.
Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType
description for more information. The common set element allows complex objects to be created using filters and set logic.
Again, please refer to the description of the set element in the oval-definitions-schema.
</xsd:documentation>
<xsd:documentation>
A vmhost_coredump_object consists of a connection string identifying the host connection information, and a VMHost name that
identifies the ESXi host for which one is collecting ESXi core dump configuration information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostObjectBaseType">
<xsd:sequence>
<xsd:element ref="oval-def:filter" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_coredump_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The vmhost_coredump_state element defines the information that can be used to evaluate the specified ESXi hosts core dump information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostStateBaseType">
<xsd:sequence>
<xsd:element name="enabled" type="oval-def:EntityStateBoolType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Displays whether or not the ESXi dump collector is enabled for the ESXi host</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="host_vnic" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The ESXi host's configured core dump destination vnic</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="network_server_ip" type="oval-def:EntityStateIPAddressStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The ESXi host's configured core dump destination IP</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="network_server_port" type="oval-def:EntityStateIntType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The ESXi host's configured core dump destination port</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- VMHost Web Server SSL Test -->
<!-- =============================================================================== -->
<xsd:element name="vmhost_webserverssl_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The vmhost_webserverssl_test is used to determine if any expired or revoked SSL certificates exist on the ESXi host.
It extends the standard TestType as defined in the oval-definitions-schema and one should refer to the TestType description
for more information. The required object element references a vmhost_webserverssl_object and the optional state element
specifies the data to check.
</xsd:documentation>
<xsd:documentation>
Leaving expired or revoked certificates on your vCenter Server system can compromise your environment. By default, each
ESXi host does not have Certificate Revocation Lists (CRL) checking available. Revoked certificates must be checked and
removed manually. Replacing certificates will avoid having users get used to clicking through browser warnings. The
warning might be an indication of a man-in-the-middle attack, and only inspection of the certificate and thumbprint can
guard against such attacks.
</xsd:documentation>
<xsd:documentation>
PowerCLI Equivalent:
# Check for Host Certificates
Get-VMHost | Foreach {
Test-WebServerSSL -URL $_.Name | Select OriginalURi, CertificateIsValid, Issuer,
@{N="Expires";E={$_.Certificate.NotAfter} },
@{N="DaysTillExpire";E={(New-TimeSpan -Start (Get-Date) -End ($_.Certificate.NotAfter)).Days} }
}
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:TestType">
<xsd:sequence>
<xsd:element name="object" type="oval-def:ObjectRefType"/>
<xsd:element name="state" type="oval-def:StateRefType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_webserverssl_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The vmhost_webserverssl_object element is used by the vmhost_webserverssl_test to define the object to be evaluated.
Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType
description for more information. The common set element allows complex objects to be created using filters and set logic.
Again, please refer to the description of the set element in the oval-definitions-schema.
</xsd:documentation>
<xsd:documentation>
A vmhost_webserverssl_object consists of a connection string identifying the host connection information, and a VMHost name that
identifies the ESXi host for which one is collecting SSL certificate information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostObjectBaseType">
<xsd:sequence>
<xsd:element ref="oval-def:filter" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_webserverssl_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The vmhost_webserverssl_state element defines the information that can be used to evaluate the specified ESXi hosts web server ssl certificate information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostStateBaseType">
<xsd:sequence>
<xsd:element name="original_uri" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The original URI of the ESXi host</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="certificate_is_valid" type="oval-def:EntityStateBoolType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Whether or not the ESXi host certificate is valid</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="issuer" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The certificate issuer</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="expires" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The certificate expiration date and time (formatted as a string)</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="days_till_expire" type="oval-def:EntityStateIntType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The number of days before the certificate expires</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- VMHost Authentication Test -->
<!-- =============================================================================== -->
<xsd:element name="vmhost_authentication_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The vmhost_authentication_test is used to determine if ESXi is configured to use a directory service such as Active Directory
to manage users and groups. It extends the standard TestType as defined in the oval-definitions-schema and one should refer
to the TestType description for more information. The required object element references a vmhost_authentication_object and the
optional state element specifies the data to check.
</xsd:documentation>
<xsd:documentation>
PowerCLI Equivalent:
# Check each host and their domain membership status
Get-VMHost | Get-VMHostAuthentication | Select VmHost, Domain, DomainMembershipStatus
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:TestType">
<xsd:sequence>
<xsd:element name="object" type="oval-def:ObjectRefType"/>
<xsd:element name="state" type="oval-def:StateRefType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_authentication_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The vmhost_authentication_object element is used by the vmhost_authentication_test to define the object to be evaluated.
Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType
description for more information. The common set element allows complex objects to be created using filters and set logic.
Again, please refer to the description of the set element in the oval-definitions-schema.
</xsd:documentation>
<xsd:documentation>
A vmhost_authentication_object consists of a connection string identifying the host connection information, and a VMHost name that
identifies the ESXi host being probed for active directory information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostObjectBaseType">
<xsd:sequence>
<xsd:element ref="oval-def:filter" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_authentication_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The vmhost_authentication_state element defines the information that can be used to evaluate the specified ESXi hosts domain and domain membership information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostStateBaseType">
<xsd:sequence>
<xsd:element name="domain" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the domain</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="domain_membership_status" type="x-vmware-esxi55:EntityStateDomainMembershipStatusType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The status of the ESXi host's membership in the domain</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- VMHost Account Test -->
<!-- =============================================================================== -->
<xsd:element name="vmhost_account_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The vmhost_account_test is used to determine certain aspects of the user accounts on an ESXi host.
It extends the standard TestType as defined in the oval-definitions-schema and one should refer
to the TestType description for more information. The required object element references a vmhost_account_object and the
optional state element specifies the data to check.
</xsd:documentation>
<xsd:documentation>
PowerCLI Equivalent:
Get-VMHostAccount | Select Name, Domain, Description, ShellAccessEnabled
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:TestType">
<xsd:sequence>
<xsd:element name="object" type="oval-def:ObjectRefType"/>
<xsd:element name="state" type="oval-def:StateRefType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_account_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The vmhost_account_object element is used by the vmhost_account_test to define the object to be evaluated.
Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType
description for more information. The common set element allows complex objects to be created using filters and set logic.
Again, please refer to the description of the set element in the oval-definitions-schema.
</xsd:documentation>
<xsd:documentation>
A vmhost_account_object consists of a connection string identifying the host connection information, a VMHost name, and an
account name, and is designed to ollect ESXi host user account information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostObjectBaseType">
<xsd:sequence>
<xsd:element name="account_name" type="oval-def:EntityObjectStringType" nillable="true" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The account_name element details the name of the VMHost's user account to collect.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="oval-def:filter" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_account_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The vmhost_account_state element defines the information that can be used to evaluate the specified ESXi host user account information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostStateBaseType">
<xsd:sequence>
<xsd:element name="account_name" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The user account name on the ESXi host</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="domain" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the domain to which the user account belongs</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="description" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Descriptive information about the user account</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="shell_access_enabled" type="oval-def:EntityStateBoolType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>true if ESXi shell access is enabled for the user account; false otherwise</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="role" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>the role granted to the host account</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- VMHost SNMP Test -->
<!-- =============================================================================== -->
<xsd:element name="vmhost_snmp_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The vmhost_snmp_test is used to determine certain aspects of an ESXi host's SNMP configuration.
It extends the standard TestType as defined in the oval-definitions-schema and one should refer
to the TestType description for more information. The required object element references a
vmhost_snmp_object and the optional state element specifies the data to check.
</xsd:documentation>
<xsd:documentation>
PowerCLI Equivalent:
Get-VMHostSnmp | Select VMHost, Enabled, Port, ReadOnlyCommunities
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:TestType">
<xsd:sequence>
<xsd:element name="object" type="oval-def:ObjectRefType"/>
<xsd:element name="state" type="oval-def:StateRefType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_snmp_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The vmhost_snmp_object element is used by the vmhost_snmp_test to define the object to be evaluated.
Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType
description for more information. The common set element allows complex objects to be created using filters and set logic.
Again, please refer to the description of the set element in the oval-definitions-schema.
</xsd:documentation>
<xsd:documentation>
A vmhost_account_object consists of a connection string identifying the host connection information, and is designed to
collect ESXi host SNMP configuration information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostObjectBaseType">
<xsd:sequence>
<xsd:element ref="oval-def:filter" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_snmp_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The vmhost_snmp_state element defines the information that can be used to evaluate the specified ESXi host SNMP configuration information.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostStateBaseType">
<xsd:sequence>
<xsd:element name="enabled" type="oval-def:EntityStateBoolType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>true if SNMP is enabled for the ESXi host; false otherwise</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="port" type="oval-def:EntityStateIntType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The configured SNMP port</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="readonly_communities" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>TODO TODO BUGBUGBUG</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- VMHost Advanced Setting Test -->
<!-- =============================================================================== -->
<xsd:element name="vmhost_advancedsetting_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The vmhost_advancedsetting_test is used to collect advanced configuration information from an ESXi host.
This test extends the standard TestType as defined in the oval-definitions-schema and one should refer to the
TestType description for more information. The required object element references a vmhost_advancedconfig_object
and the optional state element specifies the metadata to check.
</xsd:documentation>
<xsd:documentation>
PowerCLI Equivalent:
Get-VMHost | Get-AdvancedSetting -Name "ADVANCED_SETTING_NAME" | Select @{N="VMHost";E={$_.Entity}}, Name, Value
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:TestType">
<xsd:sequence>
<xsd:element name="object" type="oval-def:ObjectRefType"/>
<xsd:element name="state" type="oval-def:StateRefType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_advancedsetting_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The vmhost_advancedsetting_object element is used by the vmhost_advancedconfig_test to define those objects to be evaluated based on a specified state.
</xsd:documentation>
<xsd:documentation>
The object may select a specific VMHost, which can be NULL, but must always include an advanced configuration item name to be collected. The method by
which the advanced configuration information is collected is as follows:
Get-VMHost | Get-AdvancedSetting -Name "THE_ADVANCED_SETTING_NAME" | Select @{N="VMHost";E={$_.Entity}}, Name, Value
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostObjectBaseType">
<xsd:sequence>
<xsd:element name="advanced_setting_name" type="oval-def:EntityObjectStringType" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The vmhost_advancedsetting_name element details the name of the VMHost's advanced configuration setting to collect.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="oval-def:filter" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_advancedsetting_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The vmhost_advancedsetting_state details the values which may be applied to a given advanced configuration item.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostStateBaseType">
<xsd:sequence>
<xsd:element name="advanced_setting_name" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The vmhost_advancedconfig_name element details the name of the VMHost's advanced configuration setting to collect.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="advanced_setting_value" type="oval-def:EntityStateAnySimpleType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The advanced_configuration_value element details the value of the VMHost's advanced configuration setting that was collected.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- VMHost Service Test -->
<!-- =============================================================================== -->
<xsd:element name="vmhost_service_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The vmhost_service_test is used to collect service-related configuration information from an ESXi host.
This test extends the standard TestType as defined in the oval-definitions-schema and one should refer to the
TestType description for more information. The required object element references a vmhost_service_object
and the optional state element specifies the metadata to check.
</xsd:documentation>
<xsd:documentation>
PowerCLI Equivalent:
Get-VMHost | Get-VMHostService | Where { $_.key -eq "SERVICE_NAME" } | Select VMHost, Key, Label, Policy, Running, Required
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:TestType">
<xsd:sequence>
<xsd:element name="object" type="oval-def:ObjectRefType"/>
<xsd:element name="state" type="oval-def:StateRefType" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_service_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The vmhost_service_object element is used by the vmhost_service_test to define the object to be evaluated.
Each object extends the standard ObjectType as defined in the oval-definitions-schema and one should refer to the ObjectType
description for more information. The common set element allows complex objects to be created using filters and set logic.
Again, please refer to the description of the set element in the oval-definitions-schema.
</xsd:documentation>
<xsd:documentation>
A vmhost_service_object consists of a connection string identifying the host connection information, a VMHost name that
identifies the ESXi host being probed for service information, and the name of the service being collected.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostObjectBaseType">
<xsd:sequence>
<xsd:element name="service_name" type="oval-def:EntityObjectStringType" minOccurs="1" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The vmhost_service_name element details the name of the VMHost's service setting to collect.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="oval-def:filter" minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:element name="vmhost_service_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The vmhost_service_state details the values which may be applied to a given ESXi host's service item.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="x-vmware-esxi55:VMHostStateBaseType">
<xsd:sequence>
<xsd:element name="service_name" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The vmhost_service_name element details the name of the VMHost's service setting to collect.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="service_label" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Descriptive information regarding the service</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="service_policy" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The activation policy for the host service.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="service_running" type="oval-def:EntityStateBoolType" minOccurs="0" maxOccurs="1">
<xsd:annotation>