AGN1 and AGN2 sit inline on standard Ethernet and export audit logs in open formats. They are not a partner ecosystem — just a hardware control that works with the network gear, SIEM, ITSM, and monitoring you already operate.
A note on the word “integration”
We don't publish a Splunkbase app, a ServiceNow Store entry, or a Cisco Solution Partner badge. AGN1 sits inline on Ethernet — that's the physical-layer compatibility everyone benefits from. Logs export in CEF / JSON over syslog so any SIEM can ingest them. Maintenance windows fire via SMS, so any ticketing tool that can call an HTTP endpoint can drive them. The list below names the tools we have tested or seen customers run alongside us — not certified partnerships.
Category 01
AGN1 / AGN2 sit inline on standard Ethernet — compatible with the switches, firewalls, and routers you already operate.
AGN1 sits on the Ethernet path between any Cisco switch / firewall and the protected asset. No vendor-side configuration required — the relay is electrically transparent during open windows.
Caveat · Compatibility is at the physical Ethernet layer. We are not a Cisco Solution Partner and do not claim a Cisco-certified integration.
Place AGN1 on the LAN-side path past the FortiGate to the protected device. The FortiGate keeps doing what it does; AGN1 removes the path it would otherwise have to gate during closed windows.
Caveat · No Fabric Connector integration. Compatibility is Ethernet-layer; FortiGate logs remain unchanged.
Compatible with PAN-OS firewalls as an inline downstream control. AGN1 closes the line between approved windows — PAN-OS rules remain authoritative when the line is up.
Caveat · Not a Palo Alto NextWave partner. No App-ID, no User-ID coordination — the device operates at the cable layer.
Drop AGN1 inline on Juniper-connected paths the same way as any other vendor's switch. The relay is transparent at L1.
Compatible inline on Aruba access layers. ClearPass identity remains in place during open windows; AGN1 controls whether the line exists for ClearPass to authenticate against.
Category 02
Device audit logs export in standard formats. No proprietary collector required.
Export the device audit log in CEF format from the management port. Ingest as a standard syslog source — no custom Splunk app required.
Caveat · Not a Splunkbase-published app. The log format is documented; the operator owns the pipeline.
Audit log exports as CEF over syslog, parsed by QRadar's standard CEF DSM. Each relay state transition becomes one event.
Forward the device log via a standard Linux collector (Log Analytics agent) to Sentinel. JSON or CEF — both are accepted.
Syslog → Logstash → Elasticsearch pipeline. Pre-baked index template is published with the device documentation.
Category 03
Maintenance windows fire from your existing ticketing flow via SMS — no custom integration to write.
Approved maintenance request in ServiceNow triggers an outbound REST call to an SMS gateway (Twilio, etc.) that opens the AGN1 window with the documented duration.
Caveat · We do not publish a ServiceNow Store integration. The bridge runs on your side (Flow Designer + outbound REST).
Automation rule on ticket-approval emits an SMS via your gateway. Same pattern as ServiceNow — the ticketing tool is the source of truth for who approved which window.
Workflow Automator → outbound webhook → SMS. Works for any ticketing tool that can emit an HTTP POST on ticket transition.
Category 04
Standard SNMP and syslog from the management port — works with whichever observability stack you run.
AGN1 exposes SNMP on the management port. Standard MIB walk gives relay state, last open/close timestamp, and uptime.
SNMP template covers relay state and window history. Trigger on unexpected open or on a missed scheduled close.
Forward device syslog through a Datadog Agent host. Logs are searchable as a standard log source; no custom integration in the Datadog marketplace.
Standard SNMP polling. Useful where SolarWinds is already the OT-side monitoring system of record.
Don't see your tool?
Most stacks already speak SNMP, syslog, or HTTP.
If your tool reads a standard SNMP MIB, ingests syslog, or can fire an outbound webhook on ticket transitions, it works with AGN1. Tell us what you run and we'll point you at the exact integration pattern.