Skip to content
Skillpedia
Misc35k · #5970

implementing-ticketing-system-for-incidents

Lets your agent create a ticketing system for security incidents. It connects alerts to management systems to track issues. It's useful for organizing incident response workflows.

What it does

This tool automates the creation of security incident tickets, connecting alerts from your monitoring system (SIEM) to platforms like ServiceNow, Jira, or TheHive. It helps organize tracking, manage deadlines, and document everything for compliance.

When to use it

  • ✓When the security team needs an organized process for handling incidents.
  • ✓To meet regulations requiring detailed incident documentation.
  • ✓When multiple teams need to collaborate on an incident with clear tasks and deadlines.

Example of what to ask your AI

“Create an incident ticket from the 'Malware Detected' alert with 'High' severity and assign it to the 'SOC Tier 2' team.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/main/skills/implementing-ticketing-system-for-incidents/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/main/skills/implementing-ticketing-system-for-incidents/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool receives security alerts from your monitoring system. It then automatically creates a ticket in a management platform (like ServiceNow), filling in important details like the alert type, severity, and who should resolve it.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill implementing-ticketing-system-for-incidents

Or download just the file:

curl -L https://raw.githubusercontent.com/mukul975/Anthropic-Cybersecurity-Skills/main/skills/implementing-ticketing-system-for-incidents/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Implementing Ticketing System for Incidents

When to Use

Use this skill when:

  • SOC teams need to formalize incident tracking beyond SIEM notable event management
  • Compliance requirements mandate documented incident lifecycle with timestamps and audit trails
  • Multi-team coordination requires ticket-based workflows with assignment and escalation
  • SLA tracking needs automated measurement of response and resolution times
  • Post-incident reviews require structured data for trend analysis and reporting

Do not use for individual alert triage — ticketing is for confirmed incidents requiring multi-step investigation and remediation, not every SIEM alert.

Prerequisites

  • Ticketing platform: ServiceNow ITSM, Jira Service Management, or TheHive
  • SIEM integration capability (REST API, webhook, or SOAR connector)
  • Incident classification taxonomy (categories, severity levels, escalation paths)
  • On-call rotation schedule for analyst assignment
  • SLA definitions aligned to incident severity

Workflow

Step 1: Define Incident Classification Taxonomy

Establish standardized incident categories and severity:

incident_taxonomy:
  categories:
    - malware_infection
    - phishing_campaign
    - unauthorized_access
    - data_exfiltration
    - denial_of_service
    - ransomware
    - insider_threat
    - vulnerability_exploitation
    - account_compromise
    - policy_violation

  severity_levels:
    critical:
      definition: "Active data breach, ransomware, or business-critical system compromise"
      response_sla: 15 minutes
      resolution_sla: 4 hours
      escalation: immediate to Tier 3 + CISO notification
      examples: ["Active ransomware", "Domain admin compromise", "Customer data breach"]

    high:
      definition: "Confirmed compromise of business systems or multiple user accounts"
      response_sla: 30 minutes
      resolution_sla: 8 hours
      escalation: Tier 2 immediate, Tier 3 if unresolved in 2 hours
      examples: ["Malware with C2", "Lateral movement detected", "Phishing with credential theft"]

    medium:
      definition: "Confirmed security event requiring investigation and remediation"
      response_sla: 2 hours
      resolution_sla: 24 hours
      escalation: Tier 2 within 4 hours
      examples: ["Single phishing click", "Unauthorized software", "Policy violation"]

    low:
      definition: "Minor security event with limited impact"
      response_sla: 8 hours
      resolution_sla: 72 hours
      escalation: Tier 1 standard queue
      examples: ["Scan attempt", "Failed brute force (no compromise)", "Info disclosure"]

Step 2: Automate Ticket Creation from SIEM

ServiceNow Integration via REST API:

import requests
import json
from datetime import datetime

class IncidentTicketManager:
    def __init__(self, snow_url, snow_user, snow_password):
        self.snow_url = snow_url
        self.auth = (snow_user, snow_password)
        self.headers = {
            "Content-Type": "application/json",
            "Accept": "application/json"
        }

    def create_incident(self, alert_data):
        """Create ServiceNow incident from SIEM alert"""
        severity_map = {
            "critical": "1",
            "high": "2",
            "medium": "3",
            "low": "4"
        }

        payload = {
            "short_description": f"[SEC] {alert_data['rule_name']} — {alert_data['src']}",
            "description": self._build_description(alert_data),
            "category": "Security",
            "subcategory": alert_data.get("category", "Investigation"),
            "urgency": severity_map.get(alert_data["severity"], "3"),
            "impact": severity_map.get(alert_data["severity"], "3"),
            "assignment_group": self._get_assignment_group(alert_data["severity"]),
            "caller_id": "soc_automation",
            "u_siem_event_id": alert_data.get("notable_id", ""),
            "u_mitre_technique": alert_data.get("mitre_technique", ""),
            "u_affected_hosts": ", ".join(alert_data.get("affected_hosts", [])),
            "u_iocs": json.dumps(alert_data.get("iocs", {}))
        }

        response = requests.post(
            f"{self.snow_url}/api/now/table/incident",
            auth=self.auth,
            headers=self.headers,
            json=payload
        )
        result = response.json()["result"]
        return {
            "ticket_number": result["number"],
            "sys_id": result["sys_id"],

…
FAQ

What is an 'incident ticket'?

It's a formal record of a security issue that needs investigation and resolution, containing details about what happened, who is responsible, and the deadline.

What is SIEM?

SIEM (Security Information and Event Management) is a system that collects and analyzes security data from various devices to detect threats.

What are SLAs?

SLAs (Service Level Agreements) are agreements that define the expected time to respond to and resolve an incident, based on its severity.

Details

Original description by the author

Implements an integrated incident ticketing system connecting SIEM alerts to ServiceNow, Jira, or TheHive for structured incident tracking, SLA management, escalation workflows, and compliance documentation. Use when SOC teams need formalized incident lifecycle management with automated ticket creation, assignment routing, and resolution tracking. '

repo: mukul975/Anthropic-Cybersecurity-Skills

Popularity

GitHub stars
35k
Ranking position
#5970
License
Apache-2.0
Updated
8/31/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills