Skip Navigation Links | |
Exit Print View | |
![]() |
Trusted Extensions Label Administration Oracle Solaris 10 8/11 Information Library |
1. Labels in Trusted Extensions Software
3. Making a Label Encodings File (Tasks)
4. Labeling Printer Output (Tasks)
5. Customizing LOCAL DEFINITIONS
6. Example: Planning an Organization's Labels
The sample file has the following four classifications:
PUBLIC
INTERNAL_USE_ONLY
NEED_TO_KNOW
REGISTERED
In this model, PUBLIC is the sensitivity label for communications across the Internet. INTERNAL_USE_ONLY is the sensitivity label for communications within the company.
The sample file defines compartments to appear only in labels that have the NEED_TO_KNOW classification. The sample file also specifies that the default word Comps is changed to the word Departments in label-builder GUIs.
NEED_TO_KNOW compartments are:
ALL_DEPARTMENTS
The ALL_DEPARTMENTS compartment word gets turned on when all defined compartment bits are on and works as a toggle in a label builder.
EXECUTIVE_MGT_GROUP
SALES
FINANCE
LEGAL
MARKETING
HUMAN_RESOURCES
ENGINEERING
MANUFACTURING
SYSTEM_ADMINISTRATION
PROJECT_TEAM
PROJECT_TEAM is hierarchically below both ENGINEERING and MARKETING. The hierarchy enables a user who is working at NEED_TO_KNOW ENGINEERING or at NEED_TO_KNOW MARKETING to read files with the NEED_TO_KNOW PROJECT_TEAM label. The user cannot write to files that have that label.