Azure / Azure/bicep-registry-modules

[AVM Module Issue]: Disable weak cipher suites in API Management service module?

Open
#6,167 5 comments 1 reaction 2 assignees View on GitHub

@abhishekaryams is already working on this.

Since May 9, 2026.

Class: Resource Module :package: Language: Bicep :muscle: Status: In PR :point_right: Status: Module Orphaned :yellow_circle: Type: AVM :a: :v: :m:
Dominant language
Bicep
Stars
737
Forks
564
Avg merge
3d 15h
Merged PRs (30d)
30

Description

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Issue Type?

I'm not sure

### Module Name

avm/res/api-management/service

### (Optional) Module Version

_No response_

### Description

According to [ciphersuite.info](https://ciphersuite.info/), the following cipher suites are considered weak. Should they be disabled in [avm/res/api-management/service](https://github.com/Azure/bicep-registry-modules/blob/main/avm/res/api-management/service/main.bicep) by including them in the `customProperties` or would that have too big an impact on existing users of the module?

``` 'Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Ciphers.TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256': 'False'
'Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Ciphers.TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384': 'False'
'Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Ciphers.TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384': 'False'
'Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Ciphers.TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256': 'False'
'Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Ciphers.TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA': 'False'
'Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Ciphers.TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA': 'False'
'Microsoft.WindowsAzure.ApiManagement.Gateway.Security.Ciphers.TLS_RSA_WITH_AES_256_GCM_SHA384': 'False'
```

### (Optional) Correlation Id

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.