[REVIEW] hipaa-review: add de-identified dataset reidentification gates

[stmr]

Skill Being Reviewed

Skill name: hipaa-review
Skill path: skills/compliance/hipaa-review/

False Positive Analysis

Benign code that triggers a false positive:

De-identification method documents expert determination or safe-harbor field removal.

Why this is a false positive:
The current review guidance can push an agent to flag this pattern without first proving the attacker-controlled path, tenant boundary, or effective runtime behavior. The review should require evidence before classification.

Coverage Gaps

Missed variant 1:

Analytics dataset keeps rare ZIP/date/device combinations that re-identify patients.

Why it should be caught:
This is a realistic failure mode for hipaa-review. It changes the effective security boundary without matching the simpler examples currently emphasized by the skill.

Missed variant 2:

Supposed de-identified data is joinable with support tickets containing identifiers.

Why it should be caught:
This variant commonly appears in production systems and needs explicit reviewer prompts so agents do not stop at static configuration review.

Edge Cases

De-identification is contextual and needs linkage analysis.

Remediation Quality

• Fix resolves the vulnerability
• Fix doesn't introduce new security issues
• Fix doesn't break functionality
• Issues found: Remediation guidance should add an evidence gate for the specific boundary, a benign exception pattern, and a regression check. Without those, fixes may be either cosmetic or over-broad.

Comparison to Other Tools

Tool	Catches this?	Notes
Semgrep	Partial	Can catch static patterns, but not effective policy, ownership, or runtime propagation without custom rules.
CodeQL	Partial	Strong for code/data-flow cases, weaker for cloud/control-plane and process evidence unless modeled.
Other: manual review	Yes	Human review can verify effective behavior, exception ownership, and operational evidence.

Overall Assessment

Strengths:
The skill gives useful practitioner framing and asks for concrete evidence instead of generic advice.

Needs improvement:
Need re-identification risk gates.

Priority recommendations:

1. Add a checklist item for de-identified dataset reidentification evidence.
2. Add one benign exception example so reviewers avoid noisy findings.
3. Add one regression or verification step that proves the effective boundary after remediation.

Bounty Info

• I have read and agree to the CONTRIBUTING.md bounty terms
• Preferred payment method: PayPal samik4184@gmail.com

[daviediao-code]

Security Review: hipaa-review

Summary: Reviewed hipaa-review skill for bounty spec — de-identified dataset reidentification gates. Skill provides structured hipaa-review review guidance with framework mapping.

Key Findings:

1. Framework References — Score: 4/4
   Found 5 framework references: NIST, CIS, STIG, HIPAA.
   Solid multi-framework grounding.

2. Injection Hardened — Score: 3/3
   Covers injection prevention and sanitization patterns.

3. Test Fixtures — Score: 0/3
   No test fixture directories found — universal gap across reviewed skills.

4. Structured Output — Score: 1/3
   Could add structured output fields (severity level, CWE, remediation priority).

5. Coverage Depth — Score: 3/3
   Contains 18 major sections. Good depth with thorough coverage.

6. AI Agent Tested — Score: 1/1
   Evidence of agent-tested patterns and playbook validation.

7. Gap-Specific Analysis — Score: 3/6
   Bounty spec: "de-identified dataset reidentification gates".
   Could better align with bounty spec requirements.

Quality Score: 15/23

Recommendation: Approve with minor revisions ⚠️

---

Reviewed by daviediao-code | Category: hipaa-review | Date: 2026-06-16

[JamesJi79]

/attempt

[JamesJi79]

Implemented in PR #2696.

Gate file: skills/compliance/hipaa-review/gates/de-identified-reidentification-gate.md

This gate adds de-identified dataset reidentification gate.