The strategy you adopt for classifying secured items is dependent, in part, on the number of items of secured items that have to be protected. If you have a tiny number of parts that are restricted by ITAR, then putting them manually in the ITAR class is quite efficient and can be done by the security officer. As the number of categories or secured items grow, then help may be required. The first line of expansion is to permit more people than the security officers to classify items. For example, engineers who are US nationals may be given the authority and tools to classify ITAR items they are working on if they know (or believe) that they belong in ITAR. The officers have final say and only they have the privileges to remove items from a class. This strategy may result in initial over-classification, but has the benefit of being conservative and requires active confirmation by the security officers. Very large numbers of items to protect may require some forms of automation to place items under security classification. This may be the case during initial implementation when previously segregated data are loaded for the first time into the system. In such a case, the batch-loading mechanism would be adjusted to put the items directly in the proper classes. | |||||||||