Auvik

The Corma and Auvik integration keeps access to your network management platform in line with the IT team and MSP staff who run it. Auvik describes itself as cloud-based network management software, and IT pros and MSPs use it to manage their networks. Auvik Network Management is priced by billable network device rather than by user, so the governance question is less about seats than about who can reach your network and the credentials Auvik stores for it.

Key takeaways

• Auvik Network Management is priced on billable network devices, and its pricing page says all plans include unlimited users.
• Auvik ships with editable roles from Super Admin and Admin to Read-Only, Guest and API Access Only, assigned site by site.
• Each Auvik user can have one active API key, which inherits that user's permissions and may stop working if the user is disabled or removed.
• Auvik supports SAML 2.0 SSO without just-in-time provisioning, so every user must still be invited.

Why does access to Auvik reach so far?

Auvik holds the keys to your network. The credentials you share with Auvik, from SNMP strings and SSH logins to WMI administrator credentials and Meraki or Datto API credentials, are stored in Auvik's cloud with AES-256 encryption. Credentials added at the global level are inherited by every site and multi-site below it. That is why roles, more than seat counts, are what to review.

Users are invited by email, with a role chosen for each site, and deleting a user from the multi-site dashboard removes them from the account and from every site. Auvik Support will not delete user accounts for you: a user with the Super Admin role has to do it. Each API key is bound to the user who created it, and Auvik recommends dedicated service accounts for integrations, since disabling or removing the owner may stop the key from working. The User Activity log records changes to sites, devices and credentials, as well as user deletions.

How Corma governs Auvik

• Roles under review: Super Admin, Admin and technician roles go into automated access reviews, so each holder of elevated network access is confirmed.
• Leavers offboarded with a key check: a leaver workflow in the IT Workflow Builder asks a Super Admin to delete the person in Auvik, after checking whether an integration uses their API key.
• Service accounts with an owner: the dedicated service accounts Auvik recommends for integrations are non-human identities, so each one needs a named owner.
• Contract in view: the Auvik subscription and its renewal date sit in SaaS subscription management with the rest of your stack.

Frequently asked questions

Does Auvik support SSO and SCIM?

Auvik supports SAML 2.0 single sign-on, with setup guides for Azure AD, Okta and OneLogin, but SAML SSO is not enabled in the trial. Auvik documents no SCIM provisioning for Auvik user accounts, and there is no just-in-time provisioning, so users must be invited. Learn what single sign-on covers.

How does Corma connect to Auvik?

The Auvik API does not list users, roles or permissions, so Corma's browser-based agents handle user steps in the Auvik dashboard, in an isolated browser session with credentials taken from your password vault. See also how Corma covers network tools such as Cisco Meraki.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want to know who can still reach your network through Auvik? Book a Corma demo.