[FF] bl_security_analyzer -- Business Logic Security Analyzer closed beta

Summary

Roll out the Business Logic Security Analyzer (BLSA) behind bl_security_analyzer for a closed beta.
Delivery tracker: #630266.

  • DRI: @mbenayoun
  • Team Slack channel: #g_ast-static-analysis (Code Security)

This is a closed beta: the flag is turned on for selected top-level groups only, not by percentage.

Prerequisites

  • All BLSA monolith MRs in #630266 merged (2026-10-05; follow-ups in #632169).
  • The bl_security flow is merged and deployed on the AI Gateway (ai-assist !7077 and its stack).
  • agentic_analyzer_security_ingestion is on for the beta projects (it's checked per project, see #606048).
  • Optional, to start scans from Duo Chat /flow: duo_chat_flow_commands is on for the beta users.
  • The group Owner turned on foundational flows, and the Business Logic flow, for the group.

What could go wrong?

  • Each scan runs a Duo flow, so it uses Duo credits for the group.
  • Findings land in the Vulnerability Report as SAST findings from the gitlab_bl_security_analyzer scanner.
  • Kill switch: turn the flag off. Scans stop starting; stored findings stay.

Rollout

Non-production

/chatops gitlab run feature set bl_security_analyzer true --dev --pre --staging --staging-ref
  • Staging: full-repo scan through the API and Duo Chat /flow, findings in the Vulnerability Report.

Production: beta groups only.

/chatops gitlab run feature set --group=<beta-group-path> bl_security_analyzer true
  • Internal group first: full-repo scan end to end.
  • Closed-beta customer groups: <group paths from Omer>.
  • Closed-beta customers: first scan checked with each.

Rollback

/chatops gitlab run feature set --group=<beta-group-path> bl_security_analyzer false
Edited by Meir Benayoun