{% extends base_template %} {% block html_param %}ng-app="app"{% endblock %} {% block title_page %}AL - Classification Documentation {% endblock %} {% block js_import %} {% endblock %} {% block content %}

Classification Help

{{app_name}} Classification Engine Documentation

Submission based classification

When you submit one or many files to {{ app_name }}, you are required to provide the classification of the files you are submitting. This classification is for the submission itself and will be applied to all files in the submission. If the files that you want to submit have a different classification, you should submit them one by one and apply the proper classification to each submission.

If you realize that you've submitted a file with the wrong classification, you can always use the delete button in the submission detail page to get rid of the submission.

One file, multiple submissions

If two submission contain the same file but those submissions have different classifications, the system will assign to lowest classification of the two submissions to the file.

Example:

{% raw %}

Lets assume the following:

File1's classification will be {{ classification_definition.UNRESTRICTED | class_long }}. Submission1and Submission2 will remain to their original classification.

If one of the submission is deleted, let's says Submission2. The system will re-calculate the classification of all the files related to the deleted submission. File1's classification will now be {{ classification_definition.RESTRICTED | class_long }}. Submission1 will remain to its original classification.

{% endraw %}

Service results have classification too!

The various {{ app_name }} services will output their results at different classification levels depending on the technique/tool used to provide the result. To prevent the search engine from displaying results of classified files to unclassified users, the system will apply the maximum classification between the file classification and the service result classification to the results.

Example:

{% raw %}

Lets assume the following:

ServiceX results for File1 are going to be classified {{ classification_definition.RESTRICTED | class_long }} because the file is classified higher then the service results. In the eyes of an {{ classification_definition.UNRESTRICTED | class_long }} user, they will not exist.

ServiceY results for File2 will remain classified {{ classification_definition.RESTRICTED | class_long }} since the classification of the results is higher than the classification of the file itself.

{% endraw %}

How is the classification validated?

Classification

Classification is validated by using greater than or equal. The user's classification has to be greater than or equal to submission/file/result he or she is trying to view/search.

{% raw %}

Currently Supported classifications:

Required tokens

To view a piece of information protected with required tokens, the user must have all the tokens that the submission/file/result the user is trying to view has.

Currently Supported Required Tokens:

Groups Releaseability

To view a piece of information protected with a group releaseability, the user must have at least one of the groups that the submission/file/result the user is trying to view has.

Currently Supported Groups:

** NOTE: not providing a group makes it available to all.

Sub-Groups Releaseability

To view a piece of information protected with a sub-groups releaseability, the user must have at least one of the sub-groups that the submission/file/result the user is trying to view has.

Currently Supported Sub-Groups:

** NOTE: not providing a subgroup makes it available to all.

{% endraw %}

I don't understand, now what?

If any clarification is needed about the Security Classification engine of {{ app_name }}, don't hesitate to contact any of {{ app_name }}'s system admins.

{% endblock%} {% block loading_jumbo %}ng-show="!classification_definition"{% endblock %}