Policies Overview

Javelin provides robust, centralized policy management to ensure security, compliance, and operational consistency across your applications. Policies are defined globally and selected for applications, enabling fine-grained and reusable governance throughout your environment.

Why Use Policies?

• Centralized enforcement: Define policies once and apply them across your organization, or tailor them to individual applications as needed.
• Consistent security: Protect against prompt injection, enhance trust and safety, enforce language and content controls, guard against phishing, manage agent or code execution, and oversee file handling—all through unified, automated policy application.
• Operational efficiency: Update or adjust policies in a central location with comprehensive auditing for all assignments and modifications, streamlining management and compliance.

How Policies Work

1. Policy Creation: Configure the specific rules and constraints to enforce (e.g., safety checks, content filters).
2. Policy Selection: Select the defined policy for any application.
3. Policy Enforcement: Each incoming request is governed by the selected policy. If none is explicitly selected, a structured precedence process determines which default applies.

Policy Types

Javelin defines three types of policies:

• System Default Policy

  • This is a single policy set as the default for the entire deployment.
  • It is automatically applies to all applications.

• Group Default Policy (Coming soon)

  • A single policy can be set as the default for each group.
  • If configured, it automatically applies to all applications within that group—taking precedence over the system default policy.

• Regular Policy (Explicit Policy)

  • Any policy not set as a group or system default.
  • It only applies when explicitly selected for a specific application, and always takes higher precedence over group and system default.

Assignment & Precedence

When configuring an application, you select from the available global policies. Policy enforcement operates according to clear, hierarchical precedence—ensuring every request is consistently governed by the appropriate policy.

  Incoming Request
         |
         ▼
┌──────────────────┐
│   Application    │
└──────────────────┘
         |
         ▼
┌──────────────────┐   No    ┌─────────────────┐   No    ┌─────────────────┐   No
│     Policy       │ ──────► │ Group default   │ ──────► │ System default  │ ─────► No policy
│    selected?     │         │ policy present? │         │ policy present? │        applied
└──────────────────┘         └─────────────────┘         └─────────────────┘
        | Yes                         | Yes                       | Yes
        |                             |                           |
        └─────────────────────────────┴───────────────────────────┘
                                      |
                                      ▼ 
                           Selected policy applied

1. Selected Policy: If a specific policy is selected, it is applies.
2. Group Default Policy (Coming soon): If no explicit policy is selected, the group default (if configured) applies.
3. System Default Policy: If neither specific nor group default policy applies, the system default (if configured) applies.
4. No Policy: If no applicable policy is found, the request proceeds without policy enforcement.

By relying on transparent precedence and unified management, Javelin enables you to enforce governance at scale—delivering reliable, predictable, and efficient policy compliance across all applications.