java-sensitive-log-auditor

Detect sensitive data exposures in Java logs, stack traces, and exception messages.

1|1|Updated Apr 16, 2026

Search Tags:#security #logging #audit #java #gdpr #pci-dss #data-leaks

Ready to run

npx skills add https://github.com/iCesofT/awesome-ai --skill java-sensitive-log-auditor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: java-sensitive-log-auditor
Source: https://github.com/iCesofT/awesome-ai/tree/main/skills/03-development-java-sensitive-log-auditor
Command: npx skills add https://github.com/iCesofT/awesome-ai --skill java-sensitive-log-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits Java code to locate leaks of sensitive data in logs, errors, and traces, helping teams prevent GDPR/PCI-DSS breaches.

Core Features & Use Cases

Detects sensitive data exposures in SLF4J/Log4j logs, System.out/err, toString outputs, and exception messages.
Analyzes sources like field names (iban, dni, email, password) and literals to identify potential leaks.
Recommends safe masking and remediation patterns to fix issues in code and logging configurations.
Use cases: when reviewing .java files, during code reviews for logging practices, or during security audits of Java services.

Quick Start

Run the java-sensitive-log-auditor scan on your Java project to detect and report sensitive data exposures in logs, stack traces, and exception messages.

Frequently Asked Questions about java-sensitive-log-auditor

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

FAQPage Schema

How do I detect sensitive data leaks in Java logs?▼

To detect sensitive data leaks in Java logs, you need to audit code for exposures in SLF4J/Log4j outputs, System.out/err, and exception messages by analyzing sensitive field names like iban or password. This process identifies potential breaches and returns structured findings with severity and masking recommendations.

What is the best way to check my Java code for GDPR and PCI-DSS logging violations?▼

The best way to check Java code for GDPR and PCI-DSS logging violations is to scan .java files for sensitive data exposures in stack traces and exception messages. This audit detects sources like email and password literals, providing remediation guidance to ensure compliance.

How does sensitive data detection work in Java stack traces and exception messages?▼

Sensitive data detection works by analyzing Java code to locate sinks, such as log outputs and toString methods, and tracing them back to sources like sensitive field names and literals. It then reports these exposures with structured findings and safe masking patterns.

Can I use this audit to find unmasked IBAN or DNI fields in Log4j configurations?▼

Yes, you can use this audit to find unmasked IBAN or DNI fields by scanning Java services that use Log4j. The auditor detects sensitive field names and literals in log outputs, returning structured findings with masking recommendations to secure the data.

What are common sources of sensitive data exposure in Java applications?▼

Common sources of sensitive data exposure in Java applications include sensitive field names like iban, dni, email, and password, as well as hardcoded literals. These sources often leak through SLF4J/Log4j logs, System.out/err, and unmasked toString outputs in exception messages.

Does this logging audit work for code reviews of Java services?▼

Yes, this logging audit works for code reviews of Java services by scanning .java files to identify sensitive data exposures in logging practices. It returns structured findings with severity levels and remediation guidance to help teams fix issues during the review process.