Configuration¶
Important: Where to Configure What¶
| What to Configure | Where |
|---|---|
| Detection rules (prompt injection, DLP, URL filtering, etc.) | Strata Cloud Manager |
| Actions (allow/alert/block per detection) | Strata Cloud Manager |
| DLP patterns (SSN, credit cards, API keys) | Strata Cloud Manager |
| URL categories (malware, phishing, adult) | Strata Cloud Manager |
| Custom topics (organization policies) | Strata Cloud Manager |
| API key | Plugin config |
| Profile name | Plugin config |
| Plugin behavior (enable/disable hooks) | Plugin config |
All Guardrails Are in SCM
This plugin does NOT configure AI guardrails. All detection services, sensitivity levels, and actions are configured in your Strata Cloud Manager tenant. The plugin simply points to your SCM security profile and applies local enforcement.
Required: Plugin Configuration¶
plugins:
prisma-airs:
enabled: true
config:
# API key from Strata Cloud Manager (required)
api_key: "your-api-key-here"
# Which SCM profile to use
profile_name: "default"
# Application name for scan metadata/reporting
app_name: "openclaw"
The API key can also be set via the gateway web UI under plugin settings (marked as sensitive/hidden).
Hook Toggles¶
Enable/disable individual hooks:
plugins:
prisma-airs:
config:
reminder_enabled: true # prisma-airs-guard
audit_enabled: true # prisma-airs-audit
context_injection_enabled: true # prisma-airs-context
outbound_scanning_enabled: true # prisma-airs-outbound
tool_gating_enabled: true # prisma-airs-tools
Local Enforcement Settings¶
These control how the plugin responds locally, NOT what AIRS detects:
plugins:
prisma-airs:
config:
# Block messages when AIRS API is unreachable
fail_closed: true
# Mask DLP violations instead of blocking
dlp_mask_only: true
# Tools to block when ANY threat is detected
high_risk_tools:
- exec
- Bash
- bash
- write
- Write
- edit
- Edit
- gateway
- message
- cron
Strata Cloud Manager Setup¶
All detection configuration happens in SCM:
1. Get API Key¶
- Log into Strata Cloud Manager
- Navigate to Settings → API Keys
- Create a new key with AIRS permissions
- Copy the key to the plugin's
api_keyconfig field
2. Create Security Profile¶
- Navigate to AI Runtime Security → Security Profiles
- Create or edit a profile
- Enable detection services:
- Prompt Injection Detection
- Sensitive Data Protection (DLP)
- URL Filtering
- Toxic Content Detection
- Database Security
- Malicious Code Detection
- AI Agent Protection
- Contextual Grounding
- Custom Topic Guardrails
3. Configure Actions¶
For each detection service, set the action:
| Action | Behavior |
|---|---|
allow |
Log only, no blocking |
alert |
Log warning, allow through |
block |
Block the request |
4. Configure DLP Patterns¶
- Navigate to Data Loss Prevention
- Configure detection patterns for PII, credentials, etc.
Minimal Configuration¶
The absolute minimum to get started:
That's it. All other settings have sensible defaults.