- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
11-15-2022 07:03 AM
Hello,
Looking to set up FIM using the Cortex XDR agent and from what I have found so far, it seems unsupported. Has anyone set up FIM using any method?
The only possible option I have found so far is maybe using an auditbeat with the FIM module:
11-15-2022 09:26 AM - edited 11-15-2022 09:28 AM
Hi @Optimizer , thanks for writing to Live Community.
You are correct, the way to use File Integrity Monitoring with XDR is through BIOC rules, correlations and reports based on XQL.
Please see a few examples below:
1. XQL Based Correlation Rule : Monitor /etc/, usr/local/share/, /usr/share/ for any conf file modifications:
11-15-2022 08:34 AM
Looking into this further. BIOC rules seem to be what I'm looking for, but I am not certain how to set my specific file paths I want to be monitored.
When I test creating my own BIOC rule, I cannot find the files I am looking for in the provided list
11-15-2022 09:26 AM - edited 11-15-2022 09:28 AM
Hi @Optimizer , thanks for writing to Live Community.
You are correct, the way to use File Integrity Monitoring with XDR is through BIOC rules, correlations and reports based on XQL.
Please see a few examples below:
1. XQL Based Correlation Rule : Monitor /etc/, usr/local/share/, /usr/share/ for any conf file modifications:
11-15-2022 10:09 AM
Thank you, this helped a lot!
07-26-2023 08:46 AM
I finally got around to working on this, and... still need to configure some more, but it works.
dataset = xdr_data |filter event_type = FILE and (event_sub_type = FILE_CREATE_NEW or event_sub_type = FILE_WRITE or event_sub_type = FILE_REMOVE or event_sub_type = FILE_RENAME )
|filter action_file_path in ("C:\Program Files (x86)\*","C:\Program Files\*","C:\ProgramData\*") and action_file_name contains ".exe"
|fields agent_hostname, agent_ip_addresses , action_file_name, action_file_path, action_file_type
11-15-2023 04:09 PM
Hi Optimizer,
I'm looking for a solution to meet the 11.5 (FIM) requirement of PCI. Did Cortex XDR BIOC meet your FIM requirements?
03-19-2024 11:42 PM
Dear all,
I'm looking for FIM on Linux (etc/shadow), for the examples are the difference (object before and after) and then the process name like "/usr/sbin/sshd" or "/usr/sbin/userdel". How to show it on XQL Query? Thanks
03-20-2024 01:24 AM
Any solution of that? Thankyou
02-13-2025 01:58 PM - edited 02-13-2025 01:59 PM
The XDR agent doesn't have full FIM coverage. It doesn't calculate the hash after every change, certain paths aren't monitored, and if the host is too active then that can cause file events to not be reported to the tenant's backend database.
You can monitor for processes touching certain directories and can set BIOCs or correlation rules to trigger on file events on certain directories, but it's not 100% coverage. If you have a scrupulous auditor, or an application team that tracks every change made during a change window on a host, there's a good chance it'll end up being a finding on your auditor's report.
If you want full FIM monitoring on linux and use XDR Pro per GB/TB, look into using AuditBeats, specify the directories to monitor, and send that data in via HTTP Collectors. Prisma Cloud's Defender may provide better FIM coverage but I haven't personally tested.
https://www.elastic.co/guide/en/beats/auditbeat/current/auditbeat-module-file_integrity.html
https://docs.prismacloud.io/en/compute-edition/31/admin-guide/install/deploy-defender/app-embedded/c...
Osquery & Fleet are other viable option for FIM as well.
https://osquery.readthedocs.io/en/stable/deployment/file-integrity-monitoring/
https://fleetdm.com/
02-13-2025 02:10 PM
Isn't possible with XQL directly, as it doesn't read the file contents.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!