Security

Read-only, by design

Glass Aviary documents your Azure by reading it.

  • Read-only access

    Glass Aviary works with Azure's built-in Reader role. It checks its access before every scan, and it will not scan a subscription where it holds anything more.

  • Built to read, not write

    Glass Aviary's own code sends no write request to your Azure. The Terraform it generates is planned against your subscription and never applied.

  • No Azure credentials to hand over

    Glass Aviary connects as its own application. It never asks for a password, key or secret for your Azure.

  • Secret-shaped values removed before storage

    Before a scan's resource descriptions, tag values and role assignments are stored, values that match known secret patterns, such as keys, passwords and connection strings, are removed.

  • Withdraw access at any time

    Access is granted in your own Microsoft tenant, and you can withdraw it there without asking us.

An optional add-on, with its own consent

The principles above describe Glass Aviary on every plan. Enterprise customers can add Resilience and Remediation, the one part of Glass Aviary that makes changes in Azure. It stays off until you turn it on. It is a separate application that asks for its own write consent in your Microsoft tenant, apart from the Reader role your scans use, and you can withdraw that consent there at any time without asking us. Your scans keep the Reader role and nothing more.

Need more detail?

Detailed security information is available to customers and partners on request.

partner@glassaviary.com