# CD-SEC-04 - Sensitive Data Leakage and Handling Failures

> Platforms have no semantic understanding of which fields are sensitive, leading to PII/PHI exposure.

- **Category**: Owasp Citizen Development
- **Subcategory**: top10
- **Canonical URL**: https://designpattern.fyi/owasp_citizen_development/cdsec04_sensitive_data_leakage/

---

## Description
'**Intent**: Prevent sensitive data (PII/PHI) from flowing through misconfigured connectors, public endpoints, unencrypted logs, or AI prompts.

**Context**: Platforms have no semantic understanding of which fields are sensitive, so PII/PHI flows through misconfigured connectors, public endpoints, unencrypted logs, or AI prompts (e.g., pasting raw support tickets into an AI assistant) without anyone intending it.

**Solution**: Implement approved-connector allowlists. Restrict custom connector creation to trained personnel. Monitor for data flows that cross organizational boundaries, including multi-hop paths. Require security review for any citizen-built app touching sensitive data stores. Implement data loss prevention (DLP) controls.'



## Use Cases
Use when building low-code/no-code applications or AI-assisted code that processes sensitive data or connects to external systems.





## Trade-offs


### Advantages

- Prevents data breaches

- Enables data flow visibility

- Supports compliance requirements

- Protects sensitive information




### Considerations & Drawbacks

- Connector allowlists may limit functionality

- Data flow monitoring complexity

- DLP implementation overhead







---
**Reference**: [Original Source](https://owasp.org/www-project-citizen-development-top10-security-risks/)