Skip to main content
Skip table of contents

(LRCloud Only) Initialize the Duo Beat Using Cloud to Cloud Collection

This document explains how to initialize the Duo Beat after configuration. This is available to LRCloud customers only.

Prerequisites

Before initializing Duo Beat, do the following:

  • Make sure that the customer is an LRCloud customer and has their environment hosted.
  • Check if the Open Collector has been installed in the customer's LRCloud environment on a separate instance. If not, an Open Collector instance must be requested via a support case. 
  • Ensure that the Open Collector log source has been accepted and configured for log source virtualization.
  • Check and make sure that you have Duo Admin API credentials. If you have not already configured it, follow the instructions in Configure Duo Admin API for Duobeat.
  • Check if any service is configured with Duo for authentication to get authentication logs.

Apply the Log Source Virtualization Template  

  1. Log in to the Client Console in Cameyo.
  2. Click Deployment Manager from the toolbar.
  3. Click the Log Sources tab.
  4. Double-click the required Open Collector Log Source (such as, {instance}-opencollector.c.e3-hub-753dd405.internal Open Collector).
    The Log Message Source Properties window appears.
  5. Click the Log Source Virtualization tab. 
  6. If not checked, select the Enable Virtualization check box. 
  7. Click Create Virtual Log Sources.
    The Create Virtual Log Sources dialog box appears. 
  8. In the Virtual Log Sources menu, check the Action check box corresponding to "Syslog - Open Collector - Duo Authentication Security" and "Syslog - Open Collector - DuoBeat Heartbeat" log source types.
  9. Click  Save.
    The Virtual Log Source(s) created prompt appears.
  10. Click Ok.
  11. Click Apply. 
  12. Click Ok.
    The new Log Sources will appear in the grid as children of your parent log source. 
  13. Click the System Monitors tab. 
  14. Select the Action check box corresponding to the (customerid)-dpawc agent. 
  15. Right-click the selection, click Actions and then click Service Restart. 

Initialize the Beat 

  1. Log in to the Web Console as a Restricted Administrator User.
  2. On the top navigation bar, click the Administration icon and select Cloud Log Collection.
  3. At the top of the Cloud Log Collection page, click New Log Source.
    The New cloud log collection dialog box appears.
  4. Select the Duo Beat - Open Collector tile.
    The Add Duo Beat Log Source window appears.
  5. Enter the following details:

    Setting

    Description

    Setting

    Description

    NameEnter the name for this log source.
    Description (Optional)Enter a description for this log source.
    HostnameEnter the DUO Hostname (for example, api-abcd1234.duosecurity.com).
    Integration KeyEnter the DUO Integration Key (for example, 01234ABCDE01234ABCDE).
    Secret KeyEnter the DUO Secret Key (for example, 01234abcdeABCDE01234abcdeABCDE01234abcde).
    Logtype List

    Enter the name of logs that need to be fetched from Duo. By default, the supported log types collected are Admin, AuthLog, and TelephonyLog.

  6. Click Save.
  7. Log in to the Client Console in Cameyo.
  8. Click Deployment Manager from the toolbar.
  9. Click the System Monitors tab. 
  10. Select the Action check box corresponding to the dpwac agent.
  11. Right-click the selection, click Actions and then click Service Restart.

A new log source is created with the provided information based on the virtualized log source that was already created. Collection should start automatically in few minutes.

The Open Collector hosts the log sources. It is recommended to create a new host entity and move the log source to the new host which is done in the log source properties screen and not from the log source grid.

For security, the values entered are encrypted using LRCrypt.

Default Config Values for Duo Beat

Setting

Field Name

Default Values

1heartbeatinterval60s
2heartbeatdisabledfalse
3period

40s

4numbackdaysData

0

5

logTypeList

AuthLog, AdminLog,TelephonyLog
6limit

1000

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.