← Back to Integration
CLOUD SECURITY

Integration with Orca Security Integration with SPOG.AI

SPOG.AI integrates with Orca Security to centralize cloud asset and vulnerability visibility. The implemented connector imports Orca Serving Layer inventory and related vulnerability data into the SPOG.AI CMDB for security, risk, and compliance workflows.

Key Features

CapabilityDescription
Cloud Asset InventoryImports cloud resources discovered by Orca.
Vulnerability ContextAssociates Orca vulnerability findings with matching assets.
Multi-cloud VisibilityNormalizes supported cloud assets into SPOG.AI.
CMDB EnrichmentAdds Orca inventory and security context to asset records.

How the Integration Works

The SPOG Appliance authenticates with an Orca API token and calls the Serving Layer query API over HTTPS. It paginates inventory and vulnerability results, observes the provider request limit, enriches matching assets, and removes stale Orca enrichment after a successful synchronization.

Prerequisites

Before configuring the integration, ensure the following prerequisites are met:

  • Tenant Admin authorization in SPOG.AI.
  • Orca administrator access and an API token with read access to Serving Layer inventory and vulnerability data.
  • The regional Orca API base URL, including /api, when the default India endpoint is not applicable.
  • Outbound HTTPS access from the SPOG Appliance to the Orca API.

Configuration

1. Create an Orca API Token

Create a dedicated, least-privileged token in Orca Security.

  • Grant read access to inventory and vulnerability data used by the Serving Layer query.
  • Copy the token and store it securely.

2. Configure and Link the Integration

Create the Orca integration in SPOG.AI.

  • Enter the API token and, if required, the regional API host.
  • Save the integration, then link it to the required appliance under Administration > Appliance > Integrations.

Configuration Fields

Use the fields below when creating the integration in SPOG.AI.

FieldRequirementDescription
tokenMandatoryOrca API token. The implementation also accepts api_token as an alias.
hostOptionalAPI base URL including /api. If omitted, the implementation defaults to https://api.in.orcasecurity.io/api.

Security and Connectivity

  • Use a dedicated read-only token and rotate it according to organizational policy.
  • Store the token in a secrets vault and never place it in logs or documentation.
  • Allow outbound HTTPS port 443 to the configured Orca API host and require TLS 1.2 or later.
  • Account for Orca Serving Layer throttling; the connector limits requests to approximately two per second.

Validation and Data Coverage

Run Test Connection or an appliance synchronization, then confirm Orca-enriched assets and vulnerability data in SPOG.AI. A 401 indicates an invalid token, a 403 indicates insufficient access, and timeouts usually indicate DNS, proxy, or firewall issues.

DataCoverage
AssetsCloud inventory returned by the Orca Inventory model, including identity, type, region, cloud account, and business-unit context when available.
VulnerabilitiesRelated vulnerability identifiers, severity, CVEs, package context, and remediation metadata when returned.
SynchronizationPaginated collection, CMDB enrichment, and stale-service cleanup after a successful run.
Not ImplementedWebhook ingestion, alert ingestion, and configuration changes are not performed by this connector.

Uninstalling the Integration

  • Delete the Orca integration in SPOG.AI and unlink it from the appliance.
  • Revoke the dedicated Orca API token.
  • Remove obsolete allowlist or proxy rules.