Credentials
The company vault stores the passwords, keys and tokens ARGUNIS uses for monitoring; values stay sealed and are never shown again.
The company vault stores every credential ARGUNIS needs for monitoring: SSH, Windows, SNMP, databases, API tokens and more. Every password comes from here. Values stay sealed and are never shown again; when monitoring is assigned, ARGUNIS sends the sealed credential to the component that runs it (a probe, an agent or the ARGUNIS cloud).
Before you begin
The vault is managed by the company administrators. The Settings → Monitoring → Credentials menu appears only for them.
Credential types
Type | What it's for |
|---|---|
SSH | Linux servers and network devices over SSH: password or private key |
Windows (WinRM) | Windows servers, with a local or domain account |
SNMP v1/v2c (community) | Switches, printers and UPS units with an SNMP community |
SNMPv3 | Network devices with user, authentication and privacy |
Database | PostgreSQL, MySQL, SQL Server or Oracle, with or without TLS |
API token | A fixed token sent in a header or in the URL |
Cloud (costs) | AWS, Google Cloud or Azure, read-only access to costs |
Username and password | APIs with basic authentication, or plugins |
OAuth2 (client credentials or refresh token) | APIs with an OAuth2 server |
Token from another API (custom login) | A custom login that returns a token for the checks |
Client certificate (mTLS) | APIs that require a certificate and key |
Tunnel backup | Created by ARGUNIS for Vulnerabilities private connections; it isn't created or edited here |
What the list shows
Credential: name, summary, description, tags and the inventory group it is limited to.
Type.
Value: always hidden, with its version and the date of the last rotation.
Stored in: ARGUNIS vault. Old credentials stored in an agent appear flagged so you can move them to the vault.
Usage: how many components use it, when it was last used and whether it failed.
Last test.