> For the complete documentation index, see [llms.txt](https://docs.guardware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardware.com/documentation/protect/encryption-and-policies/classification-protection-settings.md).

# Classification Protection Settings

{% hint style="info" %}
To use MIP integration with GuardWare, your organisation must have a Microsoft licence that includes Microsoft Purview Information Protection (sensitivity labelling) capabilities, such as Microsoft 365 Business Premium, Microsoft 365 E3, Microsoft 365 E5, or Azure Information Protection P1/P2.
{% endhint %}

For Microsoft Office files, PROTECT works with Microsoft Purview Information Protection (MIP) to apply protection based on the file's classification.

The **Classification Protection Settings** page lets you configure how Microsoft Office files are protected for each classification label. Based on the file classification selected by users while adding or changing file protection, the protection mode is applied, determining whether the file is protected using only MIP or both MIP and GuardWare PROTECT. You can select a protection method for Office files, and PROTECT automatically applies the appropriate protection setting to non-Office files.

## Configure Protection by Classification

1. Navigate to **PROTECT > Classification Settings**.
2. For each file classification, select one of the following options according to your requirements and click **Submit**. The available options are:

* **Do Not Encrypt**: Files with this classification are not protected.
* **MIP Encryption**: Files are protected using Microsoft Purview Information Protection (MIP).
* **PROTECT Encryption**: Files are protected using GuardWare PROTECT.
* **MIP & PROTECT Encryption**: Files are protected using both MIP and GuardWare PROTECT.

<figure><img src="https://2233655803-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6thNYq9Il6WA2mTbj6X%2Fuploads%2FyW5txYYIfnB6zLv0Ke7u%2Fimage.png?alt=media&amp;token=621507bf-c2ac-414d-a75b-80629fa961e6" alt=""><figcaption></figcaption></figure>

For example, the following protection settings are configured:

<table><thead><tr><th width="201.5999755859375">Classification</th><th width="260.4000244140625">Office Files</th><th>Non-Office Files</th></tr></thead><tbody><tr><td>Public</td><td>MIP Encryption</td><td>PROTECT Encryption</td></tr><tr><td>Confidential</td><td>MIP &#x26; PROTECT Encryption</td><td>PROTECT Encryption</td></tr></tbody></table>

When a user adds or changes file protection from the Windows Explorer right-click menu:

* Selecting **Public** applies MIP Encryption to Office files and PROTECT Encryption to non-Office files.
* Selecting **Confidential** applies both MIP Encryption and PROTECT Encryption to Office files, and PROTECT Encryption to non-Office files.

## How MIP Works

For the MIP Encryption protection setting, Microsoft Office files are protected with Microsoft Purview Information Protection (MIP). MIP secures Office files by applying classification labels and enforcing encryption and access controls at the file level. When a file is classified (for example, Confidential or Highly Sensitive), MIP:

* Encrypts the file using Azure-based protection.
* Assigns permissions to specific users or groups.
* Verifies the user’s identity when the file is opened.
* Enforces usage rights such as view, edit, copy, or print.

This protection travels with the file, ensuring that only authorised users can access it, even if it is shared outside the organisation.

## How MIP and GuardWare PROTECT Work Together

For the MIP & PROTECT Encryption protection setting, GuardWare PROTECT and MIP work together to apply protection based on the sensitivity of the file. MIP first applies its classification-based encryption and permission controls, after which GuardWare PROTECT adds an additional layer of encryption and access control. GuardWare PROTECT:

* Controls whether a file can be accessed at all.
* Enforces access based on Security Groups.
* Prevents unauthorised tools or environments from opening the file.
* Allows access to be revoked at any time.

| Protection Mode              | Office Documents                                               | Non-Office Files                  | Key Benefits                                                                                                                                                                                                    | Typical Use Cases                                                                                                                            |
| ---------------------------- | -------------------------------------------------------------- | --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **MIP Encryption**           | Protected using Microsoft Purview Information Protection (MIP) | Protected using GuardWare PROTECT | Delivers a native Microsoft Office experience while leveraging existing Purview labels, policies, and workflows. Simplifies adoption for organisations already invested in the Microsoft security ecosystem.    | Organisations using Microsoft Purview, Microsoft 365-centric environments, and compliance-focused deployments.                               |
| **MIP & PROTECT Encryption** | Protected using both MIP and GuardWare PROTECT                 | Protected using GuardWare PROTECT | Combines Microsoft classification and compliance capabilities with GuardWare’s persistent protection model. Helps organisations maintain consistent protection across a wider range of collaboration scenarios. | Security-conscious organisations, regulated industries, critical infrastructure, engineering and intellectual property-focused environments. |

## Selecting a Protection Mode

The appropriate protection mode depends on your organisation's security strategy and existing technology investments.

* **Choose MIP Encryption** if you already use Microsoft Purview sensitivity labels and want Microsoft Office documents to remain protected through Microsoft's native protection framework while using GuardWare PROTECT for other file types.
* **Choose MIP & PROTECT Encryption** if you want to combine Microsoft classification and compliance capabilities with GuardWare protection for Office documents, providing additional control over sensitive information throughout its lifecycle.

## Select a Default Classification Label

Select a **Default Classification Label**. PROTECT applies this classification when a file is created or saved from an authorised application and no enabled data type determines another classification.

If the default classification includes encryption, PROTECT applies the selected protection to the file. Files protected by the default classification are available to the **All Users** Security Group, which includes all users registered with PROTECT.

<figure><img src="https://2233655803-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6thNYq9Il6WA2mTbj6X%2Fuploads%2FrNflmR2xrphbO7MtxL4b%2Fimage.png?alt=media&amp;token=3d4669f8-0cf2-4ad2-b7ba-17becb542562" alt=""><figcaption></figcaption></figure>

## Protect Office Files using MIP

Use the **Protect Office files using MIP** toggle to control whether Office files can use MIP protection.

When enabled, Office files can be protected using MIP, while non-Office files are protected with GuardWare PROTECT. When disabled, all file types are protected using GuardWare PROTECT.

<figure><img src="https://2233655803-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6thNYq9Il6WA2mTbj6X%2Fuploads%2F8j7hRAK1Bgguvfgm5eV1%2Fimage.png?alt=media&amp;token=fcc9fbea-138c-4c77-ad13-c8a0ef10a52a" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.guardware.com/documentation/protect/encryption-and-policies/classification-protection-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.