[ Applies to ] StorageGuard 9.2.8 and later / All supported storage, backup, SAN and cloud systems / Windows and Linux deployments
StorageGuard needs two things before it can sign in to a system. A credential is the account it signs in with. A connectivity policy says how it connects: which protocol, which credential, and whether to go through a proxy or use sudo. You create credentials first, then the policies that use them. Every data source and host you add references one connectivity policy, so one policy can serve many systems that connect the same way.
StorageGuard only needs read-only access: it runs queries, commands and API calls that read configuration, and never changes it.
Note: A connectivity policy controls how StorageGuard connects. A security policy controls what it checks. They are unrelated.
In this article
Before you begin
- A read-only account exists on each target system. The required permissions for each platform are listed in StorageGuard Scan Requirements.
- If a privileged access management (PAM) tool holds your passwords, that integration is set up first. See StorageGuard Integration with CyberArk or Configuring HashiCorp Vault in StorageGuard.
Choose a credential type
Pick the type that matches how the target system authenticates, or where the password is stored.
| Credential type | Use it for |
|---|---|
| Username and password | Most storage systems, hosts and databases. |
| SSH public key | Systems that require SSH key authentication. |
| Cyber-Ark | Passwords managed in CyberArk through the agent-based Credential Provider. |
| Cyber-Ark CCP | Passwords and certificates managed in CyberArk through the Central Credential Provider API. |
| Hashicorp | Credentials managed in HashiCorp Vault. |
| Hashicorp Vault (Token) | Tokens managed in HashiCorp Vault. |
| Cloakware | Credentials managed in CA Privileged Access Manager (formerly Cloakware). |
| Kerberos V5 | Linux hosts that authenticate with Kerberos. |
| Rotating Password | SSH accounts whose password StorageGuard changes automatically. |
| AWS access keys | AWS accounts. Enter the access key and secret. |
| Azure Access Keys | Azure accounts. Enter the access key and secret. |
| Storage Protect | IBM Storage Protect hosts and the dsmadmc administrative client. |
| Group Managed Service Accounts (gMSA) | Windows-based storage or backup systems that use gMSA. |
| Cloud Scale | Hitachi HCP for Cloud Scale. |
| Networker | Dell NetWorker. |
Add a credential
- Go to Settings > Scan > Authentication > Credentials.
- Click +.
- Select the Credential type.
- In Name, enter a name that identifies the account and where it's used, for example PowerStore read-only (Boston). You pick credentials by this name later.
- Enter the user name and password, or the fields your credential type requires. For rotating passwords and Kerberos, see the extra settings below.
- Click Save. The credential appears in the credentials list.
Extra settings for rotating passwords
Set Password expiration to Each Scan to change the password every time StorageGuard scans the host, or to a number of days.
Note: Set the expiration shorter than the password expiry policy on the target system, so StorageGuard changes the password before the system forces it to.
Extra settings for Kerberos V5
| Field | What to enter |
|---|---|
| KDC | The Key Distribution Center to use, for example a Microsoft domain controller. |
| Realm | The Kerberos realm or Active Directory domain. |
| Keytab | The path to the keytab file on the StorageGuard server. If you use a keytab, leave Password blank. |
| Username | The account name. |
| Password | The password, entered twice. Leave blank if you use a keytab. |
Decide what the connectivity policy needs
| Component | Required | When you need it |
|---|---|---|
| Protocol | Yes | Always. StorageGuard connects over secure protocols such as SSH, HTTPS and WinRM. Automatic Protocol is the default and recommended setting. |
| Credential | Yes | Always. |
| Proxy | No | When StorageGuard must reach systems through a hardened jump server or an outbound proxy instead of connecting directly. |
| Sudo | No | When the account isn't an administrator and must run privileged read-only commands, for example on Linux hosts or Dell PowerScale. Not needed with an administrative account. |
If you need a proxy or sudo, add it first so you can select it in the policy. Otherwise, continue below.
Create the connectivity policy
- Go to Settings > Scan > Authentication > Policies.
- Click +.
- In Name, enter a name that describes how the policy connects, for example HTTPS – PowerStore read-only or SSH + sudo – Linux via jump server.
- Select the Protocol. It's recommended to keep the default Automatic Protocol setting.
- If you need them, select a Proxy and a Sudo configuration.
- Select the Credential.
- Click Save.
Tip: Name policies by protocol and purpose, not by system. You'll choose them from a drop-down every time you add a data source or host, and one policy often serves many systems.
Edit or delete credentials and policies
- Credentials: in Settings > Scan > Authentication > Credentials, double-click a credential to edit it, then click Save. To delete one, right-click it and select Delete.
- Connectivity policies: in Settings > Scan > Authentication > Policies, right-click a policy and select Edit or Delete, then confirm.
- Proxies and sudo configurations: edit or delete them the same way on the Connectivity Methods page.
Add a proxy (optional)
- Go to Settings > Scan > Authentication > Connectivity Methods.
- In the top-left corner, select Proxy.
- Click +.
- Enter the proxy's name, IP address, protocol and credential.
- Click Save. The proxy appears in the proxy list.
Note: The protocol you set here is the one the proxy uses to connect onward to the target system, not the one StorageGuard uses to connect to the proxy.
Then select the proxy when you create the connectivity policy, or edit an existing policy to add it.
Add a sudo configuration (optional)
A sudo configuration lets a non-root account run the privileged read-only commands a scan needs, without full root access.
- Go to Settings > Scan > Authentication > Connectivity Methods.
- In the top-left corner, select Sudo.
- Click +.
- Enter the following, then click Save.
| Field | What to enter |
|---|---|
| Name | A name you'll recognize when you build the policy. |
| Path | The path to the sudo binary on the target system. |
| Credential | The credential sudo runs with. |
| PTY | Select this if the target system only allows interactive SSH sessions. |
Note: StorageGuard ships with default sudo configurations for Unix and Linux (Default Unix sudo and Default Linux sudo). Don't change or delete them. Create your own if you need different settings.
Then select it when you create the connectivity policy, or edit an existing policy to add it.
[ Next step ]
Add a data source that uses this connectivity policy.
Related articles
- StorageGuard Integration with CyberArk
- Configuring HashiCorp Vault in StorageGuard
- Add a data source
- StorageGuard Scan Requirements
[ Still need help? ]
Our support team can help with connecting systems and scan setup. Submit a request
Comments
0 comments
Please sign in to leave a comment.