- Taint tracking
- Following untrusted input through a program to see where it ends up. The input is marked where it arrives, then tracked across assignments, calls and service boundaries until it either reaches something dangerous or is made safe.
- Triage
- Deciding which findings deserve attention. Triage is a response to volume, and most security tooling is built to help teams sort a long list faster. The other option is to produce fewer, better-founded findings so that sorting matters less.
- Trust boundary
- The line where data moves between something you control and something you do not. Request handlers, queue consumers and the joins between services are all trust boundaries. Assumptions that hold on one side of that line frequently stop holding on the other.
- Trust gradient
- The staged path from reviewing every suggested fix to letting them go straight to a developer. You would not give a new colleague production access on their first day. A trust gradient applies the same judgement to an automated one, widening access at the pace the evidence earns it.