![]() Consider preventing your Help Desk admins from creating bypass codes for users. No - Do not issue bypass codes to EPCS users. No - Disable SMS use with an Authentication Methods policy No - Disable BlackBerry use with an Operating System policy Yes with Duo Mobile for Windows Phone 2.0 and later Yes with Duo Mobile for Android 3.25.0 and later Meets EPCS compliance for FIPS 140-2 Level 1? For the purpose of EPCS compliance, choose between available authentication methods (OTP, Duo Push, phone call, or hardware token) that meet your compliance team’s interpretation of the Federal EPCS Guidelines. One-time passcodes (OTP) are validated to meet FIPS 140-2 Level 1 per the table below. Read the enrollment documentation to learn more about these options. You'll need to enroll your users ahead of time using directory synchronization, CSV import, or another method. If configured as a "Passive authentication device", or to authenticate "Patient" logons, the Duo device will report an error message and return a failure to Epic.ĭuo Authentication for Epic does not support inline self-enrollment, as Duo Security is not a qualified credential service provider (CSP) or certificate authority (CA) for EPCS identity verification purposes. ![]() It must be installed on all Epic workstations to provide complete protection.ĭuo Authentication for Epic is a "Direct" authentication device capable of "User" authentication only. NET component that provides two-factor authentication for Epic Hyperdrive or Epic Hyperspace 2010 and later (up to and including Hyperspace 2020). Overviewĭuo Authentication for Epic is a client-side. Duo integrates with Epic Hyperdrive and Hyperspace to add two-factor authentication to Epic e-Prescription workflows. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |