You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Declaring an Azure VNet with subnets declared independently does not detect the security groups associations when they are configured as a separate resource, raising a False Positive for accurics.azure.NS.161
$ terrascan scan -t azure
results:
violations:
- rule_name: reme_noSecurityGroupAssociated
description: Ensure that Azure Virtual Network subnet is configured with a Network Security Group
rule_id: accurics.azure.NS.161
severity: MEDIUM
category: Network Security
resource_name: test-vnet
resource_type: ...
file: ../../modules/TEST/network.tf
line: 17
count:
low: 0
medium: 1
high: 0
total: 1
Expected behavior
It should not fail, i.e. it should detect the Security Group Association at azurerm_network_security_group.test-sg and azurerm_network_security_group.test-sg-resources.
The text was updated successfully, but these errors were encountered:
Yes, just confirmed this point today, we have exactly same issue if using separate ressource vnet/subnet.
And we doesn't plan to reconciliate vnet/subnet ressources, cause we will lost many features and flexibility.
Description
Declaring an Azure VNet with subnets declared independently does not detect the security groups associations when they are configured as a separate resource, raising a False Positive for
accurics.azure.NS.161
What I Did
Full Network description
Running Terrascan:
Expected behavior
It should not fail, i.e. it should detect the Security Group Association at
azurerm_network_security_group.test-sg
andazurerm_network_security_group.test-sg-resources
.The text was updated successfully, but these errors were encountered: