Building the encodings for a site and making them correct can be a time-consuming process. A system cannot be configured until the correct label_encodings file is installed.
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 more information about setting up site security policy, see Appendix A, Site Security Policy for Trusted Extensions, in Trusted Extensions Configuration and Administration.
For an example of planning a customized label_encodings file that is based on company requirements, see Example of Planning an Organization's 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].
For suggestions and examples, see Customizing the LOCAL DEFINITIONS Section.
Changing the label_encodings file on a running system is risky. For more information, see the label_encodings(5) man page.