Skip to content

Project/dlp scanner#155

Merged
CarterPerez-dev merged 2 commits intomainfrom
project/dlp-scanner
Apr 10, 2026
Merged

Project/dlp scanner#155
CarterPerez-dev merged 2 commits intomainfrom
project/dlp-scanner

Conversation

@CarterPerez-dev
Copy link
Copy Markdown
Owner

@CarterPerez-dev CarterPerez-dev commented Apr 10, 2026

Description

Provide a clear description of what this pull request does.

Type of Change

  • New project idea (SYNOPSES)
  • Full project implementation
  • Bug fix
  • Documentation improvement
  • Other (please describe)

Checklist

General:

  • My code follows the existing style and conventions
  • I have tested my changes
  • I have updated relevant documentation
  • My changes do not introduce security vulnerabilities
  • I have read the CONTRIBUTING.md guidelines

Related Issues

Link any related issues here (e.g., "Fixes #123").

Additional Context

Any other information that reviewers should know.

Scans files, databases, and network captures for sensitive data
(PII, credentials, financial, health) with 30+ detection rules,
protocol-aware network analysis, DNS exfiltration detection,
compliance mapping (HIPAA, PCI-DSS, GDPR, CCPA), and multi-format
reporting (console, JSON, SARIF, CSV).
Reflect network_scanner.py rewrite, new scoring.py module,
per-brand credit card rule IDs, NPI validator, FL/IL driver's
license rules, Literal config types, and network exfil compliance
mappings.
@gitguardian
Copy link
Copy Markdown

gitguardian bot commented Apr 10, 2026

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
30187048 Triggered Stripe Keys 8d5a177 PROJECTS/intermediate/dlp-scanner/tests/conftest.py View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@CarterPerez-dev CarterPerez-dev merged commit b7c163f into main Apr 10, 2026
22 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant