Configuration

Configuring Safeguards

Administrators can customize iGuard settings:

• Enable/Disable Validations: Control which checks are active.
• Set Thresholds: Adjust sensitivity levels.
• On Fail Actions: Define system responses (block or warn).

Administrators can customize iGuard settings in real-time through declarative configuration files, without the need to restart the system. This allows for immediate adaptation to new policies or threats, ensuring continuous protection and compliance.

Declarative Configuration for iGuard

Configurations for iGuard are defined in a YAML file, allowing for clear and human-readable settings. Changes to this configuration are applied in real-time, enabling administrators to adjust validations on-the-fly.

Here's an example of how the configuration can be set:

validations:
  - name: DetectSecrets
    enabled: True
    models:
      - OpenAI
      - Gemini
    on_fail: block

  - name: DetectPII
    enabled: True
    models:
      - OpenAI
      - Gemini
    on_fail: block
    mode: permissive

  - name: Sentiment
    enabled: True
    models:
      - OpenAI
      - Gemini
    on_fail: block
    threshold: 0.5

  - name: DetectUnusualPrompt
    enabled: True
    models:
      - OpenAI
      - Gemini
    on_fail: block

- name: DetectSafeUnsafePrompt
    enabled: True
    models:
      - OpenAI
      - Gemini
    on_fail: block

Response Actions

The on_fail Parameter

Determines how the system responds when a validation fails:

• Block: Stops the request and notifies the user.
• Warn: Allows the request but issues a warning.

Block Mode

• Immediately stops the message
• Displays error message
• Logs the incident

Warn Mode

• Shows warning message to the user.
• Logs the warning