How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

analyzing-web-server-logs-for-intrusion - Skill

Name: analyzing-web-server-logs-for-intrusion
Author: Josepassinato

Imported from Josepassinato/Security (customizations/skills/anthropic-cybersec/skills/analyzing-web-server-logs-for-intrusion/SKILL.md). Install upstream with npx skills add Josepassinato/Security --skill analyzing-web-server-logs-for-intrusion. Copyright stays with the author (Apache-2.0).

Analyzing Web Server Logs for Intrusion

When to Use

When investigating security incidents that require analyzing web server logs for intrusion
When building detection rules or threat hunting queries for this domain
When SOC analysts need structured procedures for this analysis type
When validating security monitoring coverage for related attack techniques

Prerequisites

Familiarity with security operations concepts and tools
Access to a test or lab environment for safe execution
Python 3.8+ with required dependencies installed
Appropriate authorization for any testing activities

Instructions

Install dependencies: pip install geoip2 user-agents
Collect web server access logs in Combined Log Format (Apache) or Nginx default format.
Parse each log entry extracting: IP, timestamp, method, URI, status code, response size, user-agent, referer.
Apply detection rules:
- SQL injection: UNION SELECT, OR 1=1, ' OR ', hex encoding patterns
- LFI/Path traversal: ../, /etc/passwd, /proc/self, php://filter
- XSS: <script>, javascript:, onerror=, onload=
- Scanner signatures: nikto, sqlmap, dirbuster, gobuster, wfuzz user-agents
- Brute force: >50 POST requests to login endpoints from same IP in 5 minutes
Enrich with GeoIP data and generate a prioritized findings report.

python scripts/agent.py --log-file /var/log/nginx/access.log --geoip-db GeoLite2-City.mmdb --output web_intrusion_report.json

Examples

Detect SQLi in URI

192.168.1.100 - - [15/Jan/2024:10:30:45 +0000] "GET /products?id=1' UNION SELECT username,password FROM users-- HTTP/1.1" 200 4532

Scanner User-Agent Detection

Nikto/2.1.6, sqlmap/1.7, DirBuster-1.0-RC1, gobuster/3.1.0

Install analyzing-web-server-logs-for-intrusion and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "josepassinato-security-analyzing-web-server-logs-for-intrusion", "kind": "skill", "name": "analyzing-web-server-logs-for-intrusion", "description": "Parse Apache and Nginx access logs to detect SQL injection attempts, local file inclusion, directory traversal, web scanner fingerprints, and brute-force patterns. Uses regex-based pattern matching against OWASP attack signatures, GeoIP enrichment for source attribution, and statistical anomaly detection for request frequency and response size outliers.", "publisher": "Josepassinato", "version": "1.0.0", "capabilities": { "domains": [ "coding", "data_analysis" ], "tags": [ "skill-md", "analyzing", "web", "server", "logs", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Parse Apache and Nginx access logs to detect SQL injection attempts, local file inclusion, directory traversal, web scanner fingerprints, and brute-force patterns. Uses regex-based pattern matching against OWASP attack signatures, GeoIP enrichment for source attribution, and statistical anomaly detection for request frequency and response size outliers." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/Josepassinato/Security", "path": "customizations/skills/anthropic-cybersec/skills/analyzing-web-server-logs-for-intrusion/SKILL.md", "ref": "065c0e0cfebb3f98d3c07cba0211e1b3d0e3b11b", "url": "https://github.com/Josepassinato/Security/blob/065c0e0cfebb3f98d3c07cba0211e1b3d0e3b11b/customizations/skills/anthropic-cybersec/skills/analyzing-web-server-logs-for-intrusion/SKILL.md", "key": "Josepassinato/Security/customizations/skills/anthropic-cybersec/skills/analyzing-web-server-logs-for-intrusion/SKILL.md" }, "license": "Apache-2.0" }, "instructions": "# Analyzing Web Server Logs for Intrusion\n\n\n## When to Use\n\n- When investigating security incidents that require analyzing web server logs for intrusion\n- When building detection rules or threat hunting queries for this domain\n- When SOC analysts need structured procedures for this analysis type\n- When validating security monitoring coverage for related attack techniques\n\n## Prerequisites\n\n- Familiarity with security operations concepts and tools\n- Access to a test or lab environment for safe execution\n- Python 3.8+ with required dependencies installed\n- Appropriate authorization for any testi", "cost": { "context_tokens": 444 } }

analyzing-web-server-logs-for-intrusion

About

Analyzing Web Server Logs for Intrusion

When to Use

Prerequisites

Instructions

Examples

Detect SQLi in URI

Scanner User-Agent Detection

Install analyzing-web-server-logs-for-intrusion and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews