-
Notifications
You must be signed in to change notification settings - Fork 28
/
aix-def-schema.xsd
1726 lines (1720 loc) · 117 KB
/
aix-def-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-def="http://oval.mitre.org/XMLSchema/oval-definitions-5"
xmlns:oval="http://oval.mitre.org/XMLSchema/oval-common-5"
xmlns:aix-def="http://oval.mitre.org/XMLSchema/oval-definitions-5#aix"
xmlns:sch="http://purl.oclc.org/dsdl/schematron"
targetNamespace="http://oval.mitre.org/XMLSchema/oval-definitions-5#aix"
elementFormDefault="qualified" version="5.11">
<xsd:import namespace="http://oval.mitre.org/XMLSchema/oval-definitions-5"/>
<xsd:import namespace="http://oval.mitre.org/XMLSchema/oval-common-5"/>
<!-- =============================================================================== -->
<!-- ========================= DEVICE ATTRIBUTE TEST ============================= -->
<!-- =============================================================================== -->
<xsd:element name="deviceattribute_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The deviceattribute_test is used to hold information related to the execution of the
/usr/sbin/lsattr -EOl [device] -a [attribute] command. 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 lssec_object and the optional
state element specifies the value to check.
</xsd:documentation>
<xsd:appinfo>
<sch:pattern id="aix-def_deviceattributetst">
<sch:rule context="aix-def:deviceattribute_test/aix-def:object">
<sch:assert test="@object_ref=ancestor::oval-def:oval_definitions/oval-def:objects/aix-def:deviceattribute_object/@id"><sch:value-of select="../@id"/> - the object child element of a <sch:name path=".."/> must reference a deviceattribute_object</sch:assert>
</sch:rule>
<sch:rule context="aix-def:deviceattribute_test/aix-def:state">
<sch:assert test="@state_ref=ancestor::oval-def:oval_definitions/oval-def:states/aix-def:deviceattribute_state/@id"><sch:value-of select="../@id"/> - the state child element of a <sch:name path=".."/> must reference a deviceattribute_state</sch:assert>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</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="deviceattribute_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The deviceattribute_object element is used by a deviceattribute_test to determine the collection of
information related to the execution of the /usr/sbin/lsattr -EOl [device] -a [attribute] command.
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:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:ObjectType">
<xsd:sequence>
<xsd:choice>
<xsd:element ref="oval-def:set"/>
<xsd:sequence>
<xsd:element name="device_name" type="oval-def:EntityObjectStringType">
<xsd:annotation>
<xsd:documentation>Specifies the device logical name in the Customized Devices object class whose attribute names or values you want displayed</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="attribute_name" type="oval-def:EntityObjectStringType">
<xsd:annotation>
<xsd:documentation>The name of the attribute of a specific device or type of device.</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:element>
<xsd:element name="deviceattribute_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The deviceattribute_state element defines the different information associated with a specific call
to /usr/sbin/lsattr -EOl [device] -a [attribute]. Please refer to the individual elements in the schema
for more details about what each represents.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:StateType">
<xsd:sequence>
<xsd:element name="device_name" type="oval-def:EntityStateStringType">
<xsd:annotation>
<xsd:documentation>Specifies the device logical name in the Customized Devices object class whose attribute names or values you want displayed</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="attribute_name" type="oval-def:EntityStateStringType">
<xsd:annotation>
<xsd:documentation>The name of the attribute of a specific device or type of device.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="value" type="oval-def:EntityStateAnySimpleType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The value entity defines the value to check against the device attribute being examined.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- ============================ INITTAB TEST ==================================== -->
<!-- =============================================================================== -->
<xsd:element name="inittab_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The inittab_item is used to hold information related to the /usr/sbin/lsitab command and information stored in /etc/inittab.
Currently, /usr/sbin/lsitab is used to configure records in the /etc/inittab file which controls the initialization process.
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 lssec_object and the optional state element specifies the value
to check.
</xsd:documentation>
<xsd:appinfo>
<sch:pattern id="aix-def_inittabtst">
<sch:rule context="aix-def:inittab_test/aix-def:object">
<sch:assert test="@object_ref=ancestor::oval-def:oval_definitions/oval-def:objects/aix-def:inittab_object/@id"><sch:value-of select="../@id"/> - the object child element of a <sch:name path=".."/> must reference a inittab_object</sch:assert>
</sch:rule>
<sch:rule context="aix-def:inittab_test/aix-def:state">
<sch:assert test="@state_ref=ancestor::oval-def:oval_definitions/oval-def:states/aix-def:inittab_state/@id"><sch:value-of select="../@id"/> - the state child element of a <sch:name path=".."/> must reference a inittab_state</sch:assert>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</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="inittab_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The inittab_object element is used by an inittab_test to determine the collection of entries in the /etc/inittab file.
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:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:ObjectType">
<xsd:sequence>
<xsd:choice>
<xsd:element ref="oval-def:set"/>
<xsd:sequence>
<xsd:element name="identifier" type="oval-def:EntityObjectStringType">
<xsd:annotation>
<xsd:documentation>A string (one or more than one character) that uniquely identifies an object</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:element>
<xsd:element name="inittab_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The inittab_state element defines the different information associated with a specific call to /usr/bin/lsitab.
Please refer to the individual elements in the schema for more details about what each represents.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:StateType">
<xsd:sequence>
<xsd:element name="identifier" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>A string (one or more than one character) that uniquely identifies an object</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="runlevel" type="aix-def:EntityStateInittabRunlevelType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>
The run level in which this entry can be processed. Run levels effectively correspond to a
configuration of processes in the system. Run levels are represented by the numbers 0 through 9.
There are three other values that appear in the runlevel field, even though they are not true
run levels: a, b, and c. Entries that have these characters in the runlevel field are processed
only when the telinit command requests them to be run (regardless of the current run level of the system).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="action" type="aix-def:EntityStateInittabActionType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>Tells the init command how to treat the process specified in the identifier field.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="command" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>A shell command to execute.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- =========================== SECURITY STANZA TEST ============================= -->
<!-- =============================================================================== -->
<xsd:element name="securitystanza_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The securitystanza_test is used to check information related to the /usr/bin/lssec command and the parameters it manages.
The lssec command lists attributes stored in the security configuration stanza files. The following security configuration
files contain attributes that you can specify with the Attribute parameter. The information being tested is based off the
/usr/bin/lssec [ -f File ] [ -s Stanza ] [ -a Attribute ] command. 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 lssec_object and the optional state element specifies the value to check.
</xsd:documentation>
<xsd:appinfo>
<sch:pattern id="aix-def_securitystanzatst">
<sch:rule context="aix-def:securitystanza_test/aix-def:object">
<sch:assert test="@object_ref=ancestor::oval-def:oval_definitions/oval-def:objects/aix-def:securitystanza_object/@id"><sch:value-of select="../@id"/> - the object child element of a <sch:name path=".."/> must reference a securitystanza_object</sch:assert>
</sch:rule>
<sch:rule context="aix-def:securitystanza_test/aix-def:state">
<sch:assert test="@state_ref=ancestor::oval-def:oval_definitions/oval-def:states/aix-def:securitystanza_state/@id"><sch:value-of select="../@id"/> - the state child element of a <sch:name path=".."/> must reference a securitystanza_state</sch:assert>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</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="securitystanza_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The securitystanza_object element is used by a securitystanza_test to determine the
collection of attributes in the security stanza files. 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:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:ObjectType">
<xsd:sequence>
<xsd:choice>
<xsd:element ref="oval-def:set"/>
<xsd:sequence>
<xsd:element name="stanza_file" type="aix-def:EntityObjectStanzaFileType">
<xsd:annotation>
<xsd:documentation>The stanza_file entity is an enumeration of values representing the security configuration file containing the desired attributes.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="stanza_name" type="oval-def:EntityObjectStringType">
<xsd:annotation>
<xsd:documentation>Specifies the name of the stanza to list.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="attribute_name" type="oval-def:EntityObjectStringType">
<xsd:annotation>
<xsd:documentation>Specifies the attribute to list.</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:element>
<xsd:element name="securitystanza_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The securitystanza_state element defines the different information associated with a specific
call to /usr/bin/lssec. Please refer to the individual elements in the schema for more details
about what each represents.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:StateType">
<xsd:sequence>
<xsd:element name="stanza_file" type="aix-def:EntityStateStanzaFileType">
<xsd:annotation>
<xsd:documentation>The stanza_file entity is an enumeration of values representing the security configuration file containing the desired attributes.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="stanza_name" type="oval-def:EntityStateStringType">
<xsd:annotation>
<xsd:documentation>Specifies the name of the stanza to list.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="attribute_name" type="oval-def:EntityStateStringType">
<xsd:annotation>
<xsd:documentation>Specifies the attribute to list.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="value" type="oval-def:EntityStateAnySimpleType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The value entity defines the value to check against the security parameter being examined.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- =========================== USER ACCOUNT TEST =============================== -->
<!-- =============================================================================== -->
<xsd:element name="useraccount_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The useraccount_test is used to assess information related to the /usr/sbin/lsuser command and the attributes it manages.
Currently, /usr/sbin/lsuser is used to display user account attributes. The /usr/sbin/lsuser command queries the named
attribute for the provided user account(s). 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 lssec_object and the optional state element specifies the value to check.
</xsd:documentation>
<xsd:appinfo>
<sch:pattern id="aix-def_useraccounttst">
<sch:rule context="aix-def:useraccount_test/aix-def:object">
<sch:assert test="@object_ref=ancestor::oval-def:oval_definitions/oval-def:objects/aix-def:useraccount_object/@id"><sch:value-of select="../@id"/> - the object child element of a <sch:name path=".."/> must reference a useraccount_object</sch:assert>
</sch:rule>
<sch:rule context="aix-def:useraccount_test/aix-def:state">
<sch:assert test="@state_ref=ancestor::oval-def:oval_definitions/oval-def:states/aix-def:useraccount_state/@id"><sch:value-of select="../@id"/> - the state child element of a <sch:name path=".."/> must reference a useraccount_state</sch:assert>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</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="useraccount_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The useraccount_object is used to collect information related to the /usr/sbin/lsuser command and
the user account attributes it manages. 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:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:ObjectType">
<xsd:sequence>
<xsd:choice>
<xsd:element ref="oval-def:set"/>
<xsd:sequence>
<xsd:element name="username" type="oval-def:EntityObjectStringType">
<xsd:annotation>
<xsd:documentation>The name of the user to be queried by the /usr/sbin/lsuser command.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="account_attribute" type="aix-def:EntityObjectUserAccountAttributeType">
<xsd:annotation>
<xsd:documentation>The name of the user attribute to be queried by the /usr/sbin/lsuser command. This value can include any attribute that is defined by the /usr/bin/chuser command.</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:element>
<xsd:element name="useraccount_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>
The useraccount_state element defines the different information associated with a specific call to /usr/sbin/lsuser.
Please refer to the individual elements in the schema for more details about what each represents.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:StateType">
<xsd:sequence>
<xsd:element name="username" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the user to be queried by the /usr/sbin/lsuser command.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="account_attribute" type="aix-def:EntityStateUserAccountAttributeType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The name of the user attribute to be queried by the /usr/sbin/lsuser command. This value can include any attribute that is defined by the /usr/bin/chuser command.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="value" type="oval-def:EntityStateAnySimpleType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The value entity defines the value assigned to the user attribute being examined.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<!-- =============================================================================== -->
<!-- ================================= NFSO TEST ================================= -->
<!-- =============================================================================== -->
<xsd:element name="nfso_test" substitutionGroup="oval-def:test">
<xsd:annotation>
<xsd:documentation>
The nfso test is used to check information related to the /usr/sbin/nfso command and the parameters it manages.
The nfso command sets or displays current or next boot values for network file system (NFS) tuning parameters.
The information being tested is based off the /usr/sbin/nfso -o command. 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 no_object and the optional state element specifies the value to check for.
</xsd:documentation>
<xsd:appinfo>
<sch:pattern id="aix-def_nfsotst">
<sch:rule context="aix-def:nfso_test/aix-def:object">
<sch:assert test="@object_ref=ancestor::oval-def:oval_definitions/oval-def:objects/aix-def:nfso_object/@id"><sch:value-of select="../@id"/> - the object child element of a <sch:name path=".."/> must reference a nfso_object</sch:assert>
</sch:rule>
<sch:rule context="aix-def:nfso_test/aix-def:state">
<sch:assert test="@state_ref=ancestor::oval-def:oval_definitions/oval-def:states/aix-def:nfso_state/@id"><sch:value-of select="../@id"/> - the state child element of a <sch:name path=".."/> must reference a nfso_state</sch:assert>
</sch:rule>
</sch:pattern>
</xsd:appinfo>
</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="nfso_object" substitutionGroup="oval-def:object">
<xsd:annotation>
<xsd:documentation>
The nfso_object element is used by a nfso_test to define the specific parameter 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 nfso_object consists of a single tunable entity that identifies the parameter to be looked at.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:ObjectType">
<xsd:sequence>
<xsd:choice>
<xsd:element ref="oval-def:set"/>
<xsd:sequence>
<xsd:element name="tunable" type="oval-def:EntityObjectStringType">
<xsd:annotation>
<xsd:documentation>The tunable entity holds the name of the tunable parameter to be queried by the /usr/sbin/nfso command. Examples include nfs_max_read_size and nfs_max_write_size.</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:element>
<xsd:element name="nfso_state" substitutionGroup="oval-def:state">
<xsd:annotation>
<xsd:documentation>The nfso_state element defines the different information associated with a specific call to /usr/sbin/nfso. Please refer to the individual elements in the schema for more details about what each represents.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:complexContent>
<xsd:extension base="oval-def:StateType">
<xsd:sequence>
<xsd:element name="tunable" type="oval-def:EntityStateStringType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The tunable entity is used to check the name of the tunable parameter that was used by the /usr/sbin/nfso command. Examples include nfs_max_read_size and nfs_max_write_size.</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="value" type="oval-def:EntityStateAnySimpleType" minOccurs="0" maxOccurs="1">
<xsd:annotation>
<xsd:documentation>The value entity defines the value to check against the tunable parameter being examined.</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
</xsd:element>
<xsd:complexType name="EntityObjectStanzaFileType">
<xsd:annotation>
<xsd:documentation>The lssec command lists attributes stored in the security configuration stanza files. The following security configuration files contain attributes that you can specify with the Attribute parameter.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="oval-def:EntityObjectStringType">
<xsd:enumeration value="ENVIRON">
<xsd:annotation>
<xsd:documentation>/etc/security/environ</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GROUP">
<xsd:annotation>
<xsd:documentation>/etc/security/group</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="HOSTS">
<xsd:annotation>
<xsd:documentation>/etc/security/audit/hosts</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LASTLOG">
<xsd:annotation>
<xsd:documentation>/etc/security/lastlog</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LIMITS">
<xsd:annotation>
<xsd:documentation>/etc/security/limits</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LOGIN">
<xsd:annotation>
<xsd:documentation>/etc/security/login.cfg</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MKUSER">
<xsd:annotation>
<xsd:documentation>/usr/lib/security/mkuser.default</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NSCONTROL">
<xsd:annotation>
<xsd:documentation>/etc/nscontrol.conf</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PASSWD">
<xsd:annotation>
<xsd:documentation>/etc/security/passwd</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PORTLOG">
<xsd:annotation>
<xsd:documentation>/etc/security/portlog</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PWDALG">
<xsd:annotation>
<xsd:documentation>/etc/security/pwdalg.cfg</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ROLES">
<xsd:annotation>
<xsd:documentation>/etc/security/roles</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SMITACL_USER">
<xsd:annotation>
<xsd:documentation>/etc/security/smitacl.user</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SMITACL_GROUP">
<xsd:annotation>
<xsd:documentation>/etc/security/smitacl.group</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="USER">
<xsd:annotation>
<xsd:documentation>/etc/security/user</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="USER_ROLES">
<xsd:annotation>
<xsd:documentation>/etc/security/user.roles</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="RTCD_POLICY">
<xsd:annotation>
<xsd:documentation>/etc/security/rtc/rtcd_policy.conf</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="">
<xsd:annotation>
<xsd:documentation>The empty string value is permitted here to allow for empty elements associated with variable references.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EntityStateStanzaFileType">
<xsd:annotation>
<xsd:documentation>The lssec command lists attributes stored in the security configuration stanza files. The following security configuration files contain attributes that you can specify with the Attribute parameter.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="oval-def:EntityStateStringType">
<xsd:enumeration value="ENVIRON">
<xsd:annotation>
<xsd:documentation>/etc/security/environ</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GROUP">
<xsd:annotation>
<xsd:documentation>/etc/security/group</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="HOSTS">
<xsd:annotation>
<xsd:documentation>/etc/security/audit/hosts</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LASTLOG">
<xsd:annotation>
<xsd:documentation>/etc/security/lastlog</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LIMITS">
<xsd:annotation>
<xsd:documentation>/etc/security/limits</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LOGIN">
<xsd:annotation>
<xsd:documentation>/etc/security/login.cfg</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MKUSER">
<xsd:annotation>
<xsd:documentation>/usr/lib/security/mkuser.default</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NSCONTROL">
<xsd:annotation>
<xsd:documentation>/etc/nscontrol.conf</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PASSWD">
<xsd:annotation>
<xsd:documentation>/etc/security/passwd</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PORTLOG">
<xsd:annotation>
<xsd:documentation>/etc/security/portlog</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PWDALG">
<xsd:annotation>
<xsd:documentation>/etc/security/pwdalg.cfg</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ROLES">
<xsd:annotation>
<xsd:documentation>/etc/security/roles</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SMITACL_USER">
<xsd:annotation>
<xsd:documentation>/etc/security/smitacl.user</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="SMITACL_GROUP">
<xsd:annotation>
<xsd:documentation>/etc/security/smitacl.group</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="USER">
<xsd:annotation>
<xsd:documentation>/etc/security/user</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="USER_ROLES">
<xsd:annotation>
<xsd:documentation>/etc/security/user.roles</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="RTCD_POLICY">
<xsd:annotation>
<xsd:documentation>/etc/security/rtc/rtcd_policy.conf</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="">
<xsd:annotation>
<xsd:documentation>The empty string value is permitted here to allow for empty elements associated with variable references.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
</xsd:restriction>
</xsd:simpleContent>
</xsd:complexType>
<xsd:complexType name="EntityObjectUserAccountAttributeType">
<xsd:annotation>
<xsd:documentation>The name of the user attribute to be queried by the /usr/sbin/lsuser command. This value can include any attribute that is defined by the /usr/bin/chuser command.</xsd:documentation>
</xsd:annotation>
<xsd:simpleContent>
<xsd:restriction base="oval-def:EntityObjectStringType">
<xsd:enumeration value="ACCOUNT_LOCKED">
<xsd:annotation>
<xsd:documentation>Indicates if the user account is locked</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ADMIN">
<xsd:annotation>
<xsd:documentation>Defines the administrative status of the user.</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ADMGROUPS">
<xsd:annotation>
<xsd:documentation>Defines the groups that the user administrates</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="AUDITCLASSES">
<xsd:annotation>
<xsd:documentation>Defines the user's audit classes</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="AUTH1">
<xsd:annotation>
<xsd:documentation>Defines the primary methods for authenticating the user</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="AUTH2">
<xsd:annotation>
<xsd:documentation>Defines the secondary methods for authenticating the user</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CAPABILITIES">
<xsd:annotation>
<xsd:documentation>Defines the system privileges (capabilities) which are granted to a user by the login or su commands</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CORE">
<xsd:annotation>
<xsd:documentation>Specifies the soft limit for the largest core file a user's process can create</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CORE_COMPRESS">
<xsd:annotation>
<xsd:documentation>Enables or disables core file compression</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CORE_HARD">
<xsd:annotation>
<xsd:documentation>Specifies the largest core file a user's process can create</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CORE_NAMING">
<xsd:annotation>
<xsd:documentation>Selects a choice of core file naming strategies. Valid values for this attribute are On and Off</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CORE_PATH">
<xsd:annotation>
<xsd:documentation>Enables or disables core file path specification</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CORE_PATHNAME">
<xsd:annotation>
<xsd:documentation>Specifies a location to be used to place core files, if the core_path attribute is set to On</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CPU">
<xsd:annotation>
<xsd:documentation>Identifies the soft limit for the largest amount of system unit time (in seconds) that a user's process can use</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="CPU_HARD">
<xsd:annotation>
<xsd:documentation>Identifies the largest amount of system unit time (in seconds) that a user's process can use</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="DAEMON">
<xsd:annotation>
<xsd:documentation>Indicates whether the user specified by the Name parameter can run programs using the cron daemon or the src (system resource controller) daemon</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="DATA">
<xsd:annotation>
<xsd:documentation>Specifies the soft limit for the largest data segment for a user's process</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="DATA_HARD">
<xsd:annotation>
<xsd:documentation>Specifies the largest data segment for a user's process</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="DCE_EXPORT">
<xsd:annotation>
<xsd:documentation>Allows the DCE registry to overwrite the local user information with the DCE user information during a DCE export operation</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="DEFAULT_ROLES">
<xsd:annotation>
<xsd:documentation>Specifies the default roles for the user</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="DICTIONLIST">
<xsd:annotation>
<xsd:documentation>Defines the password dictionaries used by the composition restrictions when checking new passwords</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="DOMAINS">
<xsd:annotation>
<xsd:documentation>Defines the list of domains that the user belongs to</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="EXPIRES">
<xsd:annotation>
<xsd:documentation>Identifies the expiration date of the account</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="FSIZE">
<xsd:annotation>
<xsd:documentation>Defines the soft limit for the largest file a user's process can create or extend</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="FSIZE_HARD">
<xsd:annotation>
<xsd:documentation>Defines the largest file a user's process can create or extend</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GECOS">
<xsd:annotation>
<xsd:documentation>Supplies general information about the user specified by the Name parameter</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="GROUPS">
<xsd:annotation>
<xsd:documentation>Identifies the groups to which user belongs</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="HISTEXPIRE">
<xsd:annotation>
<xsd:documentation>Defines the period of time (in weeks) that a user cannot reuse a password</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="HISTSIZE">
<xsd:annotation>
<xsd:documentation>Defines the number of previous passwords that a user cannot reuse</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="HOME">
<xsd:annotation>
<xsd:documentation>Identifies the home directory of the user specified by the Name parameter</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ID">
<xsd:annotation>
<xsd:documentation>Specifies the user ID</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LOGIN">
<xsd:annotation>
<xsd:documentation>Indicates whether the user can log in to the system with the login command</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LOGINRETRIES">
<xsd:annotation>
<xsd:documentation>Defines the number of unsuccessful login attempts allowed after the last successful login before the system locks the account</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="LOGINTIMES">
<xsd:annotation>
<xsd:documentation>Defines the days and times that the user is allowed to access the system</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MAXAGE">
<xsd:annotation>
<xsd:documentation>Defines the maximum age (in weeks) of a password</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MAXEXPIRED">
<xsd:annotation>
<xsd:documentation>Defines the maximum time (in weeks) beyond the maxage value that a user can change an expired password</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MAXREPEATS">
<xsd:annotation>
<xsd:documentation>Defines the maximum number of times a character can be repeated in a new password</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MAXULOGS">
<xsd:annotation>
<xsd:documentation>Specifies the maximum number of concurrent logins per user</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MINAGE">
<xsd:annotation>
<xsd:documentation>Defines the minimum age (in weeks) a password must be before it can be changed</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MINALPHA">
<xsd:annotation>
<xsd:documentation>Defines the minimum number of alphabetic characters that must be in a new password</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MINDIFF">
<xsd:annotation>
<xsd:documentation>Defines the minimum number of characters required in a new password that were not in the old password</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MINLEN">
<xsd:annotation>
<xsd:documentation>Defines the minimum length of a password</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="MINOTHER">
<xsd:annotation>
<xsd:documentation>Defines the minimum number of non-alphabetic characters that must be in a new password</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NOFILES">
<xsd:annotation>
<xsd:documentation>Defines the soft limit for the number of file descriptors a user process may have open at one time</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NOFILES_HARD">
<xsd:annotation>
<xsd:documentation>Defines the hard limit for the number of file descriptors a user process may have open at one time</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NPROC">
<xsd:annotation>
<xsd:documentation>Defines the soft limit on the number of processes a user can have running at one time</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="NPROC_HARD">
<xsd:annotation>
<xsd:documentation>Defines the hard limit on the number of processes a user can have running at one time</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PGRP">
<xsd:annotation>
<xsd:documentation>Identifies the primary group of the user</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PROJECTS">
<xsd:annotation>
<xsd:documentation>Defines the list of projects to which the user's processes can be assigned</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PWDCHECKS">
<xsd:annotation>
<xsd:documentation>Defines the password restriction methods enforced on new passwords</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="PWDWARNTIME">
<xsd:annotation>
<xsd:documentation>Defines the number of days before the system issues a warning that a password change is required</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="RCMDS">
<xsd:annotation>
<xsd:documentation>Controls the remote execution of the r-commands (rsh, rexec, and rcp)</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="RLOGIN">
<xsd:annotation>
<xsd:documentation>Permits access to the account from a remote location with the telnet orrlogin commands</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="ROLES">
<xsd:annotation>
<xsd:documentation>Defines the administrative roles for this user</xsd:documentation>
</xsd:annotation>
</xsd:enumeration>
<xsd:enumeration value="RSS">
<xsd:annotation>
<xsd:documentation>The soft limit for the largest amount of physical memory a user's process can allocate</xsd:documentation>
</xsd:annotation>