Skip to main content
A security profile is a packaged set of guardrail configurations that Protector Plus applies when evaluating prompts and responses. Each GenAI application is bound to a security profile — multiple applications can share a profile, or each can have its own.
Security profiles dashboard

The Security Profiles management view. Each profile carries a guardrail mix and binds to one or more applications.

​
Create a profile

1

Navigate to Security Profiles

Dashboard → Security Profiles → Create Security Profile.
2

Choose Forwarding mode or Non-forwarding mode

See sections below for mode details.
3

Configure profile settings

Fill in the profile name, LLM backend settings, and deployment mode settings (see tables below).
4

Save

The security profile is created and ready to be bound to applications.

​
Forwarding mode

The GenAI application points its LLM endpoint at the Protector Plus FQDN. Protector Plus applies the security profile bound to the FQDN before forwarding to the origin LLM.
Assign one FQDN per GenAI application — this is how Protector Plus distinguishes which security profile to apply.

​
Non-forwarding mode

The application calls Protector Plus directly using an org-wide API key and App ID. No FQDN is required. The application makes the final allow/deny decision based on the risk score returned by Protector Plus.

​
Setting up authentication for Non-forwarding mode

1

Generate the org-wide API key

Navigate to Org Settings → Click Generate to create your organization-wide API key. Store it securely — it is shown only once.
2

Register your application

Navigate to Apps → Register App.Fill in:
  • App Name: Human-readable name (e.g., “Customer Support Bot”)
  • App ID: Unique identifier (e.g., support-bot)
  • Security Profile: Select the security profile you created
Save and note your App ID.
3

Use both credentials in API calls

Include both X-API-Key (org-wide key) and X-App-ID (your app’s ID) in all API requests. See Authentication for details.
Multiple applications can share the same security profile. Simply register additional apps and bind them to the same profile.

​
Per-application isolation in practice

The diagram below shows two GenAI applications bound to two separate security profiles on the same Protector Plus instance. Each application is routed via a unique FQDN; Protector Plus applies the bound profile before forwarding to the corresponding LLM endpoint.
Per-application profiles

Per-application security profiles in Forwarding mode.

Use per-application isolation to:

Tighten regulated apps

Apply stricter PII rules to customer-facing applications handling SG NRIC/FIN.

Per-domain thresholds

Tune prompt-injection thresholds higher for apps wired to sensitive tools.

Sandbox isolation

Run research apps with minimal guardrails in Monitor mode without blocking.

Multi-tenant control

Assign different profiles per tenant in shared-platform deployments.

​
Managing profiles

​
Viewing profile details

Navigate to Security Profiles in the dashboard sidebar to view all profiles. Click on a profile to view and configure its guardrail settings.

​
Editing a profile

  1. Navigate to Security Profiles
  2. Click on the profile you want to edit
  3. Modify guardrail settings, thresholds, or backend configurations
  4. Click Save to apply changes

​
Viewing apps using a profile

On the Security Profile detail page, you can see which applications are currently bound to that profile.

​
Removing a profile

  1. Navigate to Security Profiles
  2. Click on the profile you want to remove
  3. Click Delete
  4. Confirm deletion
You cannot delete a profile that has active applications bound to it. Unbind all apps first, then delete the profile.

​
Profile administration is Super-Admin only

Security profile creation and deletion is restricted to Super Admin users. App-bound users cannot modify security profiles — see Account Management for the full access matrix.