samber/cc-skills-golang / skills/golang-security
golang-security
FlaggedSecurity best practices and vulnerability prevention for Golang — injection (SQL, command, XSS), cryptography, path traversal, SSRF and HTTP security headers, cookies, secrets management, memory safety, PII in logs, STRIDE/DREAD threat modeling, plus `gosec` SAST, race detection, and fuzz testing. Apply when writing, reviewing, or auditing Go code for security, or when touching crypto, file or network I/O, secrets, user input, or authentication. Not for non-exploitable defensive bugs such as nil panics or slice aliasing (→ See `samber/cc-skills-golang@golang-safety` skill), dependency vulnerability scanning with govulncheck (→ See `samber/cc-skills-golang@golang-dependency-management` skill), or wiring security scanners into CI pipelines (→ See `samber/cc-skills-golang@golang-continuous-integration` skill).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.0 KB |
| evals/evals.json | config | 49.0 KB |
| references/architecture.md | markdown | 10.4 KB |
| references/checklist.md | markdown | 4.0 KB |
| references/cookies.md | markdown | 4.8 KB |
| references/cryptography.md | markdown | 11.0 KB |
| references/filesystem.md | markdown | 6.8 KB |
| references/injection.md | markdown | 7.3 KB |
| references/logging.md | markdown | 3.9 KB |
| references/memory-safety.md | markdown | 5.1 KB |
| references/network.md | markdown | 6.3 KB |
| references/secrets.md | markdown | 4.8 KB |
| references/third-party.md | markdown | 4.9 KB |
| references/threat-modeling.md | markdown | 8.4 KB |
references/third-party.md
View on GitHub# Third-Party Data Leak Rules
Third-party monitoring and analytics services can inadvertently transmit sensitive user data to external systems.
**Rules:**
1. PII MUST be filtered before sending to third-party services.
2. Error tracking MUST NOT receive raw user data — use `BeforeSend` hooks to redact.
---
## Table of Contents
- [Overview](#overview)
- [Common Vulnerable Services](#common-vulnerable-services)
- [Error Tracking Services — Medium](#error-tracking-services--medium)
- [Analytics/Monitoring Services — Medium](#analyticsmonitoring-services--medium)
- [Data Filtering Layer](#data-filtering-layer)
- [Review Checklist](#review-checklist)
- [CWE References](#cwe-references)
## Overview
These rules detect Go code that sends data to third-party services. Always review what data is being transmitted and ensure it complies with privacy regulations (GDPR, CCPA, etc.).
---
## Common Vulnerable Services
| Service | Risk |
| ---------------- | ----------------------------------------------------- |
| Airbrake | Error tracking - sensitive data may be sent |
| Bugsnag | Error tracking - sensitive data exposure |
| Sentry | Error tracking - sensitive data in breadcrumbs/events |
| Rollbar | Error tracking - sensitive data leaks |
| Honeybadger | Error tracking - sensitive data leaks |
| New Relic | Monitoring - sensitive data exposure |
| Datadog | Monitoring - sensitive data in telemetry |
| OpenTelemetry | Observability - sensitive data in traces/metrics |
| Google Analytics | Analytics - PII tracking risks |
| Algolia | Search API - data exfiltration risks |
| Segment | Analytics - PII tracking risks |
| BigQuery | Analytics - sensitive data in queries |
| ClickHouse | Database - sensitive data queries |
| Elasticsearch | Search engine - sensitive data in queries |
---
## Error Tracking Services — Medium
**Bad:**
```go
import "github.com/getsentry/sentry-go"
sentry.CaptureException(err) // DON'T: Captures full request context
```
**Good:**
```go
sentry.Init(sentry.ClientOptions{
Dsn: "https://xxx@sentry.io/123",
RequestHeaders: []string{"Accept", "User-Agent"},
BeforeSend: func(event *sentry.Event, hint *sentry.EventHint) *sentry.Event {
// Remove sensitive headers
if event.Request != nil {
delete(event.Request.Headers, "Authorization")
delete(event.Request.Headers, "Cookie")
}
return event
},
})
```
---
## Analytics/Monitoring Services — Medium
**Bad:**
```go
analytics.Track("user_signed_up", analytics.Properties{
"email": user.Email, // DON'T: PII!
"phone": user.Phone, // DON'T: PII!
"address": user.Address, // DON'T: PII!
})
```
**Good:**
```go
analytics.Track("user_signed_up", analytics.Properties{
"user_id": user.ID, // OK: Internal identifier
"plan": user.Plan, // OK: Business data
"country": user.CountryCode, // OK: Non-identifying
})
// Hash PII for correlation
func hashEmail(email string) string {
h := sha256.New()
h.Write([]byte(email))
return hex.EncodeToString(h.Sum(nil))[:8]
}
```
---
## Data Filtering Layer
```go
type DataFilter struct {
sensitiveFields []string
}
func NewDataFilter() *DataFilter {
return &DataFilter{
sensitiveFields: []string{
"password", "token", "secret", "key", "email",
"phone", "address", "ssn", "credit_card", "bank_account",
},
}
}
func (f *DataFilter) Filter(data map[string]interface{}) map[string]interface{} {
result := make(map[string]interface{})
for k, v := range data {
keyLower := strings.ToLower(k)
isSensitive := false
for _, field := range f.sensitiveFields {
if strings.Contains(keyLower, field) {
isSensitive = true
break
}
}
if isSensitive {
result[k] = "[REDACTED]"
} else {
result[k] = v
}
}
return result
}
```
---
## Review Checklist
Before integrating any third-party service:
- [ ] Identify what data is being sent
- [ ] Remove any PII/PHI from transmitted data
- [ ] Review data residency requirements
- [ ] Implement data retention policies
- [ ] Set up data export logging/auditing
- [ ] Configure error handling to avoid data exposure
- [ ] Review terms of service for data usage
- [ ] Implement user consent management
- [ ] Support data deletion requests
- [ ] Conduct regular data flow audits
---
## CWE References
- **CWE-200**: Exposure of Sensitive Information
- **CWE-359**: Exposure of Private Personal Information
- **CWE-201**: Information Exposure Through Sent Data
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |