implementing-ticketing-system-for-incidents

Pass

Audited by Gen Agent Trust Hub on Apr 8, 2026

Risk Level: SAFEPROMPT_INJECTIONCREDENTIALS_UNSAFEEXTERNAL_DOWNLOADS
Full Analysis
  • [PROMPT_INJECTION]: The skill processes potentially untrusted data from external SIEM alerts to populate incident tickets, which creates a surface for indirect prompt injection.\n
  • Ingestion points: Fields such as rule_name, description, and iocs within the alert_data object in SKILL.md and scripts/agent.py.\n
  • Boundary markers: The generated descriptions use text-based headers (e.g., 'SECURITY INCIDENT — Auto-generated from SIEM') and horizontal separator lines to delimit the external data.\n
  • Capability inventory: The skill utilizes network capabilities to create, update, and escalate records via ServiceNow and TheHive REST APIs.\n
  • Sanitization: No explicit sanitization or escaping mechanisms are implemented for the alert data before its inclusion in the ticket body.\n- [CREDENTIALS_UNSAFE]: The scripts/agent.py script accepts sensitive authentication data, including ServiceNow passwords and TheHive API keys, as command-line arguments. This method of handling credentials can result in secrets being exposed in system process listings and shell command history.\n- [EXTERNAL_DOWNLOADS]: The skill utilizes the 'requests' library, which is a standard and well-known dependency fetched from the official Python Package Index (PyPI).
Audit Metadata
Risk Level
SAFE
Analyzed
Apr 8, 2026, 12:00 AM
Security Audit — agent-trust-hub — implementing-ticketing-system-for-incidents