Skip to main content

Ollandi integrations

Connect the sources your investigation needs

Browse connections for telemetry, service context, and response. Read access and execution permissions are scoped separately; available actions depend on the connected system and your deployment.

All integrations

100 systems across the security and infrastructure stack

Search by name or browse by category. Each category shows what Ollandi reads and the actions it can take through those systems.

All integrations

Cloud platforms

Control-plane activity, IAM and policy changes, resource configuration, and network flows. Approved actions: session revocation, privilege suspension, and access-path blocks through your cloud controls.

Amazon Web Services

Cloud platforms

Microsoft Azure

Cloud platforms

Google Cloud

Cloud platforms

Oracle Cloud Infrastructure

Cloud platforms

Alibaba Cloud

Cloud platforms

IBM Cloud

Cloud platforms

Glemad Cloud

Cloud platforms

Identity and access

Sign-ins, MFA, sessions, roles, privilege use, and machine identities. Approved actions: step-up authentication, session revocation, and temporary privilege suspension.

Microsoft Entra ID

Identity and access

Active Directory

Identity and access

Okta

Identity and access

Ping Identity

Identity and access

CyberArk

Identity and access

Duo

Identity and access

Glemad Identity

Identity and access

Endpoint protection

Process, file, user, and connection activity from your endpoint tools. Approved actions: host isolation and process containment through your endpoint tool.

CrowdStrike Falcon

Endpoint protection

SentinelOne

Endpoint protection

Microsoft Defender for Endpoint

Endpoint protection

Sophos

Endpoint protection

Trend Micro

Endpoint protection

Carbon Black

Endpoint protection

ESET

Endpoint protection

SIEM and logs

The events and detections you already collect, related to live infrastructure state.

Splunk

SIEM and logs

Microsoft Sentinel

SIEM and logs

Elastic

SIEM and logs

IBM QRadar

SIEM and logs

Sumo Logic

SIEM and logs

Graylog

SIEM and logs

Syslog

SIEM and logs

Network and firewall

Flows, routes, segmentation, VPN, DNS, and egress activity. Approved actions: temporary blocks and segmentation changes through your network controls.

Palo Alto Networks

Network and firewall

Fortinet

Network and firewall

Cisco

Network and firewall

Check Point

Network and firewall

Juniper Networks

Network and firewall

Cloudflare

Network and firewall

Zscaler

Network and firewall

NetFlow and sFlow

Network and firewall

Cloud security posture

Misconfigurations, exposure, and posture findings across cloud accounts.

Microsoft Defender for Cloud

Cloud security posture

Orca Security

Cloud security posture

Containers and runtime

Workloads, images, deployments, and runtime behavior. Approved actions: workload quarantine and deployment rollback where policy allows.

Kubernetes

Containers and runtime

Docker

Containers and runtime

Red Hat OpenShift

Containers and runtime

Amazon EKS

Containers and runtime

On-premises and virtualization

Servers, directories, hypervisors, storage, and hybrid dependencies.

VMware vSphere

On-premises and virtualization

Microsoft Hyper-V

On-premises and virtualization

Nutanix

On-premises and virtualization

OpenStack

On-premises and virtualization

Windows Server

On-premises and virtualization

Linux servers

On-premises and virtualization

Vulnerability management

Vulnerabilities and exposure, ranked by what an attacker could actually reach.

Tenable

Vulnerability management

Qualys

Vulnerability management

Rapid7

Vulnerability management

Monitoring and observability

Availability, performance, and capacity from your monitoring tools, so failures and threats are read together.

Datadog

Monitoring and observability

Dynatrace

Monitoring and observability

New Relic

Monitoring and observability

Prometheus

Monitoring and observability

Grafana

Monitoring and observability

Zabbix

Monitoring and observability

SolarWinds

Monitoring and observability

Nagios

Monitoring and observability

Paessler PRTG

Monitoring and observability

Code and delivery

Commits, pipelines, infrastructure-as-code changes, and releases tied to live behavior.

GitHub

Code and delivery

GitLab

Code and delivery

Bitbucket

Code and delivery

Jenkins

Code and delivery

Terraform

Code and delivery

Databases and APIs

Database activity, API gateway traffic, and application audit events. Approved actions: aPI throttling and credential rotation through your gateways and vaults.

PostgreSQL

Databases and APIs

Microsoft SQL Server

Databases and APIs

Oracle Database

Databases and APIs

MongoDB

Databases and APIs

Kong

Databases and APIs

Apigee

Databases and APIs

Workspace and collaboration

Mail, chat, file sharing, and account activity where your teams work every day. Approved actions: session revocation and holds on risky sharing through the workspace itself.

Google Workspace

Workspace and collaboration

Kimpa Workspace

Workspace and collaboration

Service management and messaging

Change records, ownership, and on-call context. Approved actions: cases, approvals, and notifications sent to the teams that own the response.

ServiceNow

Service management and messaging

Jira

Service management and messaging

Slack

Service management and messaging

Microsoft Teams

Service management and messaging

PagerDuty

Service management and messaging

Opsgenie

Service management and messaging

Email

Service management and messaging

Banking and ATM

Terminal health, dispensing, cash state, switch links, card systems, and core banking service paths. Approved actions: cases, escalations, and service holds routed through your ATM and banking operations.

BankWorld

Banking and ATM

NCR Atleos APTRA

Banking and ATM

Diebold Nixdorf Vynamic

Banking and ATM

KAL Kalignite

Banking and ATM

ACI Postilion

Banking and ATM

ACI BASE24

Banking and ATM

Temenos

Banking and ATM

Finacle

Banking and ATM

Oracle FLEXCUBE

Banking and ATM

Mambu

Banking and ATM

Card management systems

Banking and ATM

Telecommunications

Network elements, alarms, and service paths from your network management systems, plus USSD, mobile money, and partner links.

Ericsson Network Manager

Telecommunications

Nokia NetAct

Telecommunications

Huawei iMaster NCE

Telecommunications

USSD gateways

Telecommunications

Mobile money platforms

Telecommunications

Partner bank links

Telecommunications

Facilities and power

Power, UPS, generator, cooling, and building system state behind your infrastructure.

UPS and generator monitoring

Facilities and power

Building management systems

Facilities and power

Data center infrastructure management

Facilities and power

How integrations work

From source access to an approved action path

Plan how data is collected, normalized, and related to service context. Configure execution permissions separately for systems that support response.

  1. Connect

    Link each system, in cloud, on-premises, or both.

  2. Normalize

    Evidence becomes one shared picture of entities and change, with its source and time kept.

  3. Reason

    Ollandi relates every system to the others and tracks threats, failures, and vulnerabilities as they develop.

  4. Act

    A permitted action uses the connected identity, network, endpoint, or workflow system.

  5. Record

    What was read, decided, and changed is kept as audit-ready evidence.

Your own systems

Do not see your system here?

Ollandi also connects through syslog, standard log and flow formats, and its own API, so in-house platforms and less common tools can join the same picture.

FAQ

Frequently asked questions

  1. A connection supplies data or an action path; it does not establish replacement coverage. Evaluate overlapping capabilities, retention needs, and enforcement dependencies before retiring a tool.

  2. Where supported, approved actions use the connected system’s controls. Read access alone does not grant execution permission; action support and scope are reviewed during integration.

  3. Yes. Cloud, on-premises, and hybrid systems feed one shared picture, so an attack or a failure that crosses from one to the other stays one case.

  4. Ollandi can connect through syslog, standard log and flow formats, and the Ollandi API. Tell us what you run and we will plan the connection.

  5. It depends on the systems and the scope you choose. Most teams start with a few systems tied to one service they cannot afford to lose, then add more.

Get started

Map your stack to Ollandi

Tell us what you run today, and we will show which systems to connect first and what Ollandi can do with them.