Protect company data

Navigate to the Policies section and select "Extension" Click To "ADD NEW POLICY" for protect company data.

It can define various parameters including policy name, description, match criteria etc.. by clicking on "Add New Policy".

• Add Policy Name

• Description

• Policy Severity

• What type of policy do you want to create (I want to protect company data)

Match Criteria:

• Select User( select All)

• Or specific users or groups.

• select Site URL (All sites as well as choose specific sites )

• select User & Policy actions(Alert, Block, Mask, Warn , Allow)

• Click on Next.

• Data Protections (select profile)

Notification want as per organization Need(it is optional):

• Want to Receive Notification on which Channel.

• Select Frequency(Immediate, Every Hour, Evert Day)

• Click to Create Policy.

After Policy Creation Enable the status.

Once this step is complete, visit ChatGPT. Make sure the extension is installed and you are logged in using your organization domain email ID. Ensure that ChatGPT is accessible. After creating the policy, reload ChatGPT or any other relevant sites once.

In the profile, I selected the custom rule test for regex and keyword only test'. Within this rule, we’ve used a custom identifier for regex only and another custom identifier for keyword only. When we tested on ChatGPT using a value that matches the regex-only identifier, it was successfully detected.

Now tested with the keyword-only value as well, since the rule includes both identifiers. It is also working.

So this is how it works.

After detection, the user can go to the Alert page to view the Alert.

Note:

1. After creating a Custom Identifier, you must create a Custom Rule.

2. Once the rule is created, you need to create a Profile and assign the rule to it.

3. Finally, create a Policy and assign the profile to it — this is the last step for making the configuration active.

⚠️ Important Note on Deletion Flow

Make sure not to directly delete any Identifier, Rule, or Profile that is currently being used. Since all components are linked to each other, follow this proper order to avoid breaking the setup:

1. First, delete or remove the Profile from the Policy.

2. Then delete the Profile.

3. Next, delete the Rule.

4. Finally, delete the Identifier.

Deleting anything out of order may lead to broken configurations or unexpected behavior.

After detection occurs, the user can go to the Alert page to view the triggered alert. Here is the guide Alert.