Detect sensitive data exposure patterns in logs, responses, and URLs.
npx skills add https://github.com/ersinkoc/security-check --skill sc-data-exposure
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
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.
Run an automated scan against your project to identify leaks of PII, debug data, or sensitive information in logs, responses, and URLs.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
abzhawIdentify exposed secrets in source files, git history, and runtime logs.
kzahediRun valgrind to detect memory leaks and errors in YARS.
MesteriisReview configuration files for exposed secrets and security risks.
JGalegoDetect and redact secrets and PII from text using regular expressions.
