CI Gate executions

Last updated: Nov 12, 2026


Fluid Attacks' CI Gate supports the DevSecOps methodology in your projects. This tool is a security gate in your continuous integration and continuous deployment (CI/CD) environments. It stops vulnerable code before it gets to production.

CI Gate monitors your software versions. If it detects vulnerabilities that are not remediated or accepted, it automatically breaks the build. Thus, your team must remediate them, and your security standards stay high.

You can configure the rules to break the build at the organization and group levels, in the Policies section of the Fluid Attacks platform. You can see the details of each CI Gate execution in the DevSecOps section. This page describes this section.

DevSecOps table

The DevSecOps section of your group has a table with the recent executions of the security checks of Fluid Attacks. The Security check column shows the check of each execution: CI Gate, Peer Reviewer Assistant, or Scanner. For the scanner runs, read Scanner executions.

At the top, a summary shows the CI Gate executions and the Peer Reviewer Assistant reviews of the last 30 days, with their results. To see more details about an execution, click its row.

Know the DevSecOps table on the Fluid Attacks platform

For a CI Gate execution, the table columns show this data:

  • Identifier: Run and the first 7 characters of the unique alphanumeric identifier of the CI Gate run
  • Security check: CI Gate
  • Result: One of these values:
    • Passed: CI Gate found no unmanaged vulnerabilities.
    • Passed (accepted risk): CI Gate found vulnerabilities, but all of them obey your policies.
    • Failed: CI Gate found one or more unmanaged vulnerabilities.
    • Incomplete: The run stopped before it finished, so CI Gate did not evaluate the vulnerabilities.
  • Vulnerabilities: The total number of vulnerabilities that CI Gate found, with the number of unmanaged and allowed vulnerabilities. Allowed vulnerabilities obey your policies. A vulnerability is unmanaged when all these conditions are true at the same time:
    • It is open (not fixed or accepted as a risk).
    • Its severity score is equal to or more than the configured severity threshold.
    • The number of days since its report is equal to or more than the configured grace period.
    • Its age is less than the configured days to technical debt limit (if there is a limit).
  • Git repository: The nickname of the Git repository with the changes that CI Gate scanned
  • Executed day: The date and time that CI Gate ran in your pipeline

Filter the DevSecOps table

Click the filters button to see the options to limit the information in the table. To see only the CI Gate executions, select CI Gate in Security check. These filters apply to the CI Gate executions:

  • Result
  • Technique: The security testing techniques, in two groups: Static and Dynamic
  • Strictness:
    • Strict: CI Gate breaks the build if it detects unmanaged vulnerabilities. This prevents deployment to production.
    • Tolerant: CI Gate only shows warnings for unfixed vulnerabilities, and the build can go to production.
  • Breaks build: Only for CI Gate. Yes - Breaks the build or No - Doesn't break the build
  • Git repository
  • Executed day
Filter the DevSecOps table on the Fluid Attacks platform
Choose filters in DevSecOps
Apply filter in DevSecOps on the Fluid Attacks platform
Apply filter

Search the DevSecOps table

Type in the search bar of the table to see only the rows that contain your search term. You can search by repository, branch, pull request, or identifier.

Search the DevSecOps table on the Fluid Attacks platform

Download a report of the CI Gate executions

Click the Generate report button. After a short time, the report is available in Downloads. The report is a ZIP file with two comma-separated values (CSV) files:

  • ci-gate-executions.csv: The CI Gate executions
  • peer-reviewer-executions.csv: The reviews of the Peer Reviewer Assistant

The report does not include the scanner runs. The download link expires after 7 days.

Download DevSecOps table on the Fluid Attacks platform
Generate report button
Confirm DevSecOps report delivery on the Fluid Attacks platform
Success notification

View CI Gate execution details

In the DevSecOps section, to see more details about a CI Gate execution, click its row.

Select a CI Gate execution on the Fluid Attacks platform

A page opens with the title CI Gate | Run and the run identifier. This page has two tabs: Vulnerabilities and Execution log. To go back to the table, click the back arrow.

Vulnerabilities

At the top, the Vulnerabilities tab shows four cards:

  • Execution: The result of the run, Strictness, Executed date, and Identifier. Use the copy button to copy the full identifier.
  • Scope: Git repository and Technique (SAST, DAST, or All (Static - Dynamic)).
  • Security policies: The value of three policies that the execution applied.
  • Vulnerabilities: The number of vulnerabilities that the execution found. Gate divides them into two groups:
    • Unmanaged: Open vulnerabilities that break the build under your policies.
    • Allowed: Vulnerabilities that your policies tolerate. They do not break the build.
View Agent execution policy details on the Fluid Attacks platform

These are short definitions of the three policies:

  • CVSS threshold: The minimum CVSS score that an unfixed vulnerability must have to break the build
  • Grace period: The number of days during which newly discovered vulnerabilities do not break the build
  • Days to technical debt: The number of days until vulnerabilities become technical debt, which does not break the build

Below the cards, a table shows information about all the vulnerabilities that CI Gate identified in its execution.

See Agent execution summary on the Fluid Attacks platform

The table has these columns:

  • Weakness: The weakness of the vulnerability, with a link to its description
  • Vulnerability: The file path where Fluid Attacks found this vulnerability
  • Specific: The exact lines of code, inputs (for example, password fields) or ports where Fluid Attacks found the vulnerability
  • Status: Open, Closed, or Accepted
  • Gate: Unmanaged or Allowed
  • Severity (v4.0): The CVSS v4.0 score
  • Technique: The security testing technique that detected the vulnerability
  • Exploit maturity: The probability that the vulnerability causes a successful attack, as the CVSS v4.0 measures it

You can apply filters to limit the information that the table shows. With filters, you can analyze only the data that you select.

Filter execution summary table on the Fluid Attacks platform

You can also type a search term in the search box. The table then shows only the rows whose content matches your search.

Search the execution summary table on the Fluid Attacks platform

If the execution found no vulnerabilities, the tab shows No vulnerabilities found. If the run stopped before it finished, the tab shows The scan could not complete. In this case, find the cause in the execution log, and run the pipeline again.

Execution log

The content of the CI Gate execution log is not always easy to read. This section gives important information to help you get the most from the log.

These are the primary elements of the log:

  • Arguments: The content of the log depends on the parameters or arguments of the agent execution. As an example, the screenshots below show an execution with the argument --strict.

    View arguments in execution log on the Fluid Attacks platform
  • Report body: The primary part of the report is the detailed information about the detected vulnerabilities. This is a short explanation of the content shown for each vulnerability:

    • title: The category that best describes the vulnerability, following Fluid Attacks' own classification
    • url: The vulnerability URL on the platform
    • state: The condition of the group for the weakness. It is vulnerable if the weakness is present
    • exploit: From the CVSS, the probability of exploitation, from the current exploitation techniques, the availability of exploit code, and real exploitation "in the wild"
    • severity: The severity score of the weakness (from 0.1 to 10.0), with the CVSS
    • vulnerable: The total number of unfixed vulnerabilities
    • locations: The identified vulnerabilities, with this information:
      • type: Shows if Fluid Attacks found the vulnerability in the source code (static) or with attacks on the running application (dynamic)
      • technique: The security testing technique that detected the vulnerability
      • where: The file path where Fluid Attacks found this vulnerability
      • specific: The lines of code, inputs (for example, password fields) or ports where Fluid Attacks found the vulnerability
      • state: Shows that the lines of code, inputs or ports are vulnerable (the vulnerability is present)
      • severity: The severity score of this vulnerability, with the CVSS
      • compliance: Shows if the vulnerability breaks the build
    View Agent execution log on the Fluid Attacks platform
  • Summary: The report ends with a summary. The summary shows these items:

    • The total number of unfixed vulnerabilities
    • The CI Gate execution time
    • The policies that CI Gate verified
    • The name and age of the vulnerability type
    • If the build broke or passed
View execution log summary on the Fluid Attacks platform

On this page