A Modern, Agentless Approach to Complete Asset Management
Armis® is the first agentless, passive, enterprise-class security platform to address the new threat landscape of managed, unmanaged and IoT devices. It discovers every asset in your environment, analyzes device behavior to identify risks or attacks, and protects your critical business information and systems. Together, Armis and ServiceNow provide a unified asset management solution for any managed, unmanaged, IoT, medical, and manufacturing/OT device.
Continuous, Reliable Device Visibility
Having an asset inventory you can trust is a critical component for any IT or security team’s success. But with so many devices in your environment today, many of which traditional asset management and security products can’t even see, it’s hard to know what’s there--and what’s not.
When integrated with the ServiceNow CMDB, the Armis platform makes sure ServiceNow always has the latest details (hardware, installed operating system, and more) about every device in your environment. Armis continuously and passively monitors devices for additional information it can use to true-up details in your ServiceNow CMDB, giving you a complete and up-to-date asset inventory whenever you need it.
- ServiceNow Operational Technology (OT) Certified
- Identify and classify managed, unmanaged, OT and IoT devices passively in real-time, with no agent or scanning required
- Monitor device activity to true-up your CMDB with new device details
- Reduce or eliminate duplicate, erroneous, or stale CMDB device information
Version 2.3.1
Features
- Class mappings corrected. 31 default class mappings were corrected.
- Five Armis types now map to different classes.
- Controllers (DCS) types now map to OT Control System.
- Computer types now allow OS classification, so a Windows Server or Ubuntu device is classified into its server class.
- Model comes from the Armis detailed model. A device's Model now uses the Armis detailed model (detailedModel) and falls back to the Armis model when the detailed model is blank.
- Virtual machines are marked virtual. Is Virtual is now also set for devices whose Armis type is Virtual Machines, even when the Armis isVirtual value is false or empty.
Fixes
- External URL. The device link on a CI now opens the device page in Armis. When the Armis connection URL or the device ID is blank, the link is left empty instead of being written as a broken relative link.
- Devices with many network adapters. A device with about 200 or more network adapters no longer fails the import with the error "Exceeded maximum allowed length 65536 for a string". All of its adapters are imported.
- AppendMAC naming strategies. A CI name that already contains a MAC address no longer gets a second MAC address appended on each import.
- Require a type mapping. With x_armis_cmdb.classification_require_type_map set to true, devices whose type has an active classification setting are now imported. Before, every device was dropped. With the property set to false, deactivating a type now stops its devices from being imported. A device matches a setting only when its Armis category and type both match exactly, and the setting's network type is empty or matches the network type of the device's site.
- Cached access token. The cached Armis access token (x_armis_cmdb.armis_token_object) can now be read only by users with the x_armis_cmdb.admin role. Imports run by an account with only the x_armis_cmdb.user role still authenticate.
Other changes
- The import log now reports how many devices were ignored because of their type.
- The description of the x_armis_cmdb.classification_require_type_map property now states the matching rule. Its value and default (false) are unchanged.
- The package dependency records match the previous release (2.2.1). No dependency was added or removed.
- The installation guide is updated: the class mappings table, the Model and Is Virtual field mappings, the naming strategies description and the classification_require_type_map property.
After upgrading
A Store upgrade does not overwrite a record or property you have customized. Check the items below.
- Imported field list. If you customized x_armis_cmdb.import_fields, the upgrade skips it and detailedModel is not requested from Armis. Add detailedModel to the value. Without it, Model keeps coming from the Armis model.
- Cached token property. The upgrade moves the read role of x_armis_cmdb.armis_token_object from x_armis_cmdb.user to x_armis_cmdb.admin only when the property still has its shipped read role. If you changed its read roles, set the read role to x_armis_cmdb.admin yourself.
- Class mappings. A classification setting you edited keeps your values, so it does not receive the corrected class. Compare your rows with the class mappings table in the installation guide, and update the ones you want to match.
- Existing CIs. The upgrade does not rewrite CIs that already exist.
- Names that already gained extra MAC addresses are not cleaned up.
- CIs are not reclassified when a class mapping changed.
- Virtual machines that were imported without Is Virtual set are not updated.
- A CI picks up the new Model the next time its device is imported. Is Virtual is not changed on an existing CI.
- Naming strategies. If you customized one of the AppendMAC naming strategy scripts, the upgrade skips it and it can still append a second MAC address. Copy the new behavior into your script: return the name unchanged when it already contains a MAC address.
- Require a type mapping. If you run with x_armis_cmdb.classification_require_type_map set to true, devices that were dropped before now import. Check that the type settings you expect are active before the first import after the upgrade.
- IntegrationHub ETL (2.1.1 or higher)
- ISA Equipment Model
- CMDB CI Class Models (1.71.0 or higher)
- Integration Commons for CMDB (sn_cmdb_int_util) (2.12.0 or higher)
- ServiceNow IntegrationHub Action Template - Data Stream
- ITOM Licensing (com.snc.itom.license) plugin
You will need an Armis License granting API access to make use of this integration.
In addition, usage of this Service Graph Connector requires a subscription to a Subscription Unit based IT Operations Management (ITOM) Visibility or ITOM Discovery application. Managed IT Resources (as defined in Section 1.1 of the ServiceNow Subscription Unit Overview - https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/servicenow-subscription-unit-overview.pdf) created or modified in the CMDB by this Service Graph Connector, but not yet managed by ITOM Visibility or ITOM Discovery, will increase Subscription Unit consumption within that application. Customers should review their current Subscription Unit consumption within ITOM Visibility or ITOM Discovery to ensure available capacity.