The math changed

Take a team of eight engineers. Before assistants, they opened about 40 pull requests a week, and two senior engineers spent around half their time reviewing. With assistants the same team opens 80. The seniors didn't get twice as many hours, so each pull request now gets half the attention it used to.

Those numbers are an example, not a benchmark, but the shape is what most teams report. Writing scaled. Reviewing didn't. The patterns that slip through are the well-known ones: injection, hardcoded secrets, disabled checks, outdated packages, missing ownership checks. Those are exactly what scanners are good at, which is what frees human reviewers for design and business logic.

Which scanner catches which AI mistake

AI mistakeExampleScannerBest place to run it
String-built queries, unsafe deserializationf"... WHERE id = {id}"SASTIDE and pull request
Security checks switched offverify=False, @csrf_exemptSAST, Vibe CodePull request (block)
Placeholder keys that are realsk_live_... "for testing"SecretsPre-commit and pull request
Made-up or outdated packagesPyJWT==1.7.1, invented namesSCA, MalwarePull request
Open-by-default infrastructure0.0.0.0/0, Action: "*"IaCPull request, before apply
Old base images, root containersFROM node:14, no USERContainerCI image build
Real data copied into fixturesproduction rows in tests/PIIPull request
Missing ownership checksfindById(req.params.id)API, DASTStaging, nightly and on deploy

Put each check where it's cheapest

A finding costs the least when it's fixed while the AI suggestion is still on the developer's screen. It costs the most after release. So push each check as far left as it can reliably run:

IDE Pull request CI build Staging Production SASTSecrets SAST · SCASecrets · IaCPII · Malware Containerimage CVEs DAST · APItwo-user tests ContinuousDAST + ASM cheap to fix expensive to fix

Noise is the real risk

A scanner that floods developers with false positives does more harm than good. People learn to click past it, and then they click past the real finding too. With AI multiplying the amount of code, the raw number of findings goes up with it, so triage matters more than it did before.

That's why AquilaX runs every finding through Securitron AI before it reaches a developer. It checks whether the code path is actually reachable and exploitable in context, and drops the ones that aren't. The goal is a short list people actually read.

A rollout that doesn't stall the team

  1. Week 1: secrets and SCA, blocking on new code only. Low noise, high value, and the fixes are usually a key rotation or a version bump.
  2. Week 2: SAST high and critical in pull requests. Start with injection, disabled checks and deserialization. Add more rules once people trust the signal.
  3. Week 3: IaC and container scanning in CI. Block public storage, wildcard IAM and root containers. Warn on the rest.
  4. Week 4: DAST and API scanning on staging. Nightly, and after each deploy. This is where ownership bugs get caught.
  5. Baseline the backlog separately. Existing findings go into a tracked list with owners and dates. New code is held to the bar from day one, and nobody gets blocked by a five-year-old issue they didn't write.

Rule of thumb: if a check is fast and precise, block. If it's slow or noisy, report. Move checks from report to block as the signal improves.

Read the rest of the series

This guide ties together the four patterns covered in the other posts in this series: why AI writes average code, fixes that delete security checks, dependencies frozen at the training cutoff, and missing ownership checks. Each one has concrete examples and the matching fix.

One platform for every stage

SAST, SCA, secrets, IaC, container, PII, malware, API and DAST, with AI triage so your team only sees what's real.

See all scanners →