What is Burp Suite and where does it fit in a DevSecOps pipeline?

Describe Burp Suite by the failure it prevents, not by its feature list. It belongs to DAST and manual web security testing and runs at the test stage of delivery, which matters because the cost of fixing a defect rises sharply the later it is found — the core argument behind shifting security left.

Strong answers cover Proxy/Repeater/Intruder workflow, scope configuration, authenticated testing, Burp Suite Enterprise for scheduled CI scans, and where manual testing finds what automated scanners miss (business-logic and auth flaws). Interviewers also listen for the operational side: who owns the rules, how findings reach the developer who introduced them, how false positives get suppressed without silently disabling coverage, and what the break-glass path is when a fix genuinely cannot ship in time.

Tie it to the wider toolchain. Security scanning is only useful when its output is actionable, deduplicated across tools, and attached to a specific commit, image digest or resource — otherwise teams learn to ignore it.