Change record: ServiceNow completes the Armis acquisition

What changed

ServiceNow announced completion of its Armis acquisition.

This entry preserves the event separately from maintained provider and capability conclusions. A rule, announcement, release, enforcement record, or market transaction can be material before enough evidence exists to revise a company classification or comparison.

Operating consequence

Buyers need current evidence for product identity, packaging, workflow, data governance, integrations, and organizational responsibility after the ownership change.

Teams should identify which records, populations, systems, transactions, jurisdictions, products, or decisions fall within the change. Then assign an accountable owner, response date, evidence requirement, and disposition. Broad reassessment is not always necessary, but a material event deserves a documented decision.

Capabilities to revisit

Passive OT Asset Discovery And Inventory

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for passive OT asset discovery and inventory.

Asset Criticality And Operational Context

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for asset criticality and operational context.

Vulnerability And Exposure Correlation

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for vulnerability and exposure correlation.

IT Security-Operations Integration And APIs

Review the maintained workflow definition, then ask affected organizations to show how this event alters inputs, governed rules, human judgment, exceptions, action, evidence retention, and downstream exchange for IT security-operations integration and APIs.

Questions for operating teams

• Which exact population and effective date does the source establish?
• Does the change alter authority, policy, content, workflow, integration, evidence, or only market positioning?
• What customer-controlled interpretation, configuration, or process remains outside a provider's responsibility?
• What test case would show whether the operational consequence has reached production?
• What record will close, defer, or supersede this review?

Evidence boundary

The source class is Official company announcement. It establishes only the statements supported by the linked record and does not, by itself, establish implementation depth, market-wide availability, transaction-specific applicability, independent efficacy, or a universal buyer conclusion.