Connect ChatGPT or Claude. Exchange data with your business systems. Monitor workstations and servers with Wazuh.
This page explains how each connection works, what it can do, and where your people remain in control.
Ask questions, find records and prepare updates from the AI assistant you already use. InfoPol controls what the assistant can see and do.
How AI access works ↓Send data to and from your HR, ticketing, workflow, document and security tools using APIs, webhooks and scheduled jobs.
How integrations work ↓Use Wazuh to monitor workstations, servers and cloud workloads. Run it yourself or ask us to operate it for you.
How security monitoring works ↓Yes. InfoPol provides an MCP connection for AI assistants.
MCP is a standard way for an AI assistant to use approved tools and data. After connecting InfoPol, you choose which team the assistant can access and which actions it may perform.
There is no separate copy of your compliance data for the AI. The assistant works with the same risks, controls, tasks, evidence, documents and incidents that your team sees in InfoPol.
It can do the preparation work:
It cannot approve its own work.
A named person must approve each proposed change before it becomes part of the record. An assistant cannot close a task, mark a control as fully implemented or sign an attestation on your behalf.
No.
Each connection acts as one user in one team. It receives only the permissions and tools enabled for that connection. The same database-level tenant isolation used by the InfoPol application still applies.
Sessions are short-lived. Every action is recorded in a tamper-evident audit log.
In most cases, yes.
If a system has an API, supports webhooks or can make an HTTPS request, it can exchange data with InfoPol. That covers most modern HR, ticketing, workflow, document, reporting and security systems.
You do not need to replace the tools your teams already use.
Read or update InfoPol records from another application.
Send an event, file or status update into InfoPol when something happens elsewhere.
Notify another system when an InfoPol record changes or needs attention.
Let a user grant an application limited access without sharing a password.
Give a server or scheduled job access to one team and an explicit set of operations.
Let ChatGPT, Claude and other compatible AI tools use approved InfoPol actions.
Start recurring reviews, checks and evidence requests automatically.
Send notifications without introducing another application.
A ticket created in your service desk can open a task in InfoPol. Progress can be sent back to the service desk, while final approval remains in InfoPol.
A deployment pipeline can attach a configuration export or test result to the correct control and assign it to someone for review.
Your HR or directory system can keep members, roles, organisational units and job roles up to date.
InfoPol can start a review or evidence request on schedule and notify the workflow system your team already uses.
Every credential is limited to a specific team and set of operations.
Inbound requests are authenticated. Outbound webhooks are signed, logged and designed to be retried without creating duplicate work. Automated changes follow the same approval rules as changes proposed through MCP.
Every accepted change is recorded in InfoPol’s audit log.
Usually, very little:
For ordinary business-system integrations, there is no InfoPol agent to install and no need to redesign your database.
If an older system has no usable API or webhook support, we can build a small adapter for it. We agree on the scope and price before building anything.
Connections using InfoPol’s standard interfaces are included in the service.
Custom work is only needed when a system has no standard way to exchange data. If that happens, we explain what must be built and provide a price before work starts.
Yes, if you need security monitoring as part of the service.
We use Wazuh, a free and open-source security monitoring platform for endpoints and cloud workloads. It collects security events from workstations and servers and brings them into one place for investigation.
When something needs attention, it can become an incident, a piece of control evidence or an assigned task in InfoPol.
The Wazuh software is open source. You pay for the setup and operational service you choose, not for a per-device SIEM licence.
Your data and detection rules remain yours. Wazuh can run on your infrastructure, in your cloud account or in an environment hosted for you.
Wazuh is used by organisations of different sizes and has a large public community. Its source code and documentation are publicly available.
A security alert does not have to remain in a separate dashboard. InfoPol can turn it into work with an owner, evidence and an audit trail.
Wazuh runs on your hardware. You decide what, if anything, is forwarded to InfoPol.
We deploy it into your AWS, Azure or Google Cloud environment. Your account, your keys and your region.
We operate the central Wazuh environment and agree with you where the data is stored and how long it is retained.
Your own security team can operate Wazuh, or InfoPol can provide the managed service.
The managed option can include:
Wazuh is the monitoring technology. The managed service is the people and process around it.
If your scale or detection requirements later call for Elastic Security, we can change the monitoring platform while keeping the same InfoPol process for incidents, evidence and assigned work.
We will tell you what connects directly, what needs configuration, whether anything requires custom work and what it will cost.