Lines Matching full:levelrange
4 Because there are many options for MLS labeling, the examples show a limited selection of statements, however there is a simple policy that will build shown in the [`levelrange`](cil_mls_labeling_statements.md#levelrange) section.
304 - Category expressions are allowed in [`categoryset`](cil_mls_labeling_statements.md#categoryset), [`sensitivitycategory`](cil_mls_labeling_statements.md#sensitivitycategory), [`level`](cil_mls_labeling_statements.md#level), and [`levelrange`](cil_mls_labeling_statements.md#levelrange) statements.
464 levelrange
471 (levelrange levelrange_id (low_level_id high_level_id))
482 <td align="left"><p><code>levelrange</code></p></td>
483 <td align="left"><p>The <code>levelrange</code> keyword.</p></td>
487 <td align="left"><p>The <code>levelrange</code> identifier.</p></td>
502 This example policy shows [`levelrange`](cil_mls_labeling_statements.md#levelrange) statement and all the other MLS labeling statements discussed in this section and will compile as a standalone policy:
555 (levelrange levelrange_2 (level_2 level_2))
556 (levelrange levelrange_1 ((s0) level_2))
557 (levelrange low_low (systemLow systemLow))
620 <td align="left"><p>The new MLS range for the object class that is a previously declared <code>levelrange</code> identifier. This entry may also be defined as an anonymous or named <code>level</code>, <code>sensitivity</code>, <code>sensitivityalias</code>, <code>category</code>, <code>categoryalias</code> or <code>categoryset</code> identifier.</p></td>
636 (levelrange low_high (systemlow systemhigh))
