Asset Decommission

The decommission process allows users to immediately remove assets from reports, the dashboard, and API without waiting for the 30-day inactivity period. This feature is intended for individual asset removal from an environment. Do not use this feature if the asset was collected in error. Submit any inaccurate detection or scanning of assets by opening a ticket using the Support icon located at the bottom right of this page.

Scanning will cease for decommissioned assets, but small amounts of network traffic may still appear as detailed in each category below. The optional “reason for decommissioning asset” text field may be used to justify decommissioning an asset. The justification provided will be included as part of the decommissioning data records if needed for audit purposes.

Assets will immediately move to the Decommissioned section of the asset list and will not be included on reports or API calls made after decommissioning. Changes to the total asset counts and customer level scoring may be delayed for up to 30 minutes in the dashboard.

View decommissioned assets at any time under the Decommissioned tab to the left of the Customer Asset List. Decommission assets are listed in the “Decommissioned List” for 30 days or until offline 30 days, whichever is longer.

Nodeware Agents

Decommissioned assets with an installed agent should be uninstalled in the manner they were originally installed. If an agent remains on a decommissioned asset, then there may be continued network activity to the Nodeware backend; however, vulnerability scans will not run.

To reinstate a Nodeware Agent after decommissioning, the software must be reinstalled.

Uninstall instructions for each platform can be found in the articles below:

• Windows Agent
• macOS Agent
• Ubuntu and Debian Agents

Sensor Discovered Assets

Assets that are discovered by a Nodeware Sensor will continue to receive inventory related network traffic after decommissioning unless they are removed from the network–fingerprint. Vulnerability scans will not be run.

Reactivating a Nodeware Sensor may reinstate a decommissioned asset if it remains on the monitored network.

External Assets

External assets cannot be decommissioned, they must be deleted instead. This can be done in the Manage Customer view, under Sites & Interfaces. For more information, see this knowledge base article.

Subscription Billing

Decommissioned assets may be subject to billing if they were actively scanned during the current billing period; however, they will not be billed in future billing periods or actively scanned as outlined above.

Bulk Decommission

Assets can also be decommissioned from the main Assets View by selecting multiple assets with the check boxes on left of the rows and clicking Decommission option from the actions bar. This will launch the modal shown above where the justification can be recorded for auditing purposes. Clicking Decommission will confirm the changes and reload the view.