Municipal developers install unofficial IDE plugins and pull unvetted libraries into a tax-assessment build. Beyond source review, what else must security harden?
Select an answer to reveal the explanation.
Short Explanation
It's not just the app code that can bite you—the workshop, the power tools, and the garage matter too. Risky libraries and sketchy IDE plugins are back doors into city projects. Harden languages, libraries, tools, IDEs, and runtimes, not only the finished binary.
Full Explanation
Application security spans the full development ecosystem: language choice, third-party libraries, IDE extensions, build tools, and runtime platforms. Untrusted plugins or vulnerable dependencies can introduce supply-chain and integrity failures before code reaches production. Controls must cover these layers in addition to application source.