Agent skill · security · jeremylongshore
scanning-for-data-privacy-issues
Scan for data privacy issues and sensitive information exposure. Use
Why this skill is useful
Adds executable scripts for scanning codebases for data privacy violations and generates detailed compliance reports.
What it needs
Requires bash, glob, grep installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Scanning for Data Privacy Issues Overview Scan codebases for data privacy violations, PII exposure, and non-compliance with privacy regulations including GDPR, CCPA, HIPAA, and LGPD. This skill detects hardcoded personal data, unprotected PII in logs and databases, missing consent mechanisms, improper data retention, and insufficient anonymization or pseudonymization of sensitive fields. Prerequisites Access to the target codebase and configuration files in ${CLAUDESKILLDIR}/ Knowledge of the data types processed by the application (PII categories, PHI, financial data) Standard shell utilities and Grep/Glob available for pattern matching Reference: ${CLAUDESKILLDIR}/references/README.md for scanner API documentation, GDPR compliance guide, and sensitive data pattern definitions Instructions 1. Define the PII categories relevant to the application: email addresses, phone numbers, Social Security numbers, credit card numbers, IP addresses, geolocation data, biometric data, health records, and any domain-specific identifiers. 2. Scan source code for hardcoded PII using regex patterns -- detect email patterns ([a-zA-Z0-9+.-]+@[a-zA-Z0-9.-]+), SSN patterns (\d{3}-\d{2}-\d{4}), credit card patterns (Luhn-valid 13-19 digit sequences), and phone number patterns. Flag each as CWE-312 (Cleartext Storage of Sensitive Information). 3. Examine logging statements (console.log, logger.info, logging.debug, Log.d) for PII field references -- flag any logging of user email, password, token, SSN, or credit card fields as CWE-532 (Insertion of Sensitive Information into Log File), severity high. 4. Analyze database schemas and ORM models for PII fields stored without encryption -- check for columns named email, phone, ssn, dateofbirth, address that lack encryption-at-rest annotations or transparent data encryption. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/scanning-for-data-privacy-issues--8d92ff