consul/.release/security-scan.hcl
Deniz Onur Duzgun 1dfc265abe
ci(security-scanner): add support for Red Hat UBI images and fix typo (#21912)
* ci(security-scanner): add support for Red Hat UBI images and fix typo

* hclfmt

* clean-up comments

Co-authored-by: Kent Gruber <kent@hashicorp.com>

---------

Co-authored-by: Kent Gruber <kent@hashicorp.com>
2024-11-04 14:52:01 -05:00

93 lines
2.6 KiB
HCL

# Copyright (c) HashiCorp, Inc.
# SPDX-License-Identifier: BUSL-1.1
# These scan results are run as part of CRT workflows.
# Un-triaged results will block release. See `security-scanner` docs for more
# information on how to add `triage` config to unblock releases for specific results.
# In most cases, we should not need to disable the entire scanner to unblock a release.
# To run manually, install scanner and then from the repository root run
# `SECURITY_SCANNER_CONFIG_FILE=.release/security-scan.hcl scan ...`
# To scan a local container, add `local_daemon = true` to the `container` block below.
# See `security-scanner` docs or run with `--help` for scan target syntax.
container {
dependencies = true
osv = true
secrets {
matchers {
// Use most of default list, minus Vault (`hashicorp`), which has experienced false positives.
// See https://github.com/hashicorp/security-scanner/blob/v0.0.2/pkg/scanner/secrets.go#L130C2-L130C2
known = [
// "hashicorp",
"aws",
"google",
"slack",
"github",
"azure",
"npm",
]
}
}
# Triage items that are _safe_ to ignore here. Note that this list should be
# periodically cleaned up to remove items that are no longer found by the scanner.
triage {
suppress {
vulnerabilities = [
"CVE-2024-8096", # curl@8.9.1-r2,
"CVE-2024-9143", # openssl@3.3.2-r0,
]
paths = [
"internal/tools/proto-gen-rpc-glue/e2e/consul/*",
"test/integration/connect/envoy/test-sds-server/*",
"test/integration/consul-container/*",
"testing/deployer/*",
"test-integ/*",
]
}
}
}
binary {
go_modules = true
osv = true
go_stdlib = true
# We can't enable npm for binary targets today because we don't yet embed the relevant file
# (yarn.lock) in the Consul binary. This is something we may investigate in the future.
secrets {
matchers {
// Use most of default list, minus Vault (`hashicorp`), which has experienced false positives.
// See https://github.com/hashicorp/security-scanner/blob/v0.0.2/pkg/scanner/secrets.go#L130C2-L130C2
known = [
// "hashicorp",
"aws",
"google",
"slack",
"github",
"azure",
"npm",
]
}
}
# Triage items that are _safe_ to ignore here. Note that this list should be
# periodically cleaned up to remove items that are no longer found by the scanner.
triage {
suppress {
vulnerabilities = [
]
paths = [
"internal/tools/proto-gen-rpc-glue/e2e/consul/*",
"test/integration/connect/envoy/test-sds-server/*",
"test/integration/consul-container/*",
"testing/deployer/*",
"test-integ/*",
]
}
}
}