OpenParable
Skip to content
← Back to skills

Cis Azure Compute 2.10

DevOps & Security
cis-azure-compute-2.10

Cis Azure Compute 2.10 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure App Service Environment has TLS cipher suite ordering configured

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/Microsoft_Azure/CIS_Microsoft_Azure_Compute_Services_Benchmark_v2.0.0/cis-azure-compute-2.10/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-azure-compute-2-10, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Ensure App Service Environment has TLS cipher suite ordering configured

Description

App Service Environment supports changing the cipher suite from the default. The default set of ciphers is the same set that is used in the multi-tenant App Service. Changing the cipher suite is only possible with App Service Environment, the single-tenant offering, not the multi-tenant offering, because changing it affects the entire App Service deployment.

There are two cipher suites that are required for an App Service Environment: TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 and TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256. Additionally, you should include the following cipher suites, which are required for TLS 1.3: TLS_AES_256_GCM_SHA384 and TLS_AES_128_GCM_SHA256.

Rationale

Configuring your App Service Environment to use only the ciphers it requires helps to keep the environment secure.

Impact

If incorrect values are set for the cipher suite that SChannel cannot understand, all TLS communication to your server might stop functioning.

Audit Procedure

Using Azure Portal

  1. Go to Resource Explorer.
  2. Locate an App Service Environment from the left pane.
  3. Ensure the clusterSettings attribute includes:
{
  "name": "FrontEndSSLCipherSuiteOrder",
  "value": "TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"
}
  1. Repeat steps 1-3 for each App Service Environment.

Using Azure CLI

Run the following command to list App Service Environments:

az appservice ase list

For each App Service Environment, ensure that clusterSettings includes:

{
  "name": "FrontEndSSLCipherSuiteOrder",
  "value": "TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"
}

Expected Result

The clusterSettings should include a FrontEndSSLCipherSuiteOrder entry with the appropriate strong cipher suites listed.

Remediation

Using Azure Portal

  1. Go to Resource Explorer.
  2. Locate an App Service Environment from the left pane.
  3. In the right pane, click Read/Write to allow editing.
  4. Click Edit to edit the resource.
  5. Update the clusterSettings attribute to include:
{
  "name": "FrontEndSSLCipherSuiteOrder",
  "value": "TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"
}
  1. Click PUT to commit the change.
  2. Repeat steps 1-7 for each App Service Environment requiring remediation.

Default Value

TLS cipher suite ordering is not configured by default.

References

  1. https://learn.microsoft.com/en-us/azure/app-service/environment/app-service-app-service-environment-custom-settings
  2. https://learn.microsoft.com/en-us/cli/azure/appservice/ase

Profile

Level 1 | Automated