Synchronizes Orca Security cloud asset inventory into ServiceNow CMDB across multiple asset types (VMs, Containers, Buckets, Databases, VPCs, Load Balancers, Serverless, Kubernetes, IAM, and more).
Overview
First release of the Orca Security CMDB Integration. The application synchronizes multi-cloud asset inventory from the Orca Security into the ServiceNow CMDB using the IntegrationHub ETL framework. Records are reconciled through ServiceNow's Identification and Reconciliation Engine (IRE) and land CMDB tables that extend standard CI classes.
What's new
Asset synchronization. Synchronizes Orca Security cloud asset inventory into ServiceNow CMDB across multiple asset types: Virtual Machines, Containers, Buckets, Databases, Load Balancers, Segregation/Transport, Serverless, Kubernetes, Identity and Access, and a Catch-all pipeline for anything that does not match a category.
Multi-cloud coverage. Single integration covers AWS, Azure, GCP, and OCI.
IRE-based reconciliation. All inbound records pass through the Identification and Reconciliation Engine. CIs coalesce on object_id (mapped from Orca's id). Existing CIs are updated; new ones are created; duplicates are avoided.
Scheduled imports. Daily scheduled imports per asset category (Orca VM, Containers, Buckets, Databases, Load Balancer, Segregation, Serverless, Identity and Access, Kubernetes, Catch-all). Each schedule can be run on demand via Execute Now.
Staleness handling. Stale Asset Retirement flow marks CIs as Operational or Retired based on a configurable staleness threshold (in hours).
Role model. Two app-scoped roles: x_orse_orca_sec.orca_admin for configuration and scheduled imports, x_orse_orca_sec.orca_user for read-only access to imported records.
Installation
- Install the plugin dependencies listed above from System Definition > Plugins.
- Install Orca Security CMDB Integration from the ServiceNow Store, or apply the v1.0.0 update set on the target instance.
- Assign x_orse_orca_sec.orca_admin to the integration admin and x_orse_orca_sec.orca_user to read-only users.
- In the Global scope, open the cmdb_ci table and add a new choice value Orca (label and value) to the Discovery Source field, then switch back to the application scope.
- Under IntegrationHub > Connection and Credential Alias > Orca API Token Credential, create a new Connection record with a placeholder URL (for example https://placeholder.com). The placeholder host must be present even though it is not used at runtime — the Data Stream action will not execute without it.
- Open Orca CMDB Integration > Orca Configs, paste the Orca API token, set the batch size and staleness threshold, then save. The token is validated live on save.
- Navigate to Orca CMDB Integration > Orca Schedule Imports > Orca VM, click Execute Now, and confirm records appear in x_orse_orca_sec_orca_virtual_machine_instance and in cmdb_ci.
- Repeat for the remaining scheduled imports, then activate the Stale Asset Retirement flow in Flow Designer with the desired cadence.
Full step-by-step instructions, including screenshots, are in the Installation and Configuration Guide that ships with the release.
Plugin dependencies
- IntegrationHub ETL 3.3.6
- Discovery and Service Mapping Patterns 1.30.2
- CMDB CI Class Models 1.81.1