Security controls is the collective term for security classifications and security groups, which in turn are made up of one or more security marks.
There is one predefined Classification security group, but you can add as many additional security groups as you need.
Files, records, folders, and categories can be classified using the Classify option to apply a security classification and security marks.
You can set up classification guides so that users can auto-classify content.
When an item is classified it can only be seen by those with the required security clearance, and the security classification level is shown on screen. Users without the necessary security clearance won't have access to it or even know that it's there. When a classified file is declared as a record it retains its classification level and security marks.
User security clearance is set for a user (or user group) by assigning security marks to them.
1. An Alfresco Administrator can create security controls. Go to Admin Tools > Security Controls > Configure > Security Marks.
2. An Alfresco Administrator assigns security clearance levels to a user. Go to Admin Tools > Security Controls > Configure > Assign.
3. You are given the file permissions needed to edit files [22]/records [23].
4. Select to classify a file, record, folder, or category.
5. Selects security classification and/or security marks.
6. The classified item is only seen by those with the required security clearance.
7. You can reclassify the item as required, following the Downgrade Schedule or Declassification Schedule where appropriate.
In both cases you can apply security marks to both records, folders, and categories in a Records Management site, and files and folders in a standard Alfresco site. These same marks are applied to users to set their security clearance levels.
Classification security group
There are three clearance levels that can be assigned to users [8]:
You can't classify a file higher than your own security level. So if your security clearance is Confidential, you can't classify a file as Top Secret.
Security clearance levels are enforced for files and records that have been classified. For example, if a record has been classified as Top Secret, then:
User 1 would see the following, whereas User 2 would only see the Unclassified file that has no classification label:
When you set security classification for a file or record you must record a reason for the classification. Downgrade and declassification schedule option give additional control over the classification lifecycle.
Custom security groups
You can create an unlimited number of security groups, which in turn can contain an unlimited number of security marks. The marks are then applied to files and records [10] and assigned to users [8].
When you create a new security group there are three Group Types available:
Example: A Security Group named Training contains security marks of Media and Data Handling. To see a file marked as both Media or Data Handling, then a user must have both Media and Data Handling clearance.
Example: A Security Group named Nationality contains security marks of UK, US, and Aus. To see a file marked as UK and US, then a user must have UK and / or US clearance.
Example: The predefined Classification group has marks of Top Secret, Secret, and Classified. To see a file classified as Secret, then the user must have Secret or Top Secret clearance.
Using the above examples, if a record has been classified as Media, Data Handling, US, and UK, then:
Once marks are applied to content then users can only see that content if they have the required security clearance.
When security groups are created there are three different Group Types available, and each one controls how the user sees content, see How security controls work [27].
Users with Alfresco Administrator permissions can set and edit the security clearance of users and user groups [8].
When assigning marks to users or user groups, marks that are inherited from another group aren't shown. Only marks that are assigned directly to this user / group are displayed. If a user (or group) has inherited security marks from a group, then these are added to their directly assigned marks.
Hierarchy based security clearance
For hierarchy based security groups such as the prefined Classification group, a user who is assigned one mark and inherits another has the clearance of the higher of the two. For example, a user who has Confidential clearance directly assigned, and has inherited Top Secret clearance from a group, will have Top Secret Clearance.
Non-hierarchy based security clearance
For non-hierarchy based security groups the security marks are added together, so that a user who is directly assigned the UK mark, and inherits the US mark from a group, will have clearance for both UK and US marked files.
Instead of setting these individually, you can create classification guides [9] to use as templates for classifying content quickly and accurately.
You can create as many classification guides as you want and make them as complex or as simple as you need.
Each guide is made up of one or more topics. A topic can contain further subtopics, or a set of instructions. If you select to add instructions you can choose security classification, including a classification agency and reasons and downgrade and declassification schedules, as well as any additional security marks that are set up.
You can choose to make a guide available for use in classification by setting it to On, or to leave it Off until you're ready for it to be used.
When people are classifying content [10] they can select to Add Instructions and browse through the classification guides to find the instructions they want. When the instructions are applied to content then all the security classifications and controls the instructions contain are automatically applied to that content.
Example
The following example shows a classification guide for Staff Records. This guide contains a topic named Medical Records which has has instructions to include the US and Senior Manager security marks.
If a file was classified using these instructions then it would only be visible to users who have security clearance for US and Senior Manager levels.
For example, the predefined security group is Classification and contains the marks Top Secret, Secret, and Confidential. Only users assigned to the Top Secret mark can see files that have been marked as Top Secret. This works in the same way for any additional security groups that you set up.
You can set up additional security groups to match your company requirements, for example, security groups for nationality and job role.
Example: A Security Group named Training contains security marks of Media and Data Handling. To see a file marked as both Media or Data Handling, then a user must have both Media and Data Handling clearance.
Example: A Security Group named Nationality contains security marks of UK, US, and Aus. To see a file classified as UK and US, then a user must have UK and / or US clearance.
Example: The predefined Classification group has marks of Top Secret, Secret, and Classified. To see a file classified as Secret, then the user must have Secret or Top Secret clearance.
Once you've created a security group you can:
Once marks are added to the group, only users who have been assigned one of the marks can see the group.
For example, the predefined security group is Classification and contains the marks Top Secret, Secret, and Confidential. Only users assigned to the Top Secret mark can see files that have been marked as Top Secret.
You can set up additional security groups to match your company requirements, for example, security groups for nationality and job role.
You can use the same names for marks in different security groups, but within a security group each name must be unique.
Users and groups are shown with their current classification clearance (the predefined security group).
Hover over Details to see all security groups and security marks assigned to a user.
Click to select to view Groups and Users, or just Users or Groups.
Instructions are a collection of security marks and classification details. When you classify content with a topic (or topics) it's classification details are populated with those in the topic.
You can build up guides and they won't be available for use until you set them to On. Find out more in How classification guides work [5].
If it's not yet ready then you can leave it Off and switch in On at a later stage.
The guide is now listed and you can now add topics to it.
You can now click Save and add sub-topics, or select instructions to add to a topic.
If the guide is switched On then users can select from the topics it contains to automatically classify content.
If you edit a guide's instructions then that won't modify the classification level or marks applied to content previously classified using that instruction.
See Classification rules and tips [30] for more on classifying content.
You can autoclassify by adding instructions, manually apply classifications and security marks, or both.
You can classify using both Security Classification and Security Groups. You'll only see the classification options that you have security clearance for.
To autoclassify:
All the topics you've selected will have their instructions applied to the item you're classifying.
To add Other Classification Source References
To manually add classifications and security marks:
This option is only visible when classifying a folder. Only the top level folder and its immediate children are classified and only the metadata of the parent is carried over to the children. If a new child object is added at a later date it does not inherit the properties of its parent.
Downgrade Schedule
Set a schedule for when the item will be downgraded, for example, from Top Secret to Secret. You can enter a specific date for the downgrade to take place, an event that means a downgrade should be considered, and instructions on how to carry out the downgrade. All of these are optional, but once you've entered a downgrade date, event, or both, you're required to enter instructions.
Declassification Schedule
Set a schedule for when the item will be declassified. This means when its classification level will be set to Unclassified. You can enter a specific date for the declassification to take place, an event that means declassification should be considered, and exemptions for when declassification shouldn't take place. All of these are optional.
See How security controls work [3] for more details.
The item now displays its classification level, and can only be seen by those with the required security clearance.
The classification reason and classification-related properties can be seen in the Properties when you preview the item.
Once configured Classification Reasons are used because they provide you with information relevant to your organization about why an item is being classified.
Use the other icons to Delete and Edit the other Classification Reasons.
Security clearance and permissions
If a user doesn't have the required security clearance, then they won't be able to see record, folders, or categories that have been classified. For example, if a record has been classified as Top Secret, then:
You also can't classify items higher than your own security level. So if your classification clearance is Confidential, you can't classify a record as Top Secret.
Classifying folders and categories
When you classify folders and categories, there may be restrictions on the levels you can set if they contain content that has already been classified. As such you might want to consider classifying folders and categories before you classify their content. The rules are:
Go to Admin Tools > Security Controls > Configure to review the following declassification settings.
Governance Services comes configured with some common Declassification Exemptions but you can edit, delete, and create your own. You use these when you want to record the reasoning why the declassification time frame isnt being followed. Typically this occurs when you want to extend the Declassification Time Frame for some of your items in the repository.
Declassification Exemptions are used when classifying content to indicate why the default Declassification Time Frame should not be applied.
Use the other icons to Delete and Edit the other Declassification Exemptions.
The Declassification Time Frame screen is where you set the declassification period your system will use when declassifying items in Governance Services.
The Calendar Icon displays the current Declassification Time Frame.
This process may take some time to complete.
You also can't reclassify a content higher than your own security level. So if your security clearance is Confidential, you can't reclassify content as Top Secret.
See Classification rules and tips [30] for more on classifying content.
See How security controls work [3] for more details.
The content now displays its classification level, and can only be seen by those with the required security clearance.
The classification reason and classification-related properties can be seen in its properties when you preview files and records or view the details of folders and categories.
Links:
[1] https://docs.alfresco.com/../concepts/security-control-video-tutorials.html
[2] https://docs.alfresco.com/../concepts/rm-classification-lifecycle.html
[3] https://docs.alfresco.com/../concepts/rm-sc-overview.html
[4] https://docs.alfresco.com/../concepts/rm-clearance-overview.html
[5] https://docs.alfresco.com/../concepts/rm-cg-overview.html
[6] https://docs.alfresco.com/../tasks/rm-create-security-group.html
[7] https://docs.alfresco.com/../tasks/rm-add-marks.html
[8] https://docs.alfresco.com/../tasks/rm-assign-sc.html
[9] https://docs.alfresco.com/../tasks/rm-create-guide.html
[10] https://docs.alfresco.com/../tasks/rm-classify-record.html
[11] https://docs.alfresco.com/../concepts/rm-declassification.html
[12] https://docs.alfresco.com/../tasks/rm-reclassify.html
[13] https://docs.alfresco.com/../concepts/welcome-gs.html
[14] https://docs.alfresco.com/../concepts/rm-tutorials-16.html
[15] https://docs.alfresco.com/../concepts/rm-tutorials-17.html
[16] https://docs.alfresco.com/../concepts/rm-tutorials-19.html
[17] https://docs.alfresco.com/../concepts/rm-tutorials-18.html
[18] https://docs.alfresco.com/../concepts/rm-tutorials-20.html
[19] https://docs.alfresco.com/../concepts/rm-tutorials-21.html
[20] https://docs.alfresco.com/../concepts/rm-tutorials-22.html
[21] https://docs.alfresco.com/../concepts/rm-security.html
[22] https://docs.alfresco.com/6.0/references/permissions_share.html
[23] https://docs.alfresco.com/../tasks/rm-usergroups-add.html
[24] http://docs.alfresco.com/6.0/references/permissions_share.html
[25] https://docs.alfresco.com/../tasks/rm-set-permissions.html
[26] http://docs.alfresco.com/5.1/references/permissions_share.html
[27] https://docs.alfresco.com/rm-sc-overview.html
[28] https://docs.alfresco.com/rm-add-marks.html
[29] https://docs.alfresco.com/rm-classify-file.html
[30] https://docs.alfresco.com/../references/rm-classification-tips.html
[31] https://docs.alfresco.com/../tasks/rm-classificationreasons.html
[32] http://docs.alfresco.com/5.2/references/permissions_share.html
[33] https://docs.alfresco.com/../tasks/rm-DeclassificationExemptions.html
[34] https://docs.alfresco.com/../tasks/rm-DeclassificationTimeFrame.html