Scanners FAQ

Last updated: Oct 21, 2026

This section answers common questions about the standalone scanners.

General information

Where can I find the latest information about the tools?

The updated information about the Fluid Attacks scanners is in the Use the CLI section of this documentation. The documentation of the App Defense Alliance about the tool is not up to date.

Do I need to create a Dockerfile to use the tools?

No. You only need to download the Docker image.

Running the scanners

How do I run the scanners?

See Run with Docker containers and Integrate scanners into CI/CD pipelines.

What can I do with the mounting "Operation not permitted" error?

If this message appears at the end of the error log:

error: mounting /proc: Operation not permitted

Run the scan again with the --privileged flag:

docker run --privileged -v /your/local/dir:/working-dir fluidattacks/sast:latest sast scan /working-dir/config.yaml

What can I do with the invalid argument error?

If the error message at the end of the error log is this one:

[ERROR] Enter a valid argument,the argument types are the path to a .yaml configuration file or the path to a directory.

This message means that the path to the config.yaml file or to the folder to scan is incorrect. It can also mean that you try to access a local path from inside the container runtime. Thus, make sure that the path exists, and that you mount the volume correctly inside the container with the related files.

Errors during execution

Why does the scanner report my APK files under CWE-377 as unverifiable?

This means that you run a SAST scanner on APK files. Only the MAST scanner can analyze APK files. To remove those reports, add the exclude key to the "sast" section of the configuration, as follows:

sast:  include:    - .  exclude:    - glob(**/*.apk)

What can I do with the "File too large" error?

If you see this message frequently:

[WARNING] File too large

This message means that the tool ignores large files to prevent memory problems.

To remove this limit, use the "file size limit" key.

If you remove the limit and get memory errors, divide the scanner runs. For example, scan only some folders in each run.

Fluid Attacks continues to make this behavior better. Thus, this strategy can become unnecessary in the future.

What can I do if the scans are slow?

If your scan is slower than normal, do these checks:

• Check the dependency folders: Do not include dependency folders such as node_modules, dist, vendor, and their equivalents in the SAST scan.
• Use the recursion limit key: Use the "recursion limit" key to limit the search depth in a single file. The recommended value is 1000.

Why am I experiencing network errors during execution?

Network errors usually occur when the scanners run in an environment with restricted Internet access. For all the scanners to work correctly, especially the SCA scanner, run the analysis without these restrictions.

If you cannot remove the restrictions, your network must at least allow inbound and outbound communication with AWS. Some scanners use data from AWS services (public S3 buckets).

Also, the scanners can connect to external services such as Datadog, which Fluid Attacks uses for error tracking and debugging. Fluid Attacks does not keep sensitive information in those services. To disable all the execution traceability, add this setting to your YAML configuration file: tracing_opt_out: True

If you get a different error, send an email to [email protected].