AVD-AZU-0012 being reported since trivy-checks release v1.12.0?

[ricardo-kh]

Description

Some of our internal pipelines just started failing with the following message:

Report Summary

┌────────┬───────────┬───────────────────┐
│ Target │   Type    │ Misconfigurations │
├────────┼───────────┼───────────────────┤
│        │ terraform │         1         │
├────────┼───────────┼───────────────────┤
│ .      │ terraform │         0         │
└────────┴───────────┴───────────────────┘
Legend:
- '-': Not scanned
- '0': Clean (no security findings detected)


 (terraform)
============
Tests: 1 (SUCCESSES: 0, FAILURES: 1)
Failures: 1 (HIGH: 0, CRITICAL: 1)

AVD-AZU-0012 (CRITICAL): No network rules defined and default action allows access.
════════════════════════════════════════
The default_action for network rules should come into effect when no other rules are matched.
The default action should be set to Deny.


See https://avd.aquasec.com/misconfig/avd-azu-0012

But we don't use Azure.

Initially we were still on trivy 0.64.1, but updating to 0.67.0 did not solve the issue.

I have the feeling it was introduced with:

https://github.com/aquasecurity/trivy-checks/releases/tag/v1.12.0

Which contains:

feat: add check for default network rules in AVD-AZU-0012 in #284.

And was released a couple of hours ago.

I actually wanted to open an issue here: https://github.com/aquasecurity/trivy-checks/issues but couldn't. Therefore opening the issue for this repository instead.

Desired Behavior

Don't fail because of AVD-AZU-0012 while no Azure related resources are being used.

Actual Behavior

Failing because of AVD-AZU-0012 while no Azure related resources are being used.

Reproduction Steps

This is how we run `trivy`:


trivy config --exit-code 1 --timeout 15m --severity="CRITICAL,HIGH" --misconfig-scanners terraform .

### Target

Filesystem

### Scanner

Misconfiguration

### Output Format

None

### Mode

Standalone

### Debug Output

```bash
Will try to provide this later on.

Operating System

google/cloud-sdk Docker image

Version

0.67.0

Checklist

• Run trivy clean --all
• Read the troubleshooting

[ricardo-kh]

I see it has already been reported here: #9619