config-template-zap-simple.yaml

# This is a regular template file, which shows only the most important configuration entries.
#
# Author: Red Hat Product Security
#
# Additional configuration options are available, as shown in "config-template-long.yaml".
# All the values are optional (except `config.configVersion`): if a key is missing, it will mean either "disabled" or a sensible default will be selected

config:
  # WARNING: `configVersion` indicates the schema version of the config file.
  # This value tells RapiDAST what schema should be used to read this configuration.
  # Therefore you should only change it if you update the configuration to a newer schema
  # It is intended to keep backward compatibility (newer RapiDAST running an older config)
  configVersion: 6

# `application` contains data related to the application, not to the scans.
application:
  shortName: "MyApp-1.0"
  url: "<Mandatory. root URL of the application>"

# `general` is a section that will be applied to all scanners.
general:

  # See the config-template-long.yaml for more authentication options
  authentication:
    type: http_basic
    parameters:
      username: "user"
      password: "mypassw0rd"

# `scanners' is a section that configures scanning options
# See the config-template-long.yaml for more options
scanners:
  zap:
    apiScan:
      apis:
        apiUrl: "<URL to openAPI>"
        # alternative: apiFile: "<local path to openAPI file>"

    passiveScan:
      # optional list of passive rules to disable
      disabledRules: "2,10015,10024,10027,10054,10096,10109,10112"

    # Enable activeScan by uncommenting, once scans with the passiveScan only has run successfully
    # If no policy is chosen, a default ("API-scan-minimal") will be selected
    # The list of policies can be found in scanners/zap/policies/
    #activeScan:
    #  policy: "API-scan-minimal"

    miscOptions:
      # List (comma-separated string or list) of additional addons to install
      additionalAddons: "ascanrulesBeta"