How are you planning to use Armis Centrix and Veza together with ServiceNow?

[Dan_Junqueira]

Hi everyone,

With Armis Centrix and Veza becoming increasingly connected to the ServiceNow security ecosystem, I’ve been trying to understand how customers are thinking about the architecture and responsibilities between these platforms.

At a high level, I see the combination as:

• Armis Centrix providing visibility and risk context across IT, OT, IoT, cloud and other connected assets.
• Veza providing visibility into identities, permissions and answering the question of who or what has access to what.
• ServiceNow providing the business context, workflows, risk management and remediation layer.
  
  

ServiceNow itself is positioning Armis and Veza together as part of its broader Autonomous Security & Risk strategy, combining asset intelligence with identity intelligence. 

https://newsroom.servicenow.com/press-releases/details/2026/ServiceNow-launches-Autonomous-Security-...

https://investor.servicenow.com/news/news-details/2026/ServiceNow-completes-Armis-acquisition-closin...

What I am interested in is how this looks in a real implementation.

For example, imagine Armis identifies a vulnerable OT device or unmanaged asset, while Veza identifies that a service account or non-human identity has excessive privileges related to the same environment.

Would you bring both signals into ServiceNow and correlate them there to create a single risk/remediation workflow?

Or would you expect most of the correlation and prioritization to happen inside Armis/Veza first, with ServiceNow mainly orchestrating the remediation?

I’m also curious about how people see the boundaries with existing ServiceNow capabilities such as:

• CMDB / CSDM
• Vulnerability Response / Exposure Management
• Security Incident Response
• IRM
• IAM / access request processes

Veza already supports sending identity risks and remediation actions into ServiceNow workflows, while also using ServiceNow data such as CMDB context.

https://veza.com/integrations/servicenow/?

https://veza.com/blog/from-insight-to-action-automating-identity-remediation-with-veza-and-serviceno...?

So my main question is:

How would you design the target architecture so Armis, Veza and ServiceNow complement each other without creating duplicate sources of truth or overlapping remediation processes?

Would be great to hear from anyone already working with Armis Centrix, Veza, or both in a ServiceNow environment.

Thanks