Skip to main content
Skip table of contents

Integrate LogRhythm and McAfee ePolicy Orchestrator

  1. Configure VirusScan Enterprise for ePO notifications. If your site requires deployment of VirusScan Enterprise 8.5 to the LogRhythm XM or EM server that hosts the LogRhythm Alarming and Response Manager (ARM), your ePO administrator must take steps to ensure that VirusScan does not block LogRhythm’s ePO alarm notifications. To prevent blocking, follow the ePolicy Orchestrator documentation to create a VirusScan policy exception for the LogRhythm ARM and apply that policy exception to the LogRhythm XM (or EM) system. The policy exception parameters are shown here:
    • Product. VirusScan Enterprise 8.5.0

    • Category. Access Protection Policies

    • Access protection rules:

      • Categories. Common Standard Protection

      • Block/Report/Rules. Prevent modification of McAfee Common Management Agent files and settings

    • Rule Details. Processes to exclude. scarm.exe
  2. Follow the instructions in McAfee’s ePolicy Orchestrator (3.64.04.55.05.1, or 5.3) documentation to deploy the McAfee Agent to the LogRhythm XM or EM system that hosts the LogRhythm Alarming and Response Manager (ARM).
  3. Download the LogRhythm ePO Server Extension from the LogRhythm Community.
  4. Install the LogRhythm ePO Server Extension. 
    1. Start the McAfee ePO console.

    2. Click Configuration.

    3. Click Extensions.

    4. Click Install Extension located at the bottom of the Extensions panel.

    5. In the Install Extension dialog box, click the Browse button and go to the LogRhythmExtension.zip file.

    6. Select the file.

    7. Click OK
      The ePO Console displays information about the LogRhythmAlarmEvents extension.

    8. To install the extension, click OK.

  5. Configure LogRhythm to send alarm notifications to ePolicy Orchestrator.
    1. Ensure the Notification Engine is enabled.
      1. On the main toolbar, click Deployment Manager.

      2. Click the Platform Manager tab.

      3. In the Alarming, Reporting, and Response Manager Services section, click the Properties button.

      4. Select the check box next to Enable Alarming Engine.

      5. Click OK.
    2. Do one of the following:
      • Add ePO Notification to an existing user account or role.
        1. Click the People tab.

        2. To open the Person Properties dialog box, double-click a user account or role in the list.

        3. Select ePolicy Orchestrator Event from the Contact Method Type list and click Save
          Contact information is not required for ePO notification because the McAfee Agent automatically communicates events to the ePolicy Orchestrator server.

        4. Click OK.

      • Create a separate role for ePO notification.
        1. Click the People tab.
        2. Right-click the list of people, and then click New.
          The Is Person an Individual? dialog box appears.

        3. Click No because the new account is for a role and not for an individual.

        4. Enter a Display Name for the new role, such as McAfee ePO Notification.

        5. Select ePolicy Orchestrator Event from the Contact Method Type list and click Save. Contact Information is not required for ePO notification because the McAfee Agent automatically communicates events to the ePolicy Orchestrator server.

        6. Click OK.
    3. Add ePO notification to an alarm rule.
      1. On the main toolbar, click Deployment Manager.

      2. Click the Alarm Rules tab.

      3. To open the Alarm Rule window, double-click an alarm rule in the list.

      4. Click the Notify tab.

      5. On the top of the window, click Add Person.
        The Person Selector window appears.

      6. Make a selection in the Person Record Type filter box to populate the Person list.

      7. Select the person or role you created for ePO notification.

      8. Click OK.
        You return to the Alarm Rule window.

      9. Click the Information tab to enable the OK button.

      10. Click OK.
JavaScript errors detected

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

If this problem persists, please contact our support.