What is a Sandbox?
A sandbox is an isolated compliance checking environment that defines what violations to detect and how to handle them. Each sandbox has:- Type: What to check for (PII, bias, security, etc.)
- Rules: Custom compliance rules
- Regulations: Which regulations apply (GDPR, CCPA, etc.)
- Alert Threshold: Minimum risk level to alert on
- Guardian Action: How to handle pre-LLM detections
Sandbox Types
Continum supports 15 specialized sandbox types:PII_DETECTION
Detects personally identifiable information:- Names, emails, phone numbers
- SSN, passport numbers, driver’s licenses
- Credit cards, bank accounts
- Health data, biometric identifiers
- IP addresses, location data
BIAS_DETECTION
Detects discriminatory content:- Racial, gender, religious bias
- Age, disability discrimination
- Sycophantic bias
- Intersectional bias
SECURITY_AUDIT
Detects security vulnerabilities:- SQL injection, XSS, CSRF
- Secret leaks (API keys, passwords)
- Dangerous instructions
- Infrastructure exposure
PROMPT_INJECTION
Detects prompt manipulation:- Direct injection attacks
- Jailbreak attempts (DAN, STAN)
- System prompt extraction
- Goal hijacking
AGENT_SAFETY
Detects unsafe agent behavior:- Infinite loops, resource exhaustion
- Irreversible actions without confirmation
- Scope creep, privilege escalation
- Deceptive alignment
HALLUCINATION_DETECTION
Detects false information:- Fake citations, fabricated papers
- Invented statistics
- False confidence
- Expert impersonation
CONTENT_POLICY
Detects harmful content:- Violence, sexual content
- CSAM (zero tolerance)
- Hate speech, harassment
- Self-harm facilitation
FINANCIAL_COMPLIANCE
Detects financial regulation violations:- Unlicensed financial advice
- Insider trading facilitation
- Market manipulation
- Fraud enablement
LEGAL_COMPLIANCE
Detects legal liability issues:- Unauthorized legal advice
- Copyright infringement
- Defamation risk
- Privacy law breaches
FULL_SPECTRUM
Comprehensive checking across all categories. Use case: Production applications requiring maximum protectionCUSTOM
Define your own rules and detection logic. Use case: Industry-specific complianceCreating a Sandbox
Via Dashboard
- Navigate to Sandboxes in the dashboard
- Click “Create Sandbox”
- Choose a type
- Set a slug (e.g.,
my-sandbox) - Configure options
- Save
Via API
Sandbox Configuration
name
Human-readable name for the sandbox:slug
Unique identifier used in API calls:sandboxType
The type of compliance checking:PII_DETECTION, BIAS_DETECTION, SECURITY_AUDIT, PROMPT_INJECTION, AGENT_SAFETY, HALLUCINATION_DETECTION, CONTENT_POLICY, FINANCIAL_COMPLIANCE, LEGAL_COMPLIANCE, FULL_SPECTRUM, CUSTOM
regulations
Which regulations to check against:alertThreshold
Minimum risk level to alert on:LOW, MEDIUM, HIGH, CRITICAL
guardianAction
How Guardian handles pre-LLM detections:ALLOW_ALL: Log but don’t redactREDACT_AND_CONTINUE: Redact and continueBLOCK_ON_DETECT: Block LLM call
customRules
Additional rules specific to your use case:region
Geographic region for compliance:GLOBAL, US, EU, UK, APAC
active
Enable or disable the sandbox:Using Sandboxes
With SDK
With API
Plan Limits
Sandbox limits vary by plan:| Plan | Sandboxes | Audits/Month |
|---|---|---|
| DEV | 1 | 1,000 |
| PRO | 10 | Unlimited |
| PRO_MAX | 25 | Unlimited |
| ENTERPRISE | Unlimited | Unlimited |
Best Practices
Naming Convention
Use descriptive slugs:Multiple Sandboxes
Create sandboxes for different use cases:Testing
Test sandboxes before production:- Create a test sandbox
- Run sample audits
- Review signals in dashboard
- Adjust configuration
- Deploy to production
Monitoring
Monitor sandbox performance:- Signal volume per sandbox
- Risk level distribution
- False positive rate
- Processing time
Next Steps
Signal
Understand audit results
Guardian
Configure pre-LLM protection
API Reference
Sandbox API documentation
Dashboard
Manage sandboxes

