|
1 | 1 | ---
|
2 |
| -reviewed: 2023-11-13 |
| 2 | +reviewed: 2024-05-07 |
3 | 3 | severity: Critical
|
4 | 4 | pillar: Security
|
5 |
| -category: Infrastructure provisioning |
| 5 | +category: SE:02 Secured development lifecycle |
6 | 6 | resource: Deployment
|
7 | 7 | online version: https://azure.github.io/PSRule.Rules.Azure/en/rules/Azure.Deployment.SecureParameter/
|
8 | 8 | ---
|
@@ -86,18 +86,23 @@ This rule uses a heuristics to determine if a parameter should use a secure type
|
86 | 86 | - Parameters with the type `int` or `bool` are ignored regardless of how they are named.
|
87 | 87 | - Any parameter with a name containing `password`, `secret`, or `token` will be considered sensitive.
|
88 | 88 | - Except parameter names containing any of the following:
|
89 |
| - `passwordlength`, `secretname`, `secreturl`, `secreturi`, `secretrotation`, `secretinterval`, `secretprovider`, |
90 |
| - `secretsprovider`, `secretref`, `secretid`, `disablepassword`, `sync*passwords`, or `tokenname`. |
| 89 | + `length`, `interval`, `secretname`, `secreturl`, `secreturi`, `secrettype`, `secretrotation`, |
| 90 | + `secretprovider`, `secretsprovider`, `secretref`, `secretid`, `disablepassword`, `sync*passwords`, |
| 91 | + `tokenname`, `tokentype`, `keyvaultpath`, `keyvaultname`, or `keyvaulturi`. |
91 | 92 | - Any parameter with a name ending in `key` or `keys` will be considered sensitive.
|
92 | 93 | - Except parameter names ending in `publickey` or `publickeys`.
|
93 | 94 |
|
| 95 | +### Rule configuration |
| 96 | + |
| 97 | +<!-- module:config rule AZURE_DEPLOYMENT_NONSENSITIVE_PARAMETER_NAMES --> |
| 98 | + |
94 | 99 | If you identify a parameter that is _not sensitive_, and is incorrectly flagged by this rule, you can override the rule.
|
95 | 100 | To override this rule:
|
96 | 101 |
|
97 | 102 | - Set the `AZURE_DEPLOYMENT_NONSENSITIVE_PARAMETER_NAMES` configuration value to identify parameters that are not sensitive.
|
98 | 103 |
|
99 | 104 | ## LINKS
|
100 | 105 |
|
101 |
| -- [Infrastructure provisioning considerations in Azure](https://learn.microsoft.com/azure/architecture/framework/security/deploy-infrastructure) |
| 106 | +- [SE:02 Secured development lifecycle](https://learn.microsoft.com/azure/well-architected/security/secure-development-lifecycle) |
102 | 107 | - [Use Azure Key Vault to pass secure parameter value during Bicep deployment](https://learn.microsoft.com/azure/azure-resource-manager/bicep/key-vault-parameter)
|
103 | 108 | - [Integrate Azure Key Vault in your ARM template deployment](https://learn.microsoft.com/azure/azure-resource-manager/templates/template-tutorial-use-key-vault#edit-the-parameters-file)
|
0 commit comments