Mobile Guard

The ‘MobileGuard/Mob8’ App turns your Android phone into a mobile QR-code/Mifare card reader. By linking with GuardPoint 10 compatible access control systems (ACS), MobileGuard enables real-time monitoring of your users. You can perform access card and/or QR code validation on-the-move. Scanning a user’s badge/card provides: photo, location and validation details - allowing you to conduct impromptu spot-checks and update users into their correct location (Mobile Check-in). You can use MobileGuard to confirm the location of individuals during an evacuation, ensuring that everyone is accounted for and safe (Fire Mustering). The application can operate in an offline mode, using a per-downloaded database snap-shot. This allows MobileGuard to be used in instances where network connectivity is unavailable for example on coach trips or at festivals. Additional Features: Random Spot Check - for indiscriminate cardholder selection. Manual Relay Firing - for manually opening doors (forgotten cards etc.) Card Technologies Supported • 13.56MHz RFID/Proximity cards (via external or NFC-enabled mobile reader) • Mifare Desfire (contact Sensor Access on how to add your own unique company read key and security profile) • 125khz Proximity cards (via an external reader) • 32bit QR-Code Tickets/Temporary Passes Mobile device’s NFC fields vary in strength depending on the device/device cover. For high volume environments, using an external USB-C reader is recommended. Security Features Access Control Systems will often contain sensitive personal information. MobileGuard provides the following data-protection mechanisms: Application settings are protected by an additional biometric prompt, when available. When MobileGuard is used in production environments, we recommend using a secure 2-factor authenticated encrypted connection to the ACS. MobileGuard supports cryptographic keys from the device’s internal keystore (Android StrongBox/Software Keystore) to achieve 2-factor (Device key and Password) authenticated secure connections. The server must be setup to enforce client certificate authentication (mTLSv1.2/mTLSv1.3). Note: MobileGuard operates differently to a door reader since it does not need a controller and reader to operate. MobileGuard will not perform a access transaction. Instead it updates the Cardholders Area field, places a timestamp in the Cardholders custom field - cF_DateTimeField_5 and in-addition can optionally add a log entry within the Audit Log.