Benchmark: Expected Tag Values
Description
Resources should have specific values for some tags.
Usage
Install the mod:
mkdir dashboardscd dashboardspowerpipe mod initpowerpipe mod install github.com/turbot/steampipe-mod-azure-tags
Start the Powerpipe server:
steampipe service startpowerpipe server
Open http://localhost:9033 in your browser and select Expected Tag Values.
Run this benchmark in your terminal:
powerpipe benchmark run azure_tags.benchmark.expected_tag_values
Snapshot and share results via Turbot Pipes:
powerpipe benchmark run azure_tags.benchmark.expected_tag_values --share
Controls
- API Management services should have appropriate tag values
- App Service environments should have appropriate tag values
- App Service function apps should have appropriate tag values
- App Service plans should have appropriate tag values
- App Service web apps should have appropriate tag values
- Application security groups should have appropriate tag values
- Batch accounts should have appropriate tag values
- Compute availability sets should have appropriate tag values
- Compute disk encryption sets should have appropriate tag values
- Compute disks should have appropriate tag values
- Compute images should have appropriate tag values
- Compute snapshots should have appropriate tag values
- Compute virtual machines should have appropriate tag values
- Compute virtual machine scale sets should have appropriate tag values
- Container registries should have appropriate tag values
- CosmosDB accounts should have appropriate tag values
- CosmosDB mongo databases should have appropriate tag values
- CosmosDB sql databases should have appropriate tag values
- Data factories should have appropriate tag values
- Data lake analytics accounts should have appropriate tag values
- Data lake stores should have appropriate tag values
- Event Hub namespaces should have appropriate tag values
- ExpressRoute circuits should have appropriate tag values
- Firewalls should have appropriate tag values
- IoT Hubs should have appropriate tag values
- Key vault deleted vaults should have appropriate tag values
- Key vaults should have appropriate tag values
- Key vault keys should have appropriate tag values
- Key vault managed hardware security modules should have appropriate tag values
- Key vault secrets should have appropriate tag values
- Kubernetes clusters should have appropriate tag values
- Load balancers should have appropriate tag values
- Log alerts should have appropriate tag values
- Log profiles should have appropriate tag values
- Logic app workflows should have appropriate tag values
- MariaDB servers should have appropriate tag values
- Microsoft SQL elasticpools should have appropriate tag values
- Microsoft SQL managed instances should have appropriate tag values
- MySQL servers should have appropriate tag values
- Network interfaces should have appropriate tag values
- Network security groups should have appropriate tag values
- Network watchers should have appropriate tag values
- Network watcher flow logs should have appropriate tag values
- PostgreSQL servers should have appropriate tag values
- Public IPs should have appropriate tag values
- Recovery services vaults should have appropriate tag values
- Redis caches should have appropriate tag values
- Resource groups should have appropriate tag values
- Route tables should have appropriate tag values
- Search services should have appropriate tag values
- Service Bus namespaces should have appropriate tag values
- SQL databases should have appropriate tag values
- SQL servers should have appropriate tag values
- Storage accounts should have appropriate tag values
- Stream Analytics jobs should have appropriate tag values
- Virtual networks should have appropriate tag values
- Virtual network gateways should have appropriate tag values