Showing results for 
Search instead for 
Did you mean: 
Level 7
Report Inappropriate Content
Message 1 of 1

Design question: Parsing and forwarding detailed ePO events

I am investigating an (apparently authoritative) claim that "by design" ESM cannot produce a detailed parse of ePO events for forwarding to an external system.

e.g. consider a Malware alert event (576-1290). ePO provides fields "Target Hash", "Target Path", "Target File Size (Bytes)" and others which do not seem to be present in the ESM event.

Unfortunately I do not have access into the originating ePO/ESM ecosystem to validate, however having dealt with a number of top-tier SIEM/Logging products over the years (albeit not ESM/Nitro specifically), I am finding this advice somewhat dubious. Calling out to the community to get an expert position around the voracity of these claims.

Please feel free to reach out if you require further detail (versions, etc.)

Thanks in advance.

More McAfee Tools to Help You
  • Subscription Service Notification (SNS)
  • How-to: Endpoint Removal Tool
  • Support: Endpoint Security
  • eSupport: Policy Orchestrator
  • Community Help Hub

      New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

    • Find Forum FAQs
    • Learn How to Earn Badges
    • Ask for Help
    Go to Community Help

    Join the Community

      Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

    • Get helpful solutions from McAfee experts.
    • Stay connected to product conversations that matter to you.
    • Participate in product groups led by McAfee employees.
    Join the Community
    Join the Community