The vulnerability queue needs faster decisions without turning inferred reachability into a security verdict.
One side protects response time for exposed services, while the other protects the proof required before a finding changes priority.
Who you’d be doing this for
“Our security review asked which findings touch live retrieval, and I had no clean answer.”
Clement Johnson · IT Platform Owner
Owns secure internal knowledge access and must answer security reviewers about the reliability of the enterprise index.
What is at stake
Only 32% of dependency findings receive a human triage decision within one business day. You must weigh faster routing against the evidence reviewers need before treating a finding as urgent.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- faster triage vs. defensible security evidence
- reachability inference vs. reviewer judgment
- queue throughput vs. audit readiness
- cross-system context vs. access boundaries
Why Glean
Permission-aware retrieval depends on storage, access controls, and query paths that regulated customers expect to be protected by demonstrable vulnerability discipline.
Written with these in mind
Not your kind of problem? 29 more at Glean, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.