create_remediation_ticket
Create a remediation ticket for a detected attack path, initiating immediate upstream ticket creation and a background remediation loop.
Instructions
Create a remediation ticket for an attack path and start two-step remediation.
Creates the upstream ticket on the active provider immediately (~seconds), then runs the LLM+JEPA remediation loop in the background and updates the ticket. Poll get_ticket_steps for per-iteration progress. Provider-agnostic: the ticket lands on whichever provider is currently active (see get_ticket_provider).
Args: path_id: Attack path ID (from triage / validation tools). repository_id: InfraDB repository ID the path belongs to. branch_id: InfraDB branch ID. entry_node: Path entry node ID. target_node: Path target node ID. steps: JSON array of path-step objects (source_node/target_node/...). step_count: Number of steps in the path. risk_score: Path risk score (0.0-1.0). mitre_techniques: JSON array of MITRE ATT&CK technique IDs. difficulty: Path difficulty ("low"/"medium"/"high"). source: Optional origin tag for the ticket. validation_verdict: Optional JSON object with the validation verdict.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path_id | Yes | ||
| repository_id | Yes | ||
| branch_id | Yes | ||
| entry_node | Yes | ||
| target_node | Yes | ||
| steps | No | [] | |
| step_count | No | ||
| risk_score | No | ||
| mitre_techniques | No | [] | |
| difficulty | No | medium | |
| source | No | ||
| validation_verdict | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |