XWatch never changes your systems
If you allow it, it only acknowledges and comments in Zabbix. It changes nothing on your servers or network devices.
XWatch · live · sample data
- Taken by Selin Demir (SMS reply)
- Ticket INC0010001 opened
XSecure offers four AI agents for network monitoring, security, IT operations and compliance. XWatch (the monitoring agent) follows your systems in real time without touching your infrastructure; when something needs action, the agents concerned ask for your approval first. Every step is recorded in your portal.
XWatch · incident INC-6 · a real run in our lab, sample data · other agents coming
An alarm arrives and XWatch runs the playbook you drew. It calls the on-call person, moves to the next if no one answers, sends SMS and opens the ITSM ticket. Every step is recorded to the second.
What an agent may touch, whom it tells, what it asks you first: all written down in your portal, every step on record.
If you allow it, it only acknowledges and comments in Zabbix. It changes nothing on your servers or network devices.
XWatch · live · sample data
It writes what it wants to do, why, and how to undo it; you approve or reject. Requests left unanswered go to the XSecure SOC team.
XOperate and the approval queue · coming · example screen
fs-02: delete 6 backups older than 30 days to free space
Approved by A. Demir · 08:41 · backup taken again
Who, what, on what, why, and the result. Every XWatch step is recorded in your portal today; the other agents write to the same trail as they arrive. We hand over a full export whenever you ask.
Activity log · XDefend, XOperate, XComply coming · sample data
XOperate · 13/14 backups OK; fs-02 failed, ticket opened
XWatch · Selin Demir took the incident by SMS reply
XDefend · On-call did not answer; incident handed to the XSecure SOC
A. Demir · Approved the XOperate request
XComply · Evidence missing for A.5.18; reminder sent
XDefend calls your on-call security team. If no one answers, the incident goes to the XSecure SOC.
XDefend · coming · sample data
It calls the on-call person, moves to the next if no one answers, sends SMS, and opens the ITSM ticket once someone takes it. Grouping an alarm storm into one incident with AI is coming.
It weighs SIEM and EDR alarms together and brings the user, the device and the last 24 hours into one view. It opens the security ticket and calls the on-call team. If no one answers, it hands the incident to the XSecure SOC.
It checks backups and patches, writes down the cause when something fails, opens a ticket and tells the team. If it needs to change anything on your systems, it asks for your approval first.
It collects evidence for ISO 27001 and KVKK controls from the other agents’ records and your systems. It finds gaps, reminds the owner and produces an audit-ready report. It gives no legal advice.
A separate portal and a separate database for every client.
Password plus Google or Microsoft Authenticator, always.
Read-only, operator, administrator. You manage your users.
Encrypted every night, kept 30 days, a restore drill every month.
Let’s talk about your environment and your team’s workload, and agree in writing which agent works within which limits.
Or write to us directly: advisory@xsecure.com.tr
XSecure installs and runs them. You connect the integrations, set each agent’s limits and approval policy, and see every step in your portal.
XWatch works today: it takes the Zabbix alarm, calls your team, sends SMS and opens the ticket. XDefend, XOperate and XComply are coming; their screens on this page are sample data.
XWatch does not; if you allow it, it only acknowledges and comments in Zabbix. Agents that will change something write what, why and how to undo it, and act through the approval queue with your approval.
The next step of the playbook runs: the next person is called, SMS goes out, and if your playbook has a hand-over, the incident goes to XSecure. Approval requests left unanswered go to the XSecure SOC team.
You create the users: read-only, operator or administrator. Each user sets their own password, and two-step sign-in with Google or Microsoft Authenticator is required.
Every client has its own portal and its own database; nothing is shared with another client. It is backed up encrypted every night, kept 30 days, and a restore is tested every month.
XWatch works today. Let’s talk about your environment and draw the first playbook together.