2.3 Adding Known, Unmanaged Assets

Available only in the Windows console.

If you already know the host name or IP addresses of assets that you to assess with Secure Configuration Manager, you can manually add them from the Windows console. Alternatively, if you have a large number of known assets, you can create a file to import the assets. You can add Windows or UNIX servers.

The assets do not need a security agent before you add them to Secure Configuration Manager. Instead, you can assign an existing agent to each asset as you manually add them or assign the agent later. However, the asset must have an agent before you can register the asset with Secure Configuration Manager and begin assessing it for vulnerabilities. For more information, see Registering Managed Assets.

Your console user account must have proper permissions to add assets. For more information about permissions, see Managing Permissions.

2.3.1 Manually Adding Known Assets

If you have a few servers for which you already know the IP address and host name, it might be easier to manually add them. This wizard enables you to add assets with or without an agent. If the asset has an agent, you can also register the asset ass you add it to Secure Configuration Manager. For more information about registeration, see Registering Managed Assets.

  1. Log in to the Windows console.

  2. Select IT Assets > Managed Systems.

    NOTE:You can also add assets in this same way from IT Assets > Agents.

  3. Complete the wizard for adding assets.

NOTE:Secure Configuration Manager supports IPv4 and IPv6 addresses. For more information about IPv6 support, see Discovering Unmanaged Assets in Your Environment, the Secure Configuration Manager Installation Guide, and the Secure Configuration Manager Windows Agent Installation and Configuration Guide.

2.3.2 Using a Formatted File to Add Known Assets

The Core Services Configuration Utility enables you to specify a file containing a list of computers that you want to manage. Core Services reads the file and adds the listed computers to the Discovered Systems content pane. In the configuration utility, you must set the File Import Discovery field to True and specify the type and name of file to import. Secure Configuration Manager imports the systems from the file on a scheduled basis. The import runs on the same schedule as the Automatic System Discovery scheduled job. For more information about this job, see Scheduling the Discovery Process. For more information about the file import settings, see the Help for the Core Services Configuration Utility.

NOTE:Secure Configuration Manager supports IPv4 and IPv6 addresses.

The file must be an NMAP XML file, or a file in the proprietary format used by Secure Configuration Manager. If you are using the proprietary format, the complete format required for importing systems from a text file into Secure Configuration Manager is as follows:

HostName<Tab>IPAddress<Tab>Domain<Enter>

However, you can use any of the following formats as well:

HostName<Tab>IPAddress<Enter>
HostName<Tab>null<Tab>Domain<Enter> 
HostName<Enter>

The following lines are examples from an import host file:

Host1    163.28.152.2    company.com
Host2    138.25.918.4
Host3    null    company.com
Host4    2001:db8:85a3:8d3:1319:8a2e:37:7334    company.com
Host5    2001:0db8:85a3:08d3:1319:8a2e:0370:7334