Skip Navigation Links | |
Exit Print View | |
Trusted Extensions Label Administration Oracle Solaris 11.1 Information Library |
1. Labels in Trusted Extensions (Overview)
2. Planning Labels in Trusted Extensions (Tasks)
3. Creating a Label Encodings File (Tasks)
4. Labeling Printer Output (Tasks)
Security Text on Banner and Trailer Pages
Specifying the "Protect As" Classification
Configuring Security Text on Print Jobs (Task Map)
How to Specify the Text in PRINTER BANNERS
5. Customizing the LOCAL DEFINITIONS Section (Tasks)
6. Planning an Organization's Encodings File (Example)
The following task map describes how to format body pages and banner pages with labels.
|
In this procedure, you create the strings that appear at the top of the banner page and at the start of the handling instructions on the bottom of the page.
Before You Begin
You must be in the Security Administrator role in the global zone. You have planned the banners.
For background information, see Specifying Printer Banners.
For assistance, use Planning the Printer Banners in a Worksheet.
# pfedit encodings-file
These strings are associated with the text in the printer banner lines of banner and trailer pages.
PRINTER BANNERS: WORDS: name= ORCON; prefix;
You can associate compartments with particular prefixes and suffixes. Prefixes precede the compartment text and suffixes follow the compartment text on the printed output
name= (FULL SB NAME); compartments= 3; name= (FULL SA NAME); compartments= 2;
Next Steps
Continue with How to Analyze and Verify the label_encodings File.
In this procedure, you create the strings that state handling instructions on printer banner pages.
Before You Begin
You must be in the Security Administrator role in the global zone. You have planned the prefixes and suffixes.
For assistance, use Planning the Channels in a Worksheet.
# pfedit encodings-file
The WORDS in the CHANNELS lines of banner and trailer pages become prefixes or suffixes. For example:
CHANNELS: WORDS: name= CHANNELS JOINTLY; suffix; name= CHANNELS ONLY; suffix; name= HANDLE VIA; prefix;
Use your defined prefixes and suffixes.
name= (CH C); prefix= HANDLE VIA; suffix= CHANNELS JOINTLY; compartments= 6; name= (CH B); prefix= HANDLE VIA; suffix= CHANNELS JOINTLY; compartments= 1; name= (CH A); prefix= HANDLE VIA; suffix= CHANNELS JOINTLY; compartments= 0;
Next Steps
Continue with How to Analyze and Verify the label_encodings File.
The minimum “Protect As” classification protects all printer output at the specified minimum classification or above. Site security policy might require this setting if lower-level information must be protected at a higher label.
Before You Begin
You must be in the Security Administrator role in the global zone.
# pfedit encodings-file
This entry is defined in the ACCREDITATION RANGE section of the label_encodings file.
Example 4-3 Minimum “Protect As” Classification From a label_encodings File
This example shows a minimum “Protect As” classification. This classification is defined in the ACCREDITATION RANGE section of the default label_encodings file. With this setting, files that are labeled INTERNAL print with NEED_TO_KNOW on the banner and trailer pages.
minimum protect as classification= NEED_TO_KNOW;
Next Steps
Continue with How to Analyze and Verify the label_encodings File.