--- title: "Add a Linux node" description: "Add a Linux node for agentless scanning over SSH." product: "Guardian" edition: "Classic" type: "workflow" url: "https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/linux-node/" --- # Add a Linux node Add a Linux node for agentless scanning over SSH. Guardian supports multiple types of Linux nodes. For example, you can add Debian nodes, Ubuntu nodes, CentOS nodes, and more. Applies to: `Guardian Classic` !!! note For information on using the Linux Agent to add nodes, see [Linux Agent](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agents/linux-agent/index.md). ## Add a Linux node Adding a Linux node to your Guardian instance lets you monitor and track the configuration of a Linux system. !!! warning The following process assumes that you already have a Linux Connection Manager configured within your Guardian instance. For more information, see [Linux Connection Manager](https://docs.cloudhouse.com/guardian/classic/inventory/connection-managers/connection-managers/linux/linux-connection-manager/index.md). To add a Linux node for Agentless scanning, complete the following steps: 1. In the Guardian web application, navigate to the **Add Nodes** tab (**Inventory** > **Add Nodes**). The **Add Nodes** page is displayed. ![Add nodes tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/add-nodes-tab.png) 2. Type 'Linux' in the search bar. 3. Select the 'Linux' node type you want to add and click the **Go Agentless** button to proceed. The **Connect Agentlessly to [Node Type]** page is displayed. ![Linux node](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/linux-node.png) 4. Here, complete the following options: ![Connect agentlessly linux](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/inventory/add-nodes/single-nodes/connect-agentlessly-linux.png) **Connection Manager group** drop-down list : The Connection Manager group that is responsible for scanning your Linux node. Select a Connection Manager group from the drop-down list. **Node Name** field : The name of the node. The value you enter here will be used as the display name in Guardian. **Hostname / IP Address** field : The hostname or IP address of your node. !!! note Typically, this is the fully qualified domain name (**FQDN**). However, it could also be the IP address. **SSH Port (Optional)** field : The Secure Shell (**SSH**) port number that the Linux Connection Manager uses to communicate with the target nodes for scanning. If no value is provided, Guardian will default to port 22. !!! note If you enter a port number that is different to the default (port 22), make sure that it matches the port number that the administrator of the target node is using to run their SSH server. **Select credential type** radio buttons : The credentials to be used when authenticating Guardian's access to the node. The following options are available: - **SSH Key** – Option to use an SSH key to authenticate Guardian's access to the node. Enter the **Username**, then copy the displayed command and run it on the node to create the necessary files. For more information, see [Key-Based Authentication](https://docs.cloudhouse.com/guardian/classic/inventory/add-nodes/add-a-single-node/agentless/network-device-node/index.md#key-based-authentication). - Password – Option to use credentials stored in the Guardian vault or Secret Server. Select one of the options below: - **Guardian Credentials Vault** – Use credentials stored in your Guardian instance. Select an option from the **Credentials** drop-down list. Additionally, you can select 'Add New Credential' to display the **Create Credential** dialog if you anticipate using these same credentials for other nodes or integrations. For more information, see [Create Credential](https://docs.cloudhouse.com/guardian/classic/inventory/credentials/credentials/index.md#create-credential). !!! note The **Credentials** tab was introduced in V4.3.46.0 of Guardian. For more information, see [July 2024 Quarterly Release](https://docs.cloudhouse.com/guardian/classic/what-s-new/3-archive/2024/quarterly-releases/q2/july-feature-2024/index.md). !!! warning This option is only displayed if you have the **Credentials** feature enabled. If you don't, you'll be prompted to enter a **Username** and **Password** for authentication. - **Secret Server** – Use credentials stored in your organisation's existing Secret Server account. Select an option from the **Secret Server Items** drop-down list. The credentials displayed are based on the Secret Server integration. For more information, see [Secret Server Integration](https://docs.cloudhouse.com/guardian/classic/control/integrations/secret-server-integration/index.md). !!! note The Secret Server feature was introduced in V3.54.0 of Guardian. For more information, see [April 2025 Quarterly Release](https://docs.cloudhouse.com/guardian/classic/what-s-new/2-previous-release/2025/quarterly/q2/april-2025/index.md). !!! warning This option is only displayed if you have the Secret Server feature enabled. If you don't, you'll be prompted to enter a **Username** and **Password** for authentication. - **Azure Key Vault** – Use credentials stored in your organisation's Azure Key Vault. The credentials displayed are based on the Azure Key Vault integration. For more information, see [Azure Key Vault Credentials](https://docs.cloudhouse.com/guardian/classic/inventory/credentials/azure-key-vault-credentials/index.md). !!! note The Azure Key Vault feature was introduced in V3.63.0 of the Guardian Web Application. This is an optional feature that must be enabled. For more information, see [February 2026 Monthly Release](https://docs.cloudhouse.com/guardian/classic/what-s-new/1-current-release/monthly/february-2026/index.md). If selected, you are required to provide the following information: - **Username** field – Enter the username of the Azure account required to access the Azure Key Vault. This must be the same account that the selected Azure Key Vault secret belongs to. - **Azure Key Vault Items** drop-down list – Select a secret from the list. The secrets displayed are based on values from the Key Vault(s) configured in the Azure Key Vault integration. !!! tip For more information, see [Azure Key Vault Integration](https://docs.cloudhouse.com/guardian/classic/control/integrations/azure-key-vault-integration/index.md). !!! warning This option is only displayed if you have the Azure Key Vault feature enabled. If you don't, you'll be prompted to enter a **Username** and **Password** for authentication. - **AWS Secrets Manager** – Use credentials stored in your organisations AWS Secrets Manager. The credentials displayed are based on the AWS Secrets Manager integration. For more information, see [AWS Secrets Manager Credentials](https://docs.cloudhouse.com/guardian/classic/inventory/credentials/aws-secrets-manager-credentials/index.md). !!! note The AWS Secrets Manager feature was introduced in V3.64.0 of the Guardian Web Application. This is an optional feature that must be enabled. For more information, see [March 2026 Monthly Release](https://docs.cloudhouse.com/guardian/classic/what-s-new/1-current-release/monthly/march-2026/index.md). - **AWS Secrets Manager Items** drop-down list – Select credentials from the list. The credentials displayed are based on values from the credentials configured in the AWS Secrets Manager integration. !!! tip For more information, see [AWS Secrets Manager Integration](https://docs.cloudhouse.com/guardian/classic/control/integrations/aws-secrets-manager-integration/index.md). !!! warning This option is only displayed if you have the AWS Secrets Manager feature enabled. If you don't, you'll be prompted to enter a **Username** and **Password** for authentication. - **Microsoft Entra ID** – Option to use the Azure CLI service principle credentials that are configured to use SSH. Enter the following information: - **Username** field – The username of the service principal configured to use SSH. - **Azure CLI service principal password** field – The password of the service principal configured to use SSH. - **Azure CLI service principal tenant** field – The tenant ID of the service principal configured to use SSH. - **Azure CLI login command (Optional)** field – The login command for Azure CLI. !!! note This option is only available if you have the **Microsoft Entra ID** feature enabled. - **Service Account** – Option to use the same credentials currently being used by the selected Connection Manager. No further input is needed. 5. Once you've completed the above options click **Scan Node** to add the Linux node to your Guardian instance. Now, Guardian performs an initial scan of the node. You can wait on this page for the scan to finish, at which point you will see a **View Scan** button. To view the results of this initial scan, click **View Scan**. However, you can also navigate elsewhere while Guardian performs its initial scan of the node. You can then view the status of the scan on the [**Job History**](https://docs.cloudhouse.com/guardian/classic/control/job-history/job-history/index.md) page (**Inventory** > **Job History**). For more information on what to do next after adding a node, see below. ## Where next - [*Read* **Node Scan Results** What every scan of a node collected.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/nodes/node-scan-results/index.md) - [*Organise* **Node groups** Group nodes by type, location and more.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/node-groups/node-groups/index.md) - [*Tune* **Scan options** Choose what each scan collects.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/scan-options/scan-options/index.md) - [*Compare* **Configuration differencing** Compare nodes, groups and scans.](https://docs.cloudhouse.com/guardian/classic/inventory/monitored/configuration-differencing/configuration-differencing/index.md) - [*Govern* **Policies** Define the configuration you expect.](https://docs.cloudhouse.com/guardian/classic/control/policies/policies/index.md) - [*Connect* **Integrations** Sync nodes and act on events.](https://docs.cloudhouse.com/guardian/classic/control/integrations/integrations/index.md)