logging

Analyze application code for security logging and monitoring failures mapped to OWASP Top 10 2021 A09.

12|1|Updated Feb 9, 2026

Search Tags:#monitoring #security #vulnerability #logging #owasp #audit trail

Ready to run

npx skills add https://github.com/florianbuetow/claude-code --skill logging-florianbuetow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: logging
Source: https://github.com/florianbuetow/claude-code/tree/main/plugins/appsec/skills/logging
Command: npx skills add https://github.com/florianbuetow/claude-code --skill logging-florianbuetow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses critical security gaps in application logging and monitoring, preventing sensitive data exposure, log injection, and ensuring comprehensive audit trails.

Core Features & Use Cases

Security Event Logging: Ensures all critical security events (logins, access denials) are logged with sufficient detail.
Sensitive Data Detection: Identifies and flags instances where sensitive information is written to logs.
Log Injection Prevention: Analyzes code for vulnerabilities where user input could manipulate log entries.
Use Case: A developer can use this Skill to audit their authentication module, ensuring that failed login attempts are logged with the source IP and username, and that no passwords are inadvertently included in the logs.

Quick Start

Use the logging skill to analyze the current codebase for security logging issues.

Frequently Asked Questions about logging

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

FAQPage Schema

How do I check my application code for OWASP A09 security logging failures?▼

To check for OWASP A09 security logging failures, analyze application code to identify missing audit logs for security events, detect sensitive data in logs, and find log injection vulnerabilities. This process maps directly to the OWASP Top 10 2021 A09 standard to ensure comprehensive audit trails.

What is the best way to prevent sensitive data exposure in application logs?▼

Preventing sensitive data exposure in application logs involves scanning the codebase to identify and flag instances where sensitive information is written to logs. This analysis ensures that critical data such as passwords or personal identifiers are not inadvertently included in log entries.

How do I detect log injection vulnerabilities in my source code?▼

Detecting log injection vulnerabilities requires analyzing code for areas where user input could manipulate log entries. This security analysis identifies weaknesses in log generation logic, ensuring that external inputs cannot forge or alter audit trail records.

Can I filter security logging analysis by scope, depth, and severity?▼

Yes, you can filter security logging analysis by scope, depth, and severity. This targeted analysis allows developers to focus on specific modules, such as an authentication component, ensuring failed login attempts are logged with source IP and username without including passwords.

Why does my application lack adequate tamper protection for audit logs?▼

Your application lacks adequate tamper protection if the code analysis reveals insufficient safeguards against log manipulation. Ensuring comprehensive audit trails requires identifying missing alerting on failures and implementing robust tamper protection mechanisms for all security event logs.