sc-data-exposure

Detect PII leaks and verbose errors in logs and API responses.

Updated Aug 23, 2026

Search Tags:#pii #production-security #data-exposure #logging-redaction #information-disclosure #verbose-errors

Ready to run

npx skills add https://github.com/kocakburhan/emlakdefter --skill sc-data-exposure-kocakburhan

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sensitive data exposure including PII leaks, verbose errors, debug mode, and information disclosure are common production risks. This skill helps teams identify and mitigate these risks across logs, API responses, and deployment configurations.

Core Features & Use Cases

Detects PII leaks in logs, production responses, and error messages
Flags verbose error outputs and debug mode exposure
Identifies information disclosure patterns in URLs, headers, and configuration files
Provides remediation guidance and recommended mitigations to redact data and disable unsafe defaults

Quick Start

Run the sc-data-exposure check against your production logs and API responses to surface sensitive data leaks.

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 leaks in production logs and API responses?▼

To detect PII leaks in production logs and API responses, run an exposure check against your data pipelines to surface sensitive information using keyword patterns and vulnerability checks, returning remediation guidance for redaction.

What is the best way to prevent sensitive data exposure in configuration files?▼

The best way to prevent sensitive data exposure in configuration files is to identify information disclosure patterns and apply recommended mitigations that disable unsafe defaults and redact sensitive data across your environments.

How do I redact verbose error outputs and debug mode information across staging environments?▼

You redact verbose error outputs and debug mode information by applying log redaction guidance and vulnerability checks to your staging configurations, ensuring verbose errors and debug exposure are flagged for remediation.

Does this sensitive data detection approach work across development, staging, and production environments?▼

Yes, this sensitive data detection approach works across development, staging, and production environments, applying keyword patterns and vulnerability checks to log pipelines, API responses, and configuration files to identify information disclosure.

Why are verbose errors and information disclosure considered production security risks?▼

Verbose errors and information disclosure are production security risks because they expose sensitive data, PII leaks, and internal system details through API responses and error messages, allowing attackers to map vulnerabilities.

What remediation steps are recommended when PII leaks are found in URLs and headers?▼

When PII leaks are found in URLs and headers, recommended remediation steps include applying log redaction guidance, disabling unsafe defaults, and implementing safe handling of data to prevent further information disclosure.