Azure / Azure/AzureStack-QuickStart-Templates
sql-2016-alwayson - Allow all NSG Rule
- Dominant language
- PowerShell
- Stars
- 587
- Forks
- 741
- PR merge metrics
- No merged PRs in 30d
Description
@JeffGoldner
This resource is added to the NSG which opens up everything.
IMO this does not set a good example, rather leave it default and state something about NSG rules in the readme?
"resources": [
{
"name": "[variables('nsgName')]",
"location": "[resourceGroup().location]",
"type": "Microsoft.Network/networkSecurityGroups",
"apiVersion": "2015-06-15",
"properties": {
"securityRules": [
{
"name": "rule1",
"properties": {
"protocol": "*",
"sourcePortRange": "*",
"destinationPortRange": "*",
"sourceAddressPrefix": "*",
"destinationAddressPrefix": "*",
"access": "Allow",
"priority": 101,
"direction": "Inbound"
}
}
]
}
},
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the sql-2016-alwayson template and inspect the Microsoft.Network/networkSecurityGroups resource shown in the issue. Determine whether the permissive inbound rule should be removed or documented as a required customization, then validate the resulting ARM template and its NSG behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100