PII Entity Logging Leak
Detects PII-sensitive terms (email, SSN, password, etc.) appearing inside log calls in added lines.
Why this rule exists
Logs end up in third-party aggregators, support tickets, and analytics pipelines. PII in a log line is PII in every downstream system, often outside the compliance perimeter.
Code example
+ _logger.LogInformation("Login attempt: email={Email}, password={Password}", email, password);+ _logger.LogInformation("Login attempt: userId={UserId}", user.Id);Configuration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0029": { "enabled": true, "severity": "Warn" }
}
}See Configuration for the full schema.
Related rules
Hardcoding and Configuration
Detects hardcoded IPs, URLs, connection strings, secrets, and environment names committed to source.
Security Risk
Detects SQL injection patterns, weak crypto algorithms (MD5, SHA1, DES), dangerous APIs (Assembly.Load, Process.Start), and credential exposure.
Error Handling Integrity
Detects swallowed exceptions (empty catch blocks) and exception handling patterns that hide failures from callers and operators.
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0029_*.cs.
Eric Cogen -- Founder, GauntletCI
Twenty years in .NET production. Most of those years, the bugs that hurt me were not the ones tests caught. They were the assumptions I did not know I was making: a removed guard clause, a renamed method that still did the old thing, a catch {} that turned a page into a silent dashboard lie. GauntletCI is the checklist I wish I had run before every commit. It runs the rules I learned the hard way, so you do not have to.