Active Directory and LDAP integration
You do not need to keep a separate user list for corporate users; the identity is already on the directory server.
A next-generation firewall that applies the same policy set at every scale, from a branch office to a data center. Every model runs the same operating system; a rule you write at a branch behaves exactly the same way at the data center.
Identity verification on the guest network and signed access logging. It carries the same feature set as the Firewall; 802.1x and IPS/IDS are not included in this product.
A plug-and-play tunnel device that connects a branch to the central site at Layer 2. No separate configuration is needed; the settings are made through the XLOG Firewall and the customer portal.
A Layer 2 tunnel that carries the internet traffic of branches in different locations to the central site with VLANs (tagged/untagged). It works independently of your existing firewall brand.
The firewall, hotspot, logging and 802.1x all run on the same device; no separate server, no separate box and no extra license.
Connect your branches to the central site over a Layer 2 tunnel and run them as a single network; both the policy and the access logs are gathered centrally.
Combine more than one line so that another takes over when one drops, and keep a second device on standby against hardware failure.
Identify the guest through the hotel management system, grant room-based access and keep the record compliant with regulation.
Know who joined the network, with which device and when; write your rules per user and per group.
Manage a multi-location network with a single policy set across public institutions, municipalities and professional bodies.
A partnership program for software and hardware companies that build technical integrations with XLOG devices. Integration points are defined at the authentication, management and logging layers.
Marketing support offered to our resellers and technology partners: content, events and promotional materials are requested from a single point.
From public institutions to universities and from hospitals to industrial companies, a great many organizations build their networks with XLOG and keep their access logs signed on the device itself.
Access online setup, configuration and management guides for your products. Step-by-step instructions and screenshots get your device up and running quickly; use search to jump straight to a topic. The documentation is published in Turkish.
You can open a support request for your installed XLOG systems. Sharing the device model and serial number shortens the resolution time; requests are prioritized by urgency level.
Training runs on the device you have deployed: configuration, day-to-day administration and troubleshooting are covered hands-on in the same interface. You can attend in person in Isparta or online.
An IP address does not tell you who someone is. XLOG identifies the user through Active Directory and LDAP, the hotspot portal or 802.1x MAC control; it filters the device before it joins the network, ties the rule and the quota to the user, and keeps the record with the username and MAC address.
On a network without identity, both the rule and the record hang off an IP address: when the address changes, who did what is lost. With identity-based access, a username and a MAC address stand behind every session; whether you are writing a rule or searching a record, what you are looking for is the person.
A corporate user is registered in the directory, a guest is not; devices such as printers or cameras have no user at all. XLOG solves all three cases on the same device with separate identity sources; the methods can be used together.
You do not need to keep a separate user list for corporate users; the identity is already on the directory server.
Filtering the device before it joins the network rather than restricting it afterwards. With managed switch integration, client devices are blocked or filtered at the edge.
There is no directory record for guests and rotating users; verification happens at the captive portal. Once verified, the user goes online and their records are kept signed.
RADIUS MAC filtering filters the device at the edge, before it joins the network; hotspot and Active Directory verification identify the user after the device has joined. The two points do not replace one another, they complete one another.
| Method | What it verifies | Where it works | Typical user |
|---|---|---|---|
| Active Directory / LDAP | The corporate user's identity through the directory | The corporate network; with AD Agent on Windows PCs | Staff |
| 802.1x MAC control | Whether the device is authorized to join the network | On the managed switch, at the edge | Fixed devices |
| RADIUS MAC filtering | Whether the MAC address is on the allow list | On Layer 2 and Layer 3 networks with switch integration | Printers, cameras, terminals |
| Hotspot verification | The person, with an ID number, username and password or SMS | Through the captive portal | Guests |
| Layer 2 filtering | A client trying to connect from the internal network, with admin approval | On the internal network, on the device | A newly defined device |
Once the user is identified, the rule is no longer written for an IP range but for a person or a group. Speed, quota, filter profile and port permission are all bound to the same identity.
Group-based rules can be created; the rules you choose apply to the groups you choose.
Download and upload speed is defined per user or per MAC address, distributing internet speed as needed.
A quota can be defined; the internet activity of a user who exceeds the quota is cut off by the system. Daily usage is recorded and can be listed by date range.
System administrators can grant users with access permission the right to open a timed port to their own IP; the port closes automatically when the time is up.
Currently active users on the system and their quota usage are listed; devices generating excessive traffic are shown at the top.
With the detailed reporting feature, internet records can be searched by MAC address, source IP, destination IP, username, destination port, domain and date. The internet login and logout times of users who signed in through the hotspot can be listed.
Currently active users on the system and their quota usage are listed as well. Logins to the XLOG system are recorded separately; in other words, who manages the network is on the record too.
Share how many users you have, whether you use Active Directory and whether you offer guest access; let us work out the verification design together.