sc-data-exposure

Detect sensitive data exposure patterns in logs, responses, and URLs.

56|5|Updated Apr 8, 2026

Search Tags:#logs #redaction #pii #data-exposure #information-disclosure #error-disclosure

Ready to run

npx skills add https://github.com/ersinkoc/security-check --skill sc-data-exposure

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sc-data-exposure
Source: https://github.com/ersinkoc/security-check/tree/main/skills/sc-data-exposure
Command: npx skills add https://github.com/ersinkoc/security-check --skill sc-data-exposure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects sensitive data exposure across logs, production responses, and deployment artifacts, including PII leaks, verbose stack traces, and exposed configuration, ensuring data does not leave the application boundary unintentionally.

Core Features & Use Cases

Pattern-based detection scans for common leakage patterns in logs, responses, URLs, and deployment artifacts.
Vulnerability guidance provides remediation recommendations and safe handling to redact or suppress sensitive data.
Use case: In production, flag and redact passwords, tokens, and secrets found in logs or API responses to prevent data leaks.

Quick Start

Run an automated scan against your project to identify leaks of PII, debug data, or sensitive information in logs, responses, and URLs.

Frequently Asked Questions about sc-data-exposure

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

FAQPage Schema

How do I detect PII and sensitive data exposure in production logs?▼

Detect sensitive data exposure in production logs by scanning for leakage patterns such as passwords, tokens, and PII. The scan identifies unintentional boundary exits and provides standardized findings with redaction guidance to suppress exposed information.

What causes information disclosure through verbose stack traces in API responses?▼

Information disclosure occurs when verbose stack traces and debug mode are left enabled in production API responses. Scanning codebases for these leakage patterns identifies verbose errors and provides remediation recommendations to suppress sensitive output.

Can I scan codebases across different programming languages for data leaks?▼

Yes, you can scan codebases across multiple programming languages for data leaks. The detection targets production environments by pattern-matching common leakage vectors like exposed configuration and secrets in logs, independent of specific language frameworks.

What is the best way to redact sensitive data found in URLs and deployment artifacts?▼

The best way to redact sensitive data in URLs and deployment artifacts is to run an automated pattern-based scan. This generates standardized findings with CWE mappings and specific redaction guidance to safely remove or mask exposed information.

How do I map detected information disclosure vulnerabilities to standard CWE references?▼

Map detected information disclosure vulnerabilities to standard CWE references using the skill's standardized finding format. Each identified leakage pattern, such as passwords in logs or stack traces in responses, outputs with corresponding CWE mappings and remediation recommendations.