本文へ移動
cccskills
無料GitHub で公開

threat-detection

This skill should be used when the user asks to "analyze logs for threats", "detect suspicious activity", "scan for brute force attempts", "identify injection attacks", or "audit access patterns for anomalies".

インストール方法を見る

含まれるファイル(3)

  • SKILL.md4.9 KB
  • references/threat-indicators.md3.9 KB
  • scripts/threat_signal_analyzer.py15.9 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Threat Detection

Category: Engineering Domain: Security Operations

Overview

The Threat Detection skill provides automated analysis of log files for suspicious patterns including brute force attacks, injection attempts, unusual access patterns, and privilege escalation indicators. It helps security teams triage log data and identify threats before they escalate.

Clarify First

Before analyzing logs, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Log file & source type — auth / access / application logs to analyze (--file; the subject of detection)
  • Threat category — brute force / injection / access anomaly / privilege escalation (--category; focuses the scan)
  • Minimum severity — the reporting/alert threshold (--min-severity; changes which signals surface and any SIEM/CI gate)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Quick Start

# Analyze a log file for threat signals
python scripts/threat_signal_analyzer.py --file /var/log/auth.log

# Analyze with specific threat category
python scripts/threat_signal_analyzer.py --file access.log --category injection

# JSON output for SIEM integration
python scripts/threat_signal_analyzer.py --file auth.log --format json

# Set minimum severity
python scripts/threat_signal_analyzer.py --file access.log --min-severity high

Tools Overview

threat_signal_analyzer.py

Analyzes log files for suspicious activity patterns across multiple threat categories.

FeatureDescription
Brute force detectionIdentifies repeated failed login attempts from same source
Injection scanningDetects SQL injection, XSS, command injection in requests
Access anomaliesFlags unusual access times, forbidden paths, admin probes
Privilege escalationDetects sudo abuse, role changes, permission modifications
Rate analysisIdentifies request flooding and denial-of-service patterns
IP reputationFlags known-bad patterns (scanners, bots, TOR indicators)

Workflows

Log Analysis Workflow

  1. Collect - Gather logs from auth, access, application sources
  2. Analyze - Run threat_signal_analyzer.py across log files
  3. Triage - Review critical and high severity findings first
  4. Correlate - Cross-reference findings across log sources
  5. Respond - Block IPs, reset credentials, escalate as needed

Incident Investigation Workflow

  1. Scope - Identify time window and affected systems
  2. Scan - Run analyzer on all relevant log files
  3. Timeline - Build timeline from threat signals
  4. Impact - Assess what was accessed or modified
  5. Contain - Block threat actors and patch vulnerabilities

Continuous Monitoring

# Cron job: analyze auth logs every hour
python scripts/threat_signal_analyzer.py --file /var/log/auth.log --format json --min-severity high > /tmp/threat_report.json

# CI/CD: scan application logs on deployment
python scripts/threat_signal_analyzer.py --file app.log --category injection --format json

Reference Documentation

  • Threat Indicators - Common attack patterns, indicators of compromise, response playbooks

Common Patterns Quick Reference

Threat Categories

CategorySignalsSeverity
Brute force5+ failed logins from same IP in 5 minHigh
SQL injectionUNION SELECT, OR 1=1, DROP TABLE in requestsCritical
XSSscript tags, javascript: URIs, event handlers in inputHigh
Path traversal../ sequences, /etc/passwd access attemptsHigh
Command injection; cat /etc/passwd,nc, backtick usage
Admin probing/admin, /wp-admin, /phpmyadmin access attemptsMedium
Rate flooding100+ requests/minute from single IPHigh

Severity Levels

  • CRITICAL - Active exploitation attempt (injection, RCE)
  • HIGH - Likely attack in progress (brute force, privilege escalation)
  • MEDIUM - Suspicious activity requiring investigation
  • LOW - Informational, possible false positive

Response Actions

SeverityImmediate ActionFollow-Up
CriticalBlock IP, alert SOCIncident report, forensics
HighRate limit, monitorReview access, check damage
MediumLog and monitorWeekly review
LowLog onlyMonthly trend analysis

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y issues", "check color contrast", or "find accessibility violations in web pages".

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

Design and analyze A/B tests: sample size, test duration, and statistical significance for conversion experiments. Use when setting up an A/B test, calculating sample size, designing an experiment, or analyzing results.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

Design and run statistically rigorous A/B tests and experiments. Use when planning experiments, calculating sample sizes, designing test variants, selecting metrics, analyzing results, or when someone says "let's test that."

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

Sales execution across pipeline, discovery, demos, negotiation, and closing. Use when qualifying opportunities, running MEDDIC discovery, building account plans, handling objections, structuring proposals, or forecasting pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

Design ad creative across Google, Meta, LinkedIn, Twitter/X, and TikTok with platform format specs, headline formulas, and A/B testing. Use when writing ad copy, generating headline variations, creating ad sets, or validating creative.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

aeo

無料

Answer Engine Optimization (AEO): optimize content to be cited by LLMs (ChatGPT, Claude, Perplexity, Gemini) in their answers. Use when designing content for LLM citation, auditing citability, or structuring Q&A schema.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9012026年10月7日 更新

borghei のスキルをすべて見る

このスキルの問題を報告する