Skip to content

Back to the catalog

Security Engineering is a Context Problem
aseemshrey.inarticle

Security Engineering is a Context Problem

An essay arguing that security engineering is fundamentally a "context problem": scanners (SAST, cloud posture tools, CVE scanners) are cheap at generating findings but structurally strip the context (asset ownership, reachability, data sensitivity, business criticality) needed to triage them, which is why backlogs of thousands of findings pile up untouched. The author (an independent security advisor) proposes attaching context at detection time rather than triage time, argues hiring should shift toward "fast codebase ramp-up" skills over vulnerability-class knowledge, and frames LLMs as well-suited to the context-gathering legwork (reading code, walking call graphs, correlating tickets) rather than final risk decisions. It's Part 1 of a planned series, with future posts promised on SOC alert triage and AWS/cloud findings specifically.

TL;DR Security triage backlogs balloon not from lack of tooling but because scanners strip the ownership/reachability/business context needed to act on findings — and that's exactly the gap LLMs are well-suited to close.

Technologies named here

Techniques named here