Allow time to build a correct label_encodings file.
Building the encodings for a site and making the encodings correct can be a time-consuming process. A system cannot be configured until the correct label_encodings file is installed.
Know your site's security policy.
Many sites already have a security policy that was developed according to government methods. Commercial businesses, even businesses that do not have much experience in planning labeled security, can start by examining their goals for information protection. These goals can be used to make some common-sense decisions about how to use labels. If the company has developed legal requirements for labeling printed information and email, those guidelines are a good place to start.
For an example, see Chapter 6, Example: Planning an Organization's Labels.
For more about setting up your site's security policy, see Appendix A, Site Security Policy, in Oracle Solaris Trusted Extensions Configuration Guide.
Study the U. S. government label encodings file.
The government's description of the file is in the Compartmented Mode Workstation Labeling: Encodings Format: Defense Intelligence Agency document [DDS-2600-6216-93].
Customize the LOCAL DEFINITIONS section for your site.
For suggestions and examples, see Chapter 5, Customizing LOCAL DEFINITIONS.
Finalize your encodings before installing Trusted Extensions.
Changing the label_encodings file on a running system is risky. For more information, see the label_encodings(4) man page.