Logging Failures

Detect logging failures and apply secure coding practices across Python, Java, Go, TypeScript, and PHP.

22|3|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/allsmog/vuln-scout --skill logging-failures
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Logging Failures
Source: https://github.com/allsmog/vuln-scout/tree/main/whitebox-pentest/skills/logging-failures
Command: npx skills add https://github.com/allsmog/vuln-scout --skill logging-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify and prevent vulnerabilities related to insufficient logging, log injection, secrets in logs, and log tampering, ensuring your application's security events are properly recorded and protected.

Core Features & Use Cases

  • Detect Log Injection: Find instances where user input can manipulate log entries (CWE-117).
  • Identify Insufficient Logging: Ensure critical security events like authentication and authorization failures are logged (CWE-778).
  • Prevent Secrets in Logs: Detect and help redact sensitive information (passwords, tokens) from log files (CWE-532).
  • Mitigate Log Tampering: Identify potential weaknesses that could allow attackers to alter or delete logs.
  • Ensure Proper Alerting: Verify that security-relevant events trigger appropriate alerts.
  • Use Case: During a whitebox penetration test, you discover that failed login attempts are not logged. This skill provides the patterns to find where authentication is handled and highlights the missing logging statements, guiding the developer to add them.

Quick Start

Analyze the codebase for any instances of log injection vulnerabilities.

Frequently Asked Questions about Logging Failures

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

FAQPage Schema
How do I detect log injection vulnerabilities in my application code?

You can identify insufficient logging by scanning for missing audit trails on critical security events like authentication failures. This Skill detects CWE-778 by highlighting where logging statements are absent in authorization and authentication handlers across multiple languages.

How do I prevent passwords and tokens from being exposed in application logs?

To prevent secrets exposure in logs, you must detect and redact sensitive information like passwords and tokens. This Skill identifies CWE-532 instances by finding code patterns that output sensitive data to log files, providing secure coding practices for redaction.

Does this Skill align with OWASP A09 security logging and monitoring requirements?

Yes, this Skill aligns with OWASP A09 by mitigating security risks associated with logging failures. It ensures your application properly records security events by identifying log tampering weaknesses and verifying that security-relevant events trigger appropriate alerts.

Can I use this to find missing logging statements during a whitebox penetration test?

You can use this Skill during a whitebox penetration test to find missing logging statements. It provides detection patterns to locate where authentication is handled and highlights missing audit trail entries, guiding developers to add the necessary logging.

What are the limitations of relying on standard application logs for audit trails?

Standard application logs are vulnerable to log tampering and insufficient logging of critical events. This Skill helps identify these weaknesses by detecting potential code paths that allow attackers to alter logs and finding missing security event triggers.