azureenergylabelercli 2.2.5

A cli to help generate energy label for Azure tenant, subscriptions and resource groups.

A cli to help generate energy label for Azure tenant, subscriptions and resource groups.

• Documentation: https://azureenergylabelercli.readthedocs.org/en/latest

Energy Labels

Energy Labels table

label	high	medium	low
A =>	0	up to 10	up to 20
B ==>	up to 10	up to 20	up to 40
C ===>	up to 15	up to 30	up to 60
D ====>	up to 20	up to 40	up to 80
E =====>	up to 25	up to 50	up to 100

Arguments

CLI Arguments table

description	CLI argument	environment variable	example value
Tenant ID (required)	–tenant-id	AZURE_LABELER_TENANT_ID	00000000-0000-0000-0000-000000000000
Path to export the results	–export-path	AZURE_LABELER_EXPORT_PATH	/local/path or Storage Account Url with SAS token https://sa.blob.windows.net/container/?sas_token
Export only number of findings and energy label	–export-metrics	AZURE_LABELER_EXPORT_METRICS	false (default)
Export all findings information along with energy label	–export-all	AZURE_LABELER_EXPORT_ALL	true (default)
Regulatory frameworks to take into account	–frameworks	AZURE_LABELER_FRAMEWORKS	‘Microsoft cloud security benchmark,Azure CIS 1.1.0’
Explicit list of subscriptions to take into account	–allowed-subscription-ids	AZURE_LABELER_ALLOWED_SUBSCRIPTION_IDS	‘00000000-0000-0000-0000-000000000000,00000000-0000-0000-0000-000000000001’
Explicit list of subscriptions NOT to take into account	–denied-subscription-ids	AZURE_LABELER_DENIED_SUBSCRIPTION_IDS	‘00000000-0000-0000-0000-000000000000,00000000-0000-0000-0000-000000000001’
List of resource groups to exclude	–denied-resource-group-names	AZURE_LABELER_DENIED_RESOURCE_GROUP_NAMES	‘SBPP-WEU-AARC-01-RSG, SBPA-WEU-AARC-01-RSG’
Level of log printing	–log-level	AZURE_LABELER_LOG_LEVEL	info
Logging configuration	–log-config	AZURE_LABELER_LOG_CONFIG

Supported authentication types

Azure CLI

If you are running the Energy Labeler from your local machine, make sure the user you are authenticated as has the Security Reader permission or higher.

az login --tenant 00000000-0000-0000-0000-000000000000

Managed Identity

If you are running the azureenergylabeler container in Azure (on ACI, ACA, etc), this is safest and preferred authentication method. To make use of Managed Identity authentication for the Energy Labeler, make sure it is enabled on your instance (ACI, Function App, etc): .. code-block:

identity: {
    type: 'SystemAssigned'

}

Also make sure you have a role assignment to your instance, Security Reader is required. .. code-block:

@description('Security Reader role definition')
var roleDefinitionId = resourceId('microsoft.authorization/roleDefinitions', '39bc4728-0917-49c7-9d2c-d95423bc2eb4')

@description('Assign Security Reader role to the container so it can gather security compliance of the subscription/tenant')
resource securityReaderAssignment 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
  name: guid(name)
  scope: tenant()
  properties: {
    principalId: containergroup.identity.principalId
    roleDefinitionId: roleDefinitionId
  }
}

Service Principal credentials

If you are running the azureenergylabeler container outside Azure, you need to authenticate to Azure using Service Principal credentials. The Service Principal therefore must have Security Reader permission assigned to either at Tenant Level or to the subscriptions where Energy Label are calculated.

Service principal with secret

CLI Arguments table

variable name	value
AZURE_CLIENT_ID	id of an Azure Active Directory application
AZURE_TENANT_ID	id of the application’s Azure Active Directory tenant
AZURE_CLIENT_SECRET	one of the application’s client secrets

Service principal with certificate

CLI Arguments table

variable name	value
AZURE_CLIENT_ID	id of an Azure Active Directory application
AZURE_TENANT_ID	id of the application’s Azure Active Directory tenant
AZURE_CLIENT_CERTIFICATE_PATH	path to a PEM or PKCS12 certificate file including private key
AZURE_CLIENT_CERTIFICATE_PASSWORD	password of the certificate file, if any

Installation

Pipx

pipx install azureenergylabelercli
  installed package azureenergylabelercli 1.0.0, installed using Python 3.10.5
  These apps are now globally available
    - azure-energy-labeler
    - azure_energy_labeler_cli.py
done! ✨ 🌟 ✨

Examples

Calculate energy label for a tenant

azure-energy-labeler --tenant-id <TENANT_ID>

Calculate energy label for two subscriptions in a tenant

azure-energy-labeler --tenant-id <TENANT_ID> --allowed-subscription-ids 00000000-0000-0000-0000-000000000000,00000000-0000-0000-0000-000000000001

Calculate energy label for a tenant and export all findings to a local folder

azure-energy-labeler --tenant-id 2ba489e8-3466-4f52-a32d-263d28b832e1 --export-path /tmp/ --export-all

Calculate energy label for a tenant and export all findings to a Storage Account Blob Container

azure-energy-labeler --tenant-id 2ba489e8-3466-4f52-a32d-263d28b832e1 --export-path "https://sa.blob.windows.net/container/?sas_token" --export-all

Development Workflow

The workflow supports the following steps

• lint

• test

• build

• document

• upload

• graph

These actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices. Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.

The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that. It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the project

Once the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme. So for the initial delivery one would call

$ _tag –minor

which would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.

So the full workflow after git is initialized is:

• repeat as necessary (of course it could be test - code - lint :) )

  • code

  • lint

  • test

• commit and push

• develop more through the code-lint-test cycle

• tag (with the appropriate argument)

• build

• upload (if you want to host your package in pypi)

• document (of course this could be run at any point)

Important Information

This template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed. So when building a package out of this do not simple call

$ python setup.py sdist bdist_egg

as this will produce an unusable artifact with files missing. Instead use the provided build and upload scripts that create all the necessary files in the artifact.

Project Features

• TODO

History

0.0.1 (04-05-2022)

• First code creation

0.1.0 (27-06-2022)

• First release

1.0.0 (22-09-2022)

• Add support for environment variables as default argument value

• Arguments with array of values changed from a space separated list to a comma separated list

• CLI now uses the most recent version of the azureenergylabelerlib

1.0.1 (26-09-2022)

• Fixed a bug preventing collection of resource group findings

1.1.0 (04-10-2022)

• Updated dependency azurenergylabelerlib to version 2.0.0

2.0.0 (19-10-2022)

• Microsoft renamed “Azure Security Benchmark” to “Microsoft cloud security benchmark”, changing the interface

2.0.1 (20-10-2022)

• Fix broken dependecies

2.0.2 (08-03-2023)

• Bump template and dependencies.

2.0.3 (21-03-2023)

• Bumped library version which now filters subscriptions based on the tenant_id.

2.1.0 (15-05-2023)

• Added option to disable banner and spinner

• Improved filtering of findings

2.1.1 (28-06-2023)

• Updated library dependency

2.2.0 (22-09-2023)

• feat: updating azureenergylabelerlib to 3.3.0 to allow excluding resource groups

2.2.1 (22-09-2023)

• Fix: AZURE_LABELER_DENIED_RESOURCE_GROUP_NAMES changed to a string delimited list due to gitlab-ci not supporting variables of the type list.

2.2.2 (22-09-2023)

• fix: the list syntax in the readme file broke the release. It expects a comma after a quote.

2.2.3 (22-09-2023)

• fix: the list syntax in the readme file broke the release. It expects a comma after a quote.

2.2.4 (03-10-2023)

• fix: denied_resource_group_names was optional in azureenergylabelerlib 3.3.0. This broke the code if no value was given, therefore updating to 3.3.1.

2.2.5 (05-10-2023)

• feat: added validation for azure resource group names in azureenergylaberlib 3.3.2