Security Review Flow
- Tier: Ultimate
- Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
- Status: Beta
Security Review Flow detects business logic vulnerabilities in merge requests. Unlike static analysis tools that scan for known patterns, Security Review Flow reasons about the intent of your code. It identifies vulnerabilities that emerge from incorrect assumptions about authorization, data exposure, and control flow.
Security Review Flow is a foundational flow built on the GitLab Duo Agent Platform. It works alongside GitLab Duo Code Review and posts findings as threaded diff comments, each with a CWE classification, severity rating, explanation, and where possible, an inline suggested fix you can apply with one action.
Security Review Flow results are AI-generated and are advisory input, not an authoritative or complete security assessment. A review that reports no findings is not proof that a merge request is secure, and findings can include false positives that need human judgment. For more information, see Known limitations.
Use Security Review Flow when you need help with:
- Access control review: Identify missing or misconfigured authorization checks on state-changing operations.
- Authorization gap detection: Surface broken object-level and function-level authorization issues.
- Business logic analysis: Detect flaws in application workflows that could be exploited, such as race conditions in financial or stateful operations.
- Information disclosure: Identify code paths that can leak sensitive data to unauthorized callers.
- Mass assignment risk: Flag endpoints or models that can expose unintended fields to user input.
To scan the whole repository or track findings as vulnerabilities, see business logic scanning.
Prerequisites
To use Security Review Flow:
- Have the Developer, Maintainer, or Owner role for the project.
- Turn on Foundational flows and Security Review for the top-level group.
- Turn on GitLab Duo for the group or instance.
- If you do not have GitLab Duo Pro or Enterprise, turn on GitLab Duo Core for the top-level group or instance.
- For GitLab Self-Managed, configure GitLab Duo for the instance.
- In GitLab 18.8 and later, turn on Agent Platform for the top-level group. In GitLab 18.7 and earlier, turn on beta and experimental features.
Cost
Security Review Flow uses GitLab Credits each time it performs a review. Credit usage scales with diff complexity and the model you select.
The following estimates apply to the default model:
| Review complexity | Approximate LLM calls | Estimated credits |
|---|---|---|
| Small diff or a few changed files | ~16 | ~8 |
| Standard feature branch | ~28 | ~14 |
| Large or logic-heavy multi-file change | ~40 | ~20 |
By default, you start reviews manually. This lets you assess typical credit usage in your codebase before you run reviews automatically.
Use Security Review Flow
Request a review
You can request a review at any time after a merge request is created. When you request a review, the flow analyzes the merge request diff and its surrounding context.
The Duo Security Review service account is created for your top-level group when the Security Review flow is
turned on, and is available to all projects and subgroups within it. Each service account name includes the
associated top-level group, for example duo-security-review-gitlab-org.
To request a review:
- In the left sidebar, select Search or go to and find your project.
- Select Code > Merge requests and open your merge request.
- In the Reviewers section of the right sidebar, select Edit.
- In the search box, enter
Duo Security Reviewand select the account from the list.
When the review is complete, the flow posts an internal note. The note summarizes any findings and the review scope. If the review produces no findings, the flow states this in the internal note.
For each finding, the flow opens a diff thread at the relevant line. If you reply to a thread (for example, to accept the risk or disagree with the assessment), the flow reads your reply and responds accordingly. On public projects, findings are posted in the internal note only, with no inline diff comments. Posting findings privately avoids exposing security details.
The flow sets the reviewer state based on the severity of findings. The flow never sets the Approve state, even when it finds no issues:
| Severity | Reviewer state |
|---|---|
critical or high |
Request changes |
medium or low |
Comment |
| None | Comment |
Run reviews automatically
To automatically assign Security Review Flow to merge requests in a project, apply the Security Review profile to the project. Security Review Flow must also be turned on for the top-level group, as described in Prerequisites.
The Security Review profile is a business logic profile. It runs Security Review Flow instead of the business logic scan, so findings are posted only as review threads on the merge request. They are not added to the Vulnerability Report or the merge request security widget. If both business logic profiles are applied to a project, the profile that was created first in the group applies.
If Security Review Flow is turned off for the top-level group, the business logic scan runs as usual instead.
With the profile applied, the flow is assigned as a reviewer and starts a review in these cases:
- A merge request is created and is not a draft.
- A draft merge request is marked as ready.
Merge requests that are already open when you apply the profile are not reviewed automatically, and the business logic scan does not run for them. An open draft is reviewed when it’s marked as ready. To review other open merge requests, assign the flow as a reviewer.
The flow does not review again when you push new commits. To request another review, reassign the flow as a reviewer.
Automatic reviews use the merge request author’s GitLab Credits, even when someone else marks the merge request as ready. Automatic reviews do not run for these merge requests:
- Merge requests from forks
- Merge requests created by bots or service accounts
- Merge requests whose author cannot run the flow in the project
Respond to a finding
Mention the flow in a thread to ask clarifying questions about a finding, discuss remediation approaches, or flag a finding as a false positive. The flow does not perform a full re-review when mentioned.
To respond to a finding:
- In the left sidebar, select Search or go to and find your project.
- Select Code > Merge requests and open your merge request.
- In any comment thread, enter
@duo-security-reviewand select Duo Security Review from the list. - Add your message and select Comment.
Security Review Flow reads the thread context and replies directly.
Review a finding
Security Review Flow focuses on logic-level vulnerabilities frequently missed by static analyzers. Each finding is posted as a diff thread on the changed code. Each thread includes:
- The vulnerability type (CWE) with a link to the MITRE definition.
- A severity rating:
critical,high,medium, orlow. - A tier classification: Tier 1 (Exploitable), Tier 2 (Logic Flaw), or Tier 3 (Design Issue).
- An explanation of the logic flaw.
- A suggested fix, where possible.
Findings are not tracked in the Vulnerability Report and do not count toward merge request approval policies. They complement, but do not replace, static analysis (SAST) findings. To track findings as vulnerabilities, use business logic scanning.
The following CWE classifications can appear in findings:
| CWE | Description |
|---|---|
| CWE-639 | Authorization bypass through user-controlled key (BOLA / IDOR) |
| CWE-862 | Missing authorization |
| CWE-284 | Improper access control |
| CWE-200 | Exposure of sensitive information |
| CWE-840 | Business logic errors |
| CWE-915 | Improperly controlled modification of dynamically-determined object attributes (mass assignment) |
| CWE-362 | Race conditions and time-of-check / time-of-use (TOCTOU) |
Resolve a finding
To resolve a finding:
- To apply the fix, select Apply suggestion. To commit the suggestion to a new branch instead, select the dropdown list next to Apply suggestion.
- To dismiss the finding, select Resolve thread if you reviewed the finding and determined it is a false positive or accepted risk.
- To track the vulnerability for future remediation, use the standard GitLab thread actions to create an issue from the finding.
- To rate the finding’s usefulness, select thumbs up or thumbs down. This feedback helps improve the model. You can also share detailed feedback in the feedback issue.
To request another review after you resolve the findings, reassign the flow as a reviewer. The flow analyzes the updated diff and performs an action depending on the state of the finding:
- Resolved findings: The flow confirms the fix and resolves the original thread.
- Incorrect or incomplete fixes: The flow identifies any additional required changes in the original thread.
- Unaddressed findings: The original thread remains open with no additional comment.
- New findings: The flow detects any new vulnerabilities introduced by the fix and creates new comment threads for them.
Known limitations
Understand the following limitations before you rely on Security Review Flow output.
- Findings are advisory, not a coverage guarantee. Security Review Flow results are AI-generated. The flow might not surface every vulnerability in a change: its analysis works within a bounded search and read budget, so very large files or diffs might not be fully reviewed. A review that reports no findings is not proof that the merge request is secure.
- Findings can include false positives. Treat findings as input that needs human judgment, not as a final verdict.
- Security Review Flow complements other tooling. It does not replace human security review or other GitLab security tools, such as SAST and GitLab Advanced SAST.
Troubleshooting
When you use Security Review Flow, you might encounter the following issues.
The flow is not available to assign
The Duo Security Review service account is created for your top-level group when the
Security Review flow is turned on. The service account name includes the top-level group
name, for example duo-security-review-gitlab-org.
Confirm the status of the Security Review flow.
The flow does not provide findings
Confirm you meet all prerequisites, then check that the flow was correctly assigned.
- Verify that you mentioned the Duo Security Review account (its username begins with
@duo-security-review-). - Verify Allow foundational flows and Code Review settings are turned on for the top-level group.
- For GitLab Self-Managed, verify your instance is configured for GitLab Duo.
The flow does not review every merge request
Unless the project has the Security Review profile applied, you must manually assign the flow to a merge request. Even with the profile applied, some merge requests are not reviewed automatically. For more information, see run reviews automatically. If you assigned the flow but received no findings, see The flow does not provide findings.
When the flow reviews a merge request, a report with no findings typically means:
- No security issues were detected: The code logic was analyzed, and no vulnerabilities were identified.
- No security-relevant logic: The change does not contain code that impacts security (for example, documentation-only updates).
Note on large changes: For large merge requests, the flow operates within a bounded search and read budget. In these cases, the flow might report no findings or still output findings but fail to cover the full merge request, meaning important vulnerabilities could be missed. A completed review is not a guarantee of full coverage. For more information, see Known limitations.
Suggested changes do not apply cleanly
Suggestions are generated against the diff at review time. If you pushed new commits after the review, line numbers might have shifted. Request a new review to get updated suggestions against the current diff.
I received an error about GitLab Credits
Your instance or group might have exhausted the GitLab Credits for the current billing period. Contact your administrator to purchase additional credits, or wait for the credits to reset at the start of the next billing period.