> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/risk-assessment-and-prioritization/global-risk-management/hardware-security.md).

# Hardware Security

The Hardware Scan Configurations page provides a centralized view for managing and monitoring hardware security scans. This page lists all configured hardware scans, displaying their real-time execution status, associated teams, and agent connection health.

From this page, you can monitor ongoing scans, review historical scan executions, and manage individual configurations.

![](https://591284771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxDmLTMQiowMHZ4CQPCvT%2Fuploads%2FICeOnbOkhc8Fw18zWcpz%2Funknown.png?alt=media\&token=b0363683-7cca-405e-800f-ccd1f9e81249)

The following details of the scan configuration details are displayed as shown below:

* **Name** - The unique identifier or name of the hardware scan configuration.
* **Schedule** - The automated schedule (cron or interval) on which the scan runs.
* **Last Scan** - The timestamp of when the most recent scan was executed.
* **Scan Status** - The current lifecycle state of the scan. Common states include ACTIVE (running), PENDING (queued), COMPLETED (finished successfully), and FAILED (encountered an issue).
* **Scan Error** - If a scan fails, this column displays diagnostic information and error messages.
* **Team** - The specific team or access group assigned to manage the configuration.
* **Config Status** - The operational status of the configuration itself.
* **Agent Status** - The connectivity status of the underlying agent responsible for executing the scan. Possible states include connected, disconnected, or not connected. 
* **Action** - In this column the following quick actions (represented as icons) can be performed. 
  * **Trigger Scan**: Manually start a new scan for the selected configuration immediately.
  * **Edit Configuration**: Modify the settings, schedule, or team assignments of the configuration.
  * **View Assets**: Drill down to view the specific hardware assets discovered and tracked by the configuration.
  * **Delete Configuration**: Delete the configuration from the system.

### To Add a Configuration 

To add a configuration for scanning you need to access the Add Configuration page.

* Click **Add Configuration**. The Add Hardware Scan Configuration page is displayed. 

![](https://591284771-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxDmLTMQiowMHZ4CQPCvT%2Fuploads%2F05JoEUqgyFBrOS4dBFkj%2Funknown.png?alt=media\&token=e150013f-8b40-41ca-9bfe-bb74e87b9918)

* Enter the configuration details:
  * **Name** - Enter a name for the configuration.
  * **Team** - Select the teams for which the configuration needs to be applied. 
  * **Hardware Source** - Select the hardware source from the dropdown. 
  * **Hardware Integrators** - Select the hardware integrators from the dropdown. 
  * **CMDB Source** - Select the CMDB source from the dropdown. 
  * **CMDB Integrators** - Select the CMDB integrator from the dropdown. 
  * **CMDB JSON File Upload** - Click the Upload File option to upload the JSON file. 
* You can select **Schedule** to schedule the configuration’s frequency (Daily, Weekly or Monthly) and time for scanning. 
* Click **Save Configuration**. The configuration gets added for scanning.