OSDP Verified Products

When you need interoperable, high-security access control solutions, choose products bearing the OSDP Verified mark.

SIA OSDP Verified is a comprehensive testing program that validates that a device conforms to the SIA Open Supervised Device Protocol (OSDP) standard and the related performance profiles.

Use this guide to find and explore products that have been verified to meet the OSDP standards. Devices in this listing have been tested and found to meet the criteria for the standard and the profiles indicated within the listing.

Please note that verification does not automatically mean interoperability – there are still design considerations that an implementer must account for when deploying an SIA OSDP system.

OSDP Profiles

  • Basic: These devices are Wiegand replacements; they provide the supervision benefits of a bidirectional protocol, protecting them from the common person-in-the-middle attacks.
  • Secure: These devices meet the Basic profile but can also handle encrypted messages using Secure Channel and can enter and exit Basic and Secure modes as claimed.
  • Smart card: These devices can handle the transfer of structured data units required for smart card operations, which allows for use in Federal Identity, Credential and Access Management and Personal Identity Verification environments among others.
  • Biometric: These devices can utilize OSDP messages to read and match biometric templates.
BrandModelDevice TypeBasicSecureSmartCardBiometricFile TransferOSDP Standard Version TestedFirmware VersionElectronic Access Control (EAC) SoftwareEAC Name and VersionProduct WebsiteNotes
3millID3MIL-R11325Peripheral Device

Supported2.25.00.41url-iconOUI does not match vendor packaging.
3millID3MIL-R11320Peripheral Device

Supported2.25.00.41url-iconOUI does not match vendor packaging.
3millID3MIL-R11330Peripheral Device

Supported2.25.00.41url-iconOUI does not match vendor packaging.
Alarm.comET10-7WSPeripheral Device

Supported2.23.0 Build 1url-iconOUI does not match vendor packaging
Alarm.comET20-7WSPeripheral Device

Supported2.23.0 Build 1url-iconOUI does not match vendor packaging
Alarm.comET25-7WSPeripheral Device

Supported2.23.0 Build 1url-iconOUI does not match vendor packaging
BrivoB-BSKF-BPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSKF-WPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSMF-BPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSMF-WPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoBSPKF-WPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoBSPKF-WPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSPKF-BPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSPMF-WPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSPMF-BPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSPSF-WPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSPSF-BPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSSF-BPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSSF-WPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSKPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSMPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSSPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSPKPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSPMPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
BrivoB-BSPSPeripheral Device

Supported2.23.0 Build 1url-icon1. OUI does not match vendor packaging.

2. Devices show same model for tri-technology as for dual technology.
Cypress Integration SolutionsOSM-1000Access Control Units

2.21.7-build-15url-icon1. Does not support power failure (osdp_LSTATR)

2. Does not include capabilities that would be tested for an ACU connected to an access control system.
Cypress Integration SolutionsOSM-1000Peripheral Device

2.21.7-build-15url-iconDoes not support power failure (osdp_LSTATR)
EcoStruxure™ Security Expert by Schneider ElectricSecurity Purpose Controllers (SP-C)Access Control Units

2.22.08.1349
Security Expert 4.3.340.1 url-icon1. Commands not supported a. Communication Configuration Report (osdp_COM) b. Communication configuration command (osdp_COMSET)"
EcoStruxure™ Security Expert by Schneider ElectricSecurity Purpose Controllers (SP-C-IP)Access Control Units

2.22.08.1349
Security Expert 4.3.340.1 url-icon1. Commands not supported a. Communication Configuration Report (osdp_COM) b. Communication configuration command (osdp_COMSET)
EcoStruxure™ Security Expert by Schneider ElectricSecurity Purpose Web Controller (SP-C-WEB)Access Control Units

2.24.00.1455
Security Expert 4.00.1455 url-icon1. Commands not supported a. Communication Configuration Report (osdp_COM) b. Communication configuration command (osdp_COMSET)
EcoStruxure™ Security Expert by Schneider ElectricSecurity Purpose Web Controller (SP-C-WEB-IP)Access Control Units

2.24.00.1455
Security Expert 4.00.1455 url-icon1. Commands not supported a. Communication Configuration Report (osdp_COM) b. Communication configuration command (osdp_COMSET)
EcoStruxure™ Security Expert by Schneider ElectricSecurity Purpose Reader Expander Module (SP-DCU)Access Control Units

2.21.12.598
Security Expert 4.3.340.1 url-icon1. Commands not supported a. Communication Configuration Report (osdp_COM) b. Communication configuration command (osdp_COMSET)
EcoStruxure™ Security Expert by Schneider ElectricSecurity Purpose Reader Expander Module (SP-MRDM2)Access Control Units

2.21.12.598
Security Expert 4.3.340.1 url-icon1. Commands not supported a. Communication Configuration Report (osdp_COM) b. Communication configuration command (osdp_COMSET)
EcoStruxure™ Security Expert by Schneider ElectricSecurity Purpose Reader Expander Module (SP-RDM2)Access Control Units

2.21.12.598
Security Expert 4.3.340.1 url-icon1. Commands not supported a. Communication Configuration Report (osdp_COM) b. Communication configuration command (osdp_COMSET)
Deister ElectronicsPRD6Peripheral Device

2.2e93_3.06url-iconPD does not adhere with pending guidance for behavior to commands in clear text while in secure channel
Deister ElectronicsKPD6Peripheral Device

2.2e93_3.06url-iconPD does not adhere with pending guidance for behavior to commands in clear text while in secure channel
Farpointe DataP-300-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataP-403-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataP-405-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataP-410-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataP-453-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataP-455-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataP-500-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataP-530-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataP-620-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataP-640-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataP-710-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataP-900-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataDelta3-OSDPPeripheral Device

2.21.7-build-14url-iconDoes not support power failure (osdp_LSTATR)
Farpointe DataDelta5-OSDPPeripheral Device

2.21.7-build-14url-iconDoes not support power failure (osdp_LSTATR)
Farpointe DataDelta5.3-OSDPPeripheral Device

2.21.7-build-14url-iconDoes not support power failure (osdp_LSTATR)
Farpointe DataDelta6.2-OSDPPeripheral Device

2.21.7-build-14url-iconDoes not support power failure (osdp_LSTATR)
Farpointe DataDelta6.4-OSDPPeripheral Device

2.21.7-build-14url-iconDoes not support power failure (osdp_LSTATR)
Farpointe DataDelta403-OSDPPeripheral Device

2.21.7-build-14url-iconDoes not support power failure (osdp_LSTATR)
Farpointe DataDelta405-OSDPPeripheral Device

2.21.7-build-14url-iconDoes not support power failure (osdp_LSTATR)
Farpointe DataDelta410-OSDPPeripheral Device

2.21.7-build-14url-iconDoes not support power failure (osdp_LSTATR)
Farpointe DataCSR-35L-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataCSR-6.2L-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataCSR-6.4L-OSDPPeripheral Device

2.21.7-build-14url-icon
Farpointe DataSRD PIN ReaderPeripheral Device

2.21.1.8url-icon
HIDSigno 20Peripheral Device

2.25.37url-iconRequires a formula to access serial number (osdp_PDID)
HIDSigno 20KPeripheral Device

2.25.37url-iconRequires a formula to access serial number (osdp_PDID)
HIDSigno 40Peripheral Device

2.25.37url-iconRequires a formula to access serial number (osdp_PDID)
HIDSigno 40KPeripheral Device

2.25.37url-iconRequires a formula to access serial number (osdp_PDID)
ICT PRX-TSEC-MINIPeripheral Device

2.21.04.XXXX (M0C4)url-iconRequires a formula to access version number (osdp_PDID)
ICT PRX-TSEC-STDPeripheral Device

2.21.04.XXXX (M0C4)url-iconRequires a formula to access version number (osdp_PDID)
ICT PRX-TSEC-STD-KPPeripheral Device

2.21.04.XXXX (M0C4)url-iconRequires a formula to access version number (osdp_PDID)
ICT PRX-TSEC-EXTRA-KPPeripheral Device

2.21.04.XXXX (M0C4)url-iconRequires a formula to access version number (osdp_PDID)
ICT PRX-TSEC-EXTRAPeripheral Device

2.21.04.XXXX (M0C4)url-iconRequires a formula to access version number (osdp_PDID)
LenelS2 LNL-R10320-05TBPeripheral Device

Supported2.2 5.00.41url-icon
LenelS2 LNL-R10325-05TBPeripheral Device

Supported2.2 5.00.41url-icon
LenelS2 LNL-R10330-05TBPeripheral Device

Supported2.2 5.00.41url-icon
LenelS2 LNL-R11320-05TBPeripheral Device

Supported2.2 5.00.41url-icon
LenelS2 LNL-R11325-05TBPeripheral Device

Supported2.2 5.00.41url-icon
LenelS2 LNL-R11330-05TBPeripheral Device

Supported2.2 5.00.41url-icon
Safetrust Sabre ModulePeripheral Device

2.2 1.2 Build 8url-icon
Safetrust SA500Peripheral Device

2.2 1.2 Build 8url-icon
Safetrust SA510Peripheral Device

2.2 1.2 Build 8url-icon
Safetrust SA520Peripheral Device

2.2 1.2 Build 8url-icon
Safetrust SA530Peripheral Device

2.2 1.2 Build 8url-icon
EcoStruxure™ Security Expert by Schneider ElectricSmart Card Mini ReaderPeripheral Device

2.21.04.272url-icon1. OUI does not match vendor packaging.
2. Firmware version in PDID requires formula to obtain version number"
EcoStruxure™ Security Expert by Schneider ElectricSmart Card Mullion ReaderPeripheral Device

2.21.04.272url-icon

1. OUI does not match vendor packaging.

2. Firmware version in PDID requires formula to obtain version number.
EcoStruxure™ Security Expert by Schneider ElectricSmart Card Mullion ReaderPeripheral Device

2.21.04.272url-icon1. OUI does not match vendor packaging.
2. Firmware version in PDID requires formula to obtain version number.
EcoStruxure™ Security Expert by Schneider ElectricSmart Card Wallplate ReaderPeripheral Device

2.21.04.272url-icon1. OUI does not match vendor packaging.
2. Firmware version in PDID requires formula to obtain version number"
EcoStruxure™ Security Expert by Schneider ElectricSmart Card Wallplate Reader with KeypadPeripheral Device

2.21.04.272url-icon1. OUI does not match vendor packaging.
2. Firmware version in PDID requires formula to obtain version number.
Schlage MTB11Peripheral Device

Supported2.260.47.23url-icon
Schlage MTKB15Peripheral Device

Supported2.260.47.23url-icon
Schlage MTB15Peripheral Device

Supported2.260.47.23url-icon
STid ARCS-A/BTPeripheral Device

Supported2.212url-icon
STid ARCS-B/BTPeripheral Device

Supported2.212url-icon
STid ARCS-C/BTPeripheral Device

Supported2.212url-icon
STid ARCS-D/BTPeripheral Device


Supported2.212url-icon
STid ARCS-I/BTPeripheral Device

Supported2.212url-icon
STid ARCS-J/BTPeripheral Device

Supported2.212url-icon
STid ARCS-IM/BTPeripheral Device

Supported2.212url-icon
STid ARCS-JM/BTPeripheral Device

Supported2.212url-icon
STid ARCS-AQ/BTPeripheral Device

Supported2.212url-icon
STid ARCS-BQ/BTPeripheral Device

Supported2.212url-icon
STid ARCS-CQ/BTPeripheral Device

Supported2.212url-icon
STid ARC1S/BTPeripheral Device

Supported2.212url-icon
Suprema XPD2-GKDBPeripheral Device

2.2 1.5 Build 0url-icon
Suprema XPD2-GDBPeripheral Device

2.2 1.5 Build 0url-icon
Suprema XPD2-MDBPeripheral Device

2.2 1.5 Build 0url-icon
Third MillenniumRX190Peripheral Device

Supported2.25.00.44url-icon
Third MillenniumRX1K90Peripheral Device

Supported2.25.00.44url-icon
Third MillenniumRX290Peripheral Device

Supported2.25.00.44url-icon
Third MillenniumRX390Peripheral Device

Supported2.25.00.44url-icon
Third MillenniumRX3K90Peripheral Device

Supported2.25.00.44url-icon
Third MillenniumRX490Peripheral Device

Supported2.25.00.44url-icon
Third MillenniumRX590Peripheral Device

Supported2.25.00.44url-icon
Third MillenniumRX5M90Peripheral Device

Supported2.25.00.44url-icon
WaveLynx TechnologiesEthos ET10Peripheral Device


Supported2.23.0 Build 1url-iconDoes not support osdp_GenAuth for Smartcard Profile
WaveLynx TechnologiesEthos ET20Peripheral Device


Supported2.23.0 Build 1url-iconDoes not support osdp_GenAuth for Smartcard Profile
WaveLynx TechnologiesEthos ET25Peripheral Device


Supported2.23.0 Build 1url-iconDoes not support osdp_GenAuth for Smartcard Profile
HID MercuryLP1501Access Control Units

Supported2.21.29.4url-icon1. Reader communication resets if default autoconfiguration active.

2. ACURXSIZE specifies an invalid value.

3. ACU ignores a NAK on sequence zero and fails to reset the sequence.
HID MercuryLP1502Access Control Units

Supported2.21.29.4url-icon1. Reader communication resets if default autoconfiguration active.

2. ACURXSIZE specifies an invalid value.

3. ACU ignores a NAK on sequence zero and fails to reset the sequence.
HID MercuryLP2500Access Control Units

Supported2.21.29.4url-icon1. Reader communication resets if default autoconfiguration active.

2. ACURXSIZE specifies an invalid value.

3. ACU ignores a NAK on sequence zero and fails to reset the sequence.
HID MercuryLP4502Access Control Units

Supported2.21.29.7url-icon1. Reader communication resets if default autoconfiguration active.

2. ACURXSIZE specifies an invalid value.

3. ACU ignores a NAK on sequence zero and fails to reset the sequence.
HID MercuryMR50-S3Access Control Units

Supported2.23.21.12url-icon1. Reader communication resets if default autoconfiguration active.

2. ACURXSIZE specifies an invalid value.

3. ACU ignores a NAK on sequence zero and fails to reset the sequence.
HID MercuryMR52-S3Access Control Units

Supported2.23.21.12url-icon1. Reader communication resets if default autoconfiguration active.

2. ACURXSIZE specifies an invalid valu.

3. ACU ignores a NAK on sequence zero and fails to reset the sequence.
HID MercuryMR62eAccess Control Units

Supported2.23.21.12url-icon1. Reader communication resets if default autoconfiguration active. 2. ACURXSIZE specifies an invalid value 3. ACU ignores a NAK on sequence zero and fails to reset the sequence.
HIDHID Aero X1100Access Control Units

2.23.21.12url-icon1. Reader communication resets if default autoconfiguration active. 2. ACURXSIZE specifies an invalid value 3. ACU ignores a NAK on sequence zero and fails to reset the sequence.
HIDHID Aero X100Access Control Units

2.23.21.12url-icon1. Reader communication resets if default autoconfiguration active. 2. ACURXSIZE specifies an invalid value 3. ACU ignores a NAK on sequence zero and fails to reset the sequence.
HoneywellPW7K1ICAccess Control Units

2.21.30.2.0665
Pro-Watch 5.5.0.12710url-icon1. Commands not supported
  1. Power Failure Status request (osdp_LSTAT)
  2. Input Status request (osdp_ISTAT)
  3. Output Status request (osdp_OSTAT)
  4. Output control command (osdp_OUT)
2. Communication configuration command is not able to manually configure an existing PD to new communication settings (osdp_COMSET)

3. Rotate security keys requires controller reset (osdp_KEYSET)

4. Limited to 1 device for OSDP port

5. CRC only used by ACU in Secure Channel mode

6. Bad CRC or osdp_BUSY responses will cause the ACU to reinitialize the connection
HoneywellPW7K1R2Access Control Units

2.23.21.13
Pro-Watch 5.5.0.12710url-icon1. Commands not supported
  1. Power Failure Status request (osdp_LSTAT)
  2. Input Status request (osdp_ISTAT)
  3. Output Status request (osdp_OSTAT)
  4. Output control command (osdp_OUT)

2. Communication configuration command is not able to manually configure an existing PD to new communication settings (osdp_COMSET)

3. Rotate security keys requires controller reset (osdp_KEYSET)

4. Limited to 1 device for OSDP port

5. CRC only used by ACU in Secure Channel mode 6. Bad CRC or osdp_BUSY responses will cause the ACU to reinitialize the connection
ZKTecoAtlas 100Access Control Units

2.23.1.4-2022-04-21-061637url-icon
ZKTecoAtlas 200Access Control Units

2.23.1.4-2022-04-21-061637url-icon
ZKTecoAtlas 400Access Control Units

2.23.1.4-2022-04-21-061637url-icon
ZKTecoAtlas 160Access Control Units

2.23.1.4-2022-04-21-061637url-icon
ZKTecoAtlas 260Access Control Units

2.23.1.4-2022-04-21-061637url-icon
ZKTecoAtlas 460Access Control Units

2.23.1.4-2022-04-21-061637url-icon
Iris AccessiCAM7000SPeripheral Device

2.28.22.10url-icon
Iris AccessiCAM7010SPeripheral Device

2.28.22.10url-icon
Iris AccessiCAM7101SPeripheral Device

2.28.22.10url-iconosdp_TEXT command only works for temporary text. A parameter NAK is returned if you attempt to use permanent parameters.
Iris AccessiCAM7111SPeripheral Device

2.28.22.10url-iconosdp_TEXT command only works for temporary text. A parameter NAK is returned if you attempt to use permanent parameters.

Ready to Get Verified?

Learn more about the OSDP verification process, get pricing information for the program and start your application here.

Get Started