Skip to main content

Configuring Policies

Learn how to configure policies to match your organization's security requirements.

Accessing Policy Configuration​

  1. Navigate to Policies in the sidebar
  2. Browse policies by category or search
  3. Click a policy to configure it

Policy Settings​

Basic Settings​

Enable/Disable​

Toggle the policy on or off:

  • Enabled - Policy actively monitors and enforces
  • Disabled - Policy doesn't run

Policy Name​

  • Pre-built policies have fixed names
  • Custom policies can be named descriptively

Description​

  • Document what the policy does
  • Note any organization-specific context

Trigger Behavior​

Configure what happens when the policy matches:

BehaviorUser ExperienceAlert Created
BlockAction prevented, warning shownYes
WarnWarning shown, user can proceedYes
LogNo user notificationYes
tip

Start with Warn for new policies to observe patterns before enforcing blocks.

Sensitivity​

Adjust how aggressively the policy matches:

LevelDescriptionFalse Positive Rate
LowOnly high-confidence matchesLower
MediumBalanced detectionModerate
HighCatch more potential matchesHigher

Detection Configuration​

Pattern Settings​

For pattern-based policies:

Pattern: \b\d{3}-\d{2}-\d{4}\b
Options: Case insensitive
Context: Surrounding 50 characters

Keyword Lists​

For keyword-based policies:

  1. Click Edit Keywords
  2. Add words/phrases (one per line)
  3. Configure matching:
    • Exact match - Word boundaries
    • Contains - Anywhere in text
    • Regex - Pattern matching
  4. Save changes

Allowlist​

Exclude legitimate matches:

  1. Click Manage Allowlist
  2. Add patterns to allow:
    • Specific values (e.g., test SSN 123-45-6789)
    • Patterns (e.g., test-*)
    • Users (e.g., security-team@company.com)
  3. Add justification for audit trail
  4. Save

Scope Configuration​

Platform Scope​

Choose where the policy applies:

  • All AI Platforms - Universal enforcement
  • Specific Platforms:
    • ChatGPT
    • Claude
    • Google Gemini
    • Microsoft Copilot
    • Custom platforms

User Scope​

Define who the policy affects:

ScopeDescription
All UsersEveryone in organization
Specific TeamsSelected teams only
Specific UsersIndividual users
Exclude UsersEveryone except listed

Site Overrides​

Override policy behavior on specific sites:

Creating Custom Policies​

Professional

New Policy Wizard​

  1. Click Create Policy

  2. Select a template:

    • Keyword Match - Match specific words
    • Pattern Match - Regex-based detection
    • Data Type - Structured data formats
    • Blank - Build from scratch

  3. Configure the policy:

Step 1: Basic Info​

  • Name your policy
  • Select category
  • Add description

Step 2: Detection Rules​

  • Define what to match
  • Set sensitivity
  • Configure context window

Step 3: Behavior​

  • Choose trigger action
  • Set notification preferences
  • Configure escalation

Step 4: Scope​

  • Select platforms
  • Choose users/teams
  • Set exceptions

Example: Custom Policy​

Scenario: Block sharing of project codename "Phoenix"

Name: Project Phoenix Protection
Category: Intellectual Property
Detection:
  Type: Keyword
  Terms: ["Project Phoenix", "Phoenix initiative", "Operation Phoenix"]
  Match: Case insensitive
Behavior:
  Action: Block
  Message: "This content may contain confidential project information."
Scope:
  Platforms: All
  Users: All except security-team

Policy Testing​

Test Mode​

Test policies without affecting users:

  1. Enable Test Mode on the policy
  2. Policy runs but doesn't enforce
  3. View would-be alerts in dashboard
  4. Tune as needed
  5. Disable test mode to enforce

Test Content​

Use the policy tester:

  1. Click Test Policy
  2. Enter sample content
  3. See if policy would trigger
  4. View match details

Policy History​

Track changes to policies:

  1. Open policy settings
  2. Click History tab
  3. See all changes with:
    • Who made the change
    • What was changed
    • When it changed
  4. Compare versions
  5. Revert if needed

Bulk Operations​

Import/Export​

Export policies for backup or transfer:

  1. Select policies (or all)
  2. Click Export > JSON
  3. Download configuration file

Import policies:

  1. Click Import
  2. Upload JSON file
  3. Review changes
  4. Confirm import

Bulk Enable/Disable​

  1. Select multiple policies
  2. Click Bulk Actions
  3. Choose Enable or Disable
  4. Confirm action

Best Practices​

Policy Naming​

  • Use clear, descriptive names
  • Include what's detected
  • Note the category

Documentation​

  • Document why each policy exists
  • Note business requirements
  • Track who requested it

Testing​

  • Always test before enabling Block mode
  • Use representative test data
  • Check for false positives

Review Cycle​

  • Review policies monthly
  • Adjust based on alert volume
  • Archive unused policies