Hardware state changes, including contact sensor, REX, generic inputs, and tamper detection
Entry events, including anti-passback breaches, successful and denied unlock attempts, and forced or propped open entries
Lockdown plan trigger and revert attempts
Set up is easy using the basic Openpath Rules Engine — generate a token in Splunk, then create a rule for each Openpath event type you’d like to send to Splunk. New events will be sent to the Splunk platform, where you can search and gain insight for your business.
Monitor security breaches. Easily track vulnerabilities and issues like forced and propped open doors, anti-passback misuse, and hardware tampering.
Evaluate entry traffic. In addition to collecting Openpath reader badge-in and badge-out events, you can also track usage of doors not associated with readers by importing REX and contact sensor state change events to Splunk.
Track lockdown usage. At a glance, see who is triggering and reverting lockdown plans, which lockdown plans are being used more than others, and how often they’re being used.
Gain insight into your Openpath data. See who is accessing your entries and when; see what credential methods they’re using, and whether they’re onsite or remote.
Make informed decisions. By ingesting Openpath data in Splunk, you can evaluate and analyze all of your business data in one place, wherever you are, and on whatever device.
