About Custom Security Custom Security

Additional Security Settings 6-17

5. In the Security Classification field, delete the current security level using the

keyboard or by selecting the blank line from list.

6. Click OK.

6.3 Custom Security

Custom security is optional and are another layer of security in addition to supplemental markings see Supplemental Markings on page 6-2. Two types of custom security are available: ■ Simple custom security fields, where custom field are configured to be matched by a user rather than a designated supplemental marking. This is called custom supplemental markings in the DoD 5015 standard, ■ Advanced custom security, where security is applied to fields that use option lists. Security can be applied to individual items in the option list. Unlike supplemental markings, custom security is enforced at the item level. Supplemental markings are enforced at both the record folder and the item level. This section covers the following topics: ■ About Custom Security on page 6-17 ■ Managing Custom Security on page 6-18 ■ Simple Custom Security Field Example on page 6-21

6.3.1 About Custom Security

To work with custom security, you need to have one of the following rights: ■ Admin.Triggers : This right enables you to view information. ■ Admin.RecordManager : In addition to viewing information, this right also enables you to create add, edit, and delete custom security. A simple custom security field pairs a custom content field with a custom user field. For example, you can create a custom security field such as Project Name. Users must be assigned the appropriate project name or names to access or view an item assigned with custom security. If the match all setting is enabled, a user must be assigned to all the same projects as an item is assigned to for the user to access an item with multiple project assignments. If a user does not match all project names, the user cannot access an item. You can opt to select the match all feature for custom security fields just as you can with supplemental markings. Content is then checked in with one or more custom security field options, such as a particular project name, assigned to the content. For instance, user1 is assigned project name Pangea only. The user named user2 is assigned both project name Pangea and Tectonic. If content is checked in with multiple field options assigned for example, Pangea and Tectonic, then only a user with all project names assigned user2 can access that content. If the match all setting is disabled, then a user only must match one field option to access an item. Advanced custom security also limits access to content items. However, advanced security can also restrict access based on aliases as well as individual users. This type of security assigns security at the item level for option lists. When using this type of security, the only metadata that can be used is that which has an option list associated 6-18 Oracle Fusion Middleware Setup Guide for Universal Records Management with it. Access can then be restricted to individual items in the option list by limiting which accounts, which users, or which aliases of users can access specific options.

6.3.2 Managing Custom Security