Here's a summary of my findings.
- incoming data from an untrusted source is untrusted data or unvalidated data
- it passes a trust boundary on its way into a trusted environment or trusted domain
- a validation process can label the data trusted, in my question I described a use case where this state is named "whitelisted"
- while validating the data upon violations the system can
- block the data
- sanitize the data
Some references ...
IDS00-J. Sanitize untrusted data passed across a trust boundary:
Many programs accept untrusted data originating from unvalidated users, network connections, and other untrusted sources and then pass the (modified or unmodified) data across a trust boundary to a different trusted domain.
Input Validation and Data Sanitization:
Data received by a component from a source outside the component's trust boundary can be malicious and can result in an injection attack
Please see the given data flow diagram, where the incoming data is labeled "untrusted data".
Trust Boundary Violation:
A trust boundary can be thought of as line drawn through a program. On one side of the line, data is untrusted. On the other side of the line, data is assumed to be trustworthy. The purpose of validation logic is to allow data to safely cross the trust boundary--to move from untrusted to trusted.
So Adnan, your conclusion "untrusted" seems pretty legit. And Saladin, "un-sanitized" seems to fit somehow but I do like "untrusted" more because it seems to be more common and sanitization does not happen all the time.