Amazon Web Services
Cloud platforms
Ollandi integrations
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.
Featured integrations
Each one feeds the same live picture, so evidence from one system can confirm or challenge another.
Cloud platforms
Cloud platforms
Cloud platforms

Cloud platforms
Identity and access
Identity and access

Identity and access
Endpoint protection
Endpoint protection
SIEM and logs
Network and firewall
Network and firewall
Banking and ATM
Banking and ATM
Banking and ATM
Telecommunications
Telecommunications
Network and firewall
Containers and runtime
On-premises and virtualization
Code and delivery
Service management and messaging
Service management and messaging

Workspace and collaboration
All integrations
Search by name or browse by category. Each category shows what Ollandi reads and the actions it can take through those systems.
All integrations
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.
Cloud platforms
Cloud platforms
Cloud platforms
Cloud platforms
Cloud platforms
Cloud platforms

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

Identity and access

Identity and access
Process, file, user, and connection activity from your endpoint tools. Approved actions: host isolation and process containment through your endpoint tool.
Endpoint protection
Endpoint protection
Endpoint protection
Endpoint protection
Endpoint protection
Endpoint protection
Endpoint protection
The events and detections you already collect, related to live infrastructure state.
SIEM and logs
SIEM and logs
SIEM and logs

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

Network and firewall
Network and firewall
Misconfigurations, exposure, and posture findings across cloud accounts.
Cloud security posture

Cloud security posture
Workloads, images, deployments, and runtime behavior. Approved actions: workload quarantine and deployment rollback where policy allows.
Containers and runtime
Containers and runtime
Containers and runtime
Containers and runtime
Servers, directories, hypervisors, storage, and hybrid dependencies.
On-premises and virtualization

On-premises and virtualization
On-premises and virtualization
On-premises and virtualization
On-premises and virtualization
On-premises and virtualization
Vulnerabilities and exposure, ranked by what an attacker could actually reach.
Vulnerability management
Vulnerability management

Vulnerability management
Availability, performance, and capacity from your monitoring tools, so failures and threats are read together.
Monitoring and observability
Monitoring and observability
Monitoring and observability
Monitoring and observability
Monitoring and observability
Monitoring and observability
Monitoring and observability
Monitoring and observability
Monitoring and observability
Commits, pipelines, infrastructure-as-code changes, and releases tied to live behavior.
Code and delivery
Code and delivery
Code and delivery
Code and delivery
Code and delivery
Database activity, API gateway traffic, and application audit events. Approved actions: aPI throttling and credential rotation through your gateways and vaults.
Databases and APIs
Databases and APIs
Databases and APIs
Databases and APIs
Databases and APIs
Databases and APIs
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.
Workspace and collaboration

Workspace and collaboration
Change records, ownership, and on-call context. Approved actions: cases, approvals, and notifications sent to the teams that own the response.
Service management and messaging
Service management and messaging
Service management and messaging
Service management and messaging
Service management and messaging
Service management and messaging
Service management and messaging
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.
Banking and ATM
Banking and ATM
Banking and ATM
Banking and ATM

Banking and ATM

Banking and ATM
Banking and ATM

Banking and ATM
Banking and ATM
Banking and ATM
Banking and ATM
Network elements, alarms, and service paths from your network management systems, plus USSD, mobile money, and partner links.
Telecommunications
Telecommunications
Telecommunications
Telecommunications
Telecommunications
Telecommunications
Power, UPS, generator, cooling, and building system state behind your infrastructure.
Facilities and power
Facilities and power
Facilities and power
How integrations work
Plan how data is collected, normalized, and related to service context. Configure execution permissions separately for systems that support response.
Link each system, in cloud, on-premises, or both.
Evidence becomes one shared picture of entities and change, with its source and time kept.
Ollandi relates every system to the others and tracks threats, failures, and vulnerabilities as they develop.
A permitted action uses the connected identity, network, endpoint, or workflow system.
What was read, decided, and changed is kept as audit-ready evidence.
Your own systems
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
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.
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.
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.
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.
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
Tell us what you run today, and we will show which systems to connect first and what Ollandi can do with them.