Skip to main content
Each guardrail is enabled per profile and may operate in block or monitor mode (in-line deployments). Block drops the connection on violation; Monitor passes the prompt through but records the detection on the Alerts page. Worked examples below follow the patterns formalised in CloudsineAI’s internal UAT Test Plans.

​
Standard Protection

​
Keyword Blocklist

Inspects both inputs and outputs for words that may be sensitive or violate company policies.
1

Open the guardrail configuration

Standard Protection → Keyword → Configuration.
2

Add a keyword rule

Click Add New Keyword and supply:
  • Phase: Input or Output
  • Title: short label (e.g., bomb-block)
  • Description: free text
  • Keywords: the literal strings to match
3

Verify with a test prompt

Send a prompt containing the keyword to /input-check (or /output-check for an output rule) and confirm the alert fires on the Alerts page.
Apply the same keyword to LLM responses by creating a separate rule with Phase = Output. Input and output rules are independent.

​
Regex Pattern Matching

Inspects inputs and outputs for text matching a regular expression. Example: detect confidentiality markers.
Configure as:
  • Phase: Input (or Output)
  • Name: Sensitive doc pattern
  • Description: any
  • Regular Expression: pattern above
Test prompts that should fire: Please share the confidential roadmap, top secret playbook, internal use only memo.

​
PII Detection

Enabling the PII guardrail activates detection for all supported categories by default. Individual categories can be toggled. Supported categories: Singapore NRIC/FIN, Phone Number, Person, Email Address, Credit Card, Passport Number, and similar identifiers. Worked SG-context test patterns (from UAT Test Plans §2.3):
  • Credit card: 4716-3018-9386-3240
  • SG NRIC/FIN: S9334193G
For minimum false-positive operation, start with only the categories that matter for your domain (e.g., SG NRIC/FIN + Phone + Email + Credit Card for a Singapore consumer app).

​
ShieldPrompt™

​
LLM Guardrail (CyberLLM)

Enable: ShieldPrompt → LLM Guardrail → ON. The threshold is configurable per security profile; defaults are tuned for production. Increasing the threshold reduces false positives at the cost of recall. Test prompts:

​
Vector Guardrail (TVDB)

Enable: ShieldPrompt → Vector Guardrail → ON. Sensitivity: Low / Medium / High.
  • Medium — recommended default.
  • High — recommended when stacking with the LLM guardrail and accepting higher false-positive rates for stronger coverage of paraphrased attacks.
The Vector guardrail catches semantically similar variants of known attacks:

​
Content Moderation

Enable: ShieldPrompt → Content Moderation → ON. Inspects outputs only; returns a category label when content is flagged unsafe (VIOLENCE, UNETHICAL, HATE, etc.).

​
System Prompt Protection

Enable: ShieldPrompt → System Prompt Protection → ON. No additional configuration required — Protector Plus detects system-prompt leakage in LLM responses.

​
Block vs Monitor

Both modes write the detection record to the Alerts page and to any configured SIEM destination. A recommended starting configuration is to enable: LLM, Vector, Content Moderation, and System Prompt Protection guardrails. Run for 1–2 weeks in Monitor mode while tuning thresholds. Switch to Block for guardrails whose false-positive rate is acceptable for the domain.