Trusted Solaris Label Administration

Analyzing the Requirements for Each Label

The Security Administrator agrees that the set of labels mandated by the legal department is a good start but realizes that the labels need to be analyzed further before they can be encoded.

PROPRIETARY/CONFIDENTIAL: INTERNAL_USE_ONLY

The PROPRIETARY/CONFIDENTIAL: INTERNAL_USE_ONLY label is for information that is proprietary to the company but which, because of its low level of sensitivity, may be distributed to all employees, all of whom have signed nondisclosure agreements before starting employment. Information with this label may also be distributed to others such as the employees of vendors and contractors, as long as each person who receives the information has also signed a nondisclosure agreement. Because the Internet may be snooped, information with this label may not be sent over the Internet, but it may be sent via email within the company.

Memos containing spending guidelines 

Internal job postings 

PROPRIETARY/CONFIDENTIAL: NEED_TO_KNOW

The PROPRIETARY/CONFIDENTIAL: NEED_TO_KNOW label is intended for information that is proprietary to the company, has a higher level of sensitivity than INTERNAL_USE_ONLY, and has a more limited audience. Distribution is limited to employees who have a need to know the information and to others who have signed nondisclosure agreements who also have a need to know.

For example, if only the group of people working in a particular project should see certain information, then NEED_TO_KNOW should be used on that information. People who receive information with this label can copy it and pass it on to other people who also have a need to know and have signed a nondisclosure agreement. Whenever information should be restricted to a particular group, the name of the group should be specified on the printed or otherwise-copied version of the information.

Having the name of a group in this label makes it clear that the information should not be given to anyone outside of the group. Information with this label may not be sent over the Internet but it may be sent via email within the company.

Product design documents 

Project details 

Employee Status Change Form 

PROPRIETARY/CONFIDENTIAL: REGISTERED

The PROPRIETARY/CONFIDENTIAL: REGISTERED classification is intended for information that is proprietary to the company, has a very high level of sensitivity, and could significantly harm the company if released to the wrong parties or if it was released at the wrong time. Registered information must be numbered and tracked by the owner. Each copy must be assigned to a specific person and returned to the owner for destruction after being read. Copies may be made only by the owner of the information. Use of brownish-red paper is recommended because this color cannot be copied.

This label is to be used when only one specific group of people should be allowed to see the proprietary information. This information cannot be shown to anyone who is not authorized by the owner, and it cannot be shown to employees of other companies who have not signed a nondisclosure agreement--even if the owner authorizes them to see it. Information with this label may not be sent via email.

End of quarter financial information not yet released 

Sales forecasts 

Marketing forecasts 

Names of Group Associated with the Need to Know

The Security Administrator decided that the NEED_TO_KNOW label should contain the names of groups or departments. The Security Administrator asked for suggestions about what words to use to define groups or areas of interest within the organization, and came up with the following list.

Engineering 

Executive Management 

Finance 

Human Resources 

Legal 

Manufacturing 

Marketing 

Sales 

System Administration 

Understanding the Set of Labels

The next step is to decide:

The Security Administrator used a large board and pieces of paper marked with the words that should be in the labels, as shown in Figure 5-7, to visualize the relationships and rearrange the pieces until they all fit together.

The administrator came up with the following:

Figure 5-7 Example Planning Board for Label Relationships

Graphic