AI Security Detectors

Oculum is purpose-built for AI-native security. While traditional security scanners focus on OWASP-style vulnerabilities, Oculum specializes in detecting security issues unique to LLM-powered applications.

Why AI Security Matters

AI applications introduce new attack surfaces that traditional tools miss:

  • Prompt Injection — Malicious input that manipulates LLM behavior
  • Unsafe Execution — AI-generated code executed without validation
  • Data Exfiltration — Sensitive data leaked through AI responses
  • Agent Takeover — Autonomous agents performing unintended actions
  • Supply Chain — Compromised models or packages

Oculum's detectors are designed specifically for these AI-era threats.


Detection Categories

AI-Specific Detectors

CategoryWhat It DetectsSeverity
Prompt InjectionUnvalidated user input in LLM promptsHigh-Critical
Unsafe ExecutionAI-generated code executed without checksCritical
Package HallucinationNon-existent packages suggested by AIHigh
RAG SecurityData exfiltration, poisoning, PII leaks in RAGMedium-Critical
MCP SecurityTool poisoning, credential exposure, prompt injectionHigh-Critical
Agent SafetyExcessive agency, overpermissive toolsMedium-High
Model Supply ChainUnsafe model loading, unverified sourcesHigh-Critical

Traditional Detectors

CategoryWhat It DetectsCoverage
SecretsAPI keys, tokens, credentialsComprehensive
Config AuditDebug flags, insecure settingsStandard
Weak CryptoMD5, SHA1, DES usageStandard

Three-Layer Detection

Oculum uses a layered approach for accurate detection:

Layer 1: Pattern Matching

Fast, deterministic detection:

  • Regex patterns for known secrets
  • Entropy analysis for potential secrets
  • URL detection for sensitive endpoints

Speed: ~1000 files/second

Layer 2: Structural Analysis

Context-aware heuristics:

  • Auth pattern recognition
  • Dangerous function detection
  • AI code fingerprinting
  • Data flow tracking

Speed: ~500 files/second

Layer 3: AI Semantic Analysis

Deep understanding using Claude:

  • Full taint analysis
  • Business logic validation
  • Cross-file flow tracking
  • Framework-aware analysis

Speed: ~50 files/second


Severity Levels

LevelMeaningAction
CriticalImmediate exploitation riskFix before deploy
HighSignificant security riskFix soon
MediumModerate risk, needs reviewReview and decide
LowMinor issuesConsider fixing
InfoInformationalAwareness only

Confidence Levels

Each finding includes a confidence level:

  • High — Strong evidence, low false positive rate
  • Medium — Good evidence, may need context review
  • Low — Potential issue, requires manual verification

AI-validated findings (--depth verified) have higher confidence levels.


Filtering by Category

Fail on Specific Categories

# Only fail on AI-related issues
oculum scan --fail-on-categories "ai-*"

# Only fail on secrets
oculum scan --fail-on-categories "secrets-*"

# Multiple categories
oculum scan --fail-on-categories "ai-*,secrets-*"

Available Category Prefixes

  • ai-* — All AI security detectors
  • secrets-* — Secret detection
  • owasp-* — Traditional web vulnerabilities
  • config-* — Configuration issues

Understanding Findings

Each finding includes:

  1. Category — The detector that found it
  2. Severity — Impact level
  3. Confidence — Detection certainty
  4. Location — File, line, column
  5. Description — What was found
  6. Remediation — How to fix it
  7. Validation Notes — AI reasoning (for verified scans)

Example Finding

{
  "category": "ai_prompt_injection",
  "severity": "high",
  "confidence": "high",
  "message": "User input passed directly to LLM prompt",
  "file": "src/api/chat.ts",
  "line": 45,
  "remediation": "Validate and sanitize user input before including in prompts",
  "validationNotes": "User input from request body is concatenated directly into the system prompt without sanitization."
}

Quick Reference

| If you're building... | Focus on these detectors | |----------------------|-------------------------| | Chatbot / AI Assistant | Prompt Injection, Agent Safety | | RAG Application | RAG Security, Data Exfiltration | | Code Generation Tool | Unsafe Execution, Package Hallucination | | MCP Server/Client | MCP Security, Tool Poisoning | | Fine-tuning Pipeline | Model Supply Chain |


Next Steps

Explore individual detector categories: