config

Application security scanning preferences are managed via a centralized configuration file. You can define default scan scope, depth, severity filters, and excluded paths in `.appsec/config.yaml` to ensure consistent settings across projects.

To set default AppSec scan scope and exclude directories, configure the persistent settings in `.appsec/config.yaml`. You can specify a default scope like 'changed' files and define excluded paths such as the 'vendor' directory for automated application.

Centralized AppSec configuration streamlines security tool preferences and thresholds into a single `.appsec/config.yaml` file. You need it to ensure automated, customized, and consistent application security scanning when specific flags are not provided.

Yes, you can configure accepted risks and scanner paths for application security tools. The configuration file supports defining scanner paths, accepted risks, severity filters, and hooks that integrate with other AppSec skills automatically.

The best way to handle persistent security thresholds is using a centralized configuration file. Defining settings like default scope, depth, and severity filters in `.appsec/config.yaml` ensures security tools adhere to predefined standards automatically.