Some of the most valuable security knowledge is being developed somewhere else.

I did not come into security through a computer science degree, a military background, or an internship at a big firm.

Before cybersecurity, I spent years doing sex work. That required constant, fast judgment about people: who was safe, who was lying, what information to share, when something felt slightly wrong, and when to end a conversation.

When I began learning about social engineering, identity verification, pretexting, and elicitation, I kept recognizing things. I had been doing versions of that work for years. What I was missing was the language, the literature, and the technical grounding.

Pink Team started when I noticed the overlap.

Sex work is where I first recognized this kind of knowledge. It is not the only place it exists.

What kinds of security knowledge are people already building before anyone gives it that name?

People learn to screen strangers, hold boundaries, protect identity, manage reputation, navigate platform risk, and build warning systems long before any institution calls that work security.

That does not automatically make someone a security expert.

But it can produce knowledge worth paying attention to, testing, and developing.

Pink Team is interested in that process.

Pink Team is developing a human-layer security practice focused on trust, identity, social engineering, impersonation, public exposure, and the ways people become the route into a system.

The long-term goal is to create a repeatable and ethical method for assessing the human attack surface around an organization.

That could include examining what information is publicly exposed, where trust is concentrated, which verification steps fail under pressure, and how a believable stranger might gain access.

Pink Team is still early. The work right now is research, writing, technical study, and method development.