log-analysis

Correlate authentication, system, application, and web server logs to detect attacker activity patterns.

175|26|Updated Aug 14, 2025
One-click install
npx skills add https://github.com/jmagly/aiwg --skill log-analysis-jmagly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: log-analysis
Source: https://github.com/jmagly/aiwg/tree/main/agentic/code/frameworks/forensics-complete/skills/log-analysis
Command: npx skills add https://github.com/jmagly/aiwg --skill log-analysis-jmagly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of analyzing disparate log files to identify sophisticated cyber threats that would otherwise go unnoticed.

Core Features & Use Cases

  • Multi-Source Log Correlation: Integrates data from auth.log, syslog, journald, application logs, and web server logs.
  • Pattern Detection: Identifies indicators of compromise such as brute force attacks, privilege escalation, and lateral movement.
  • Use Case: A security analyst can trigger this skill after a suspected breach to quickly generate a timeline of attacker activity, pinpointing the entry vector and subsequent actions.

Quick Start

Analyze all available logs on the current system to detect suspicious activity.

Frequently Asked Questions about log-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I correlate logs from multiple sources to detect security threats?

Correlating logs from multiple sources detects security threats by integrating auth.log, syslog, journald, application logs, and web server logs to identify attacker activity patterns. This process uncovers sophisticated cyber threats through automated multi-source data analysis.

What is the best way to identify brute force attacks and privilege escalation in system logs?

Identifying brute force attacks and privilege escalation in system logs is best achieved by analyzing auth.log and journald entries for suspicious authentication patterns. This approach pinpoints indicators of compromise by detecting repeated failed logins and unauthorized permission changes.

Can I trace lateral movement across authentication and web server logs?

You can trace lateral movement across authentication and web server logs by correlating access patterns between auth.log and web server entries. This multi-source correlation identifies how attackers pivot through the network after their initial entry vector.

How does automated threat hunting build a timeline of suspicious events from journald and syslog?

Automated threat hunting builds a timeline of suspicious events from journald and syslog by parsing and correlating sequential log entries. It satisfies incident response requirements by producing a structured chronological view of attacker activity across disparate system files.

Does multi-source log analysis work for incident response after a suspected breach?

Multi-source log analysis works for incident response after a suspected breach by quickly generating a timeline of attacker activity. Security analysts trigger this correlation to pinpoint the entry vector and subsequent actions across system and application logs.