This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
Traps false positive
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- Discussions
- Cloud Delivered Security Services
- Endpoint (Traps) Discussions
- Re: Traps false positive
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
Traps false positive
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
03-07-2019 06:34 AM
Hi,
We are having an issue with a file. This file can have several hashes so its not possible to click in "treat as benign", besause the has file changes. SO what is the correct way to permit this file?
Thanks
10 REPLIES 10
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
03-07-2019 06:38 AM
If the file is in a set location you could simply whitelist the file itself via the file path, or if this is an in-house application EXE/DLL file you could have your developers sign the application so you can whitelist it based off of the signing certificate.
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
03-07-2019 06:43 AM
How can we do that: If the file is in a set location you could simply whitelist the file itself via the file path?
The issue is that, WF lasts 10 minutes in permit the access to this file, so end-users first receive denied access, and then in 10 minutes end-user can open the file. But all en users open a ticket about this issue.
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
03-07-2019 06:45 AM
Directions differ based on the version of Traps you are using. Are you using the hosted Traps Management Service or are you still running the on-site Endpoint Security Manager?
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
03-07-2019 06:46 AM
If the file name changes, you can whitelist the file path (with env. varablies if needed), and use a wildcard (*) for the file name. If the file name does not change, it would be advised to include the file name.
Related Content
- ms-ds-smbv3 - Trojan-Downloader/Win32.guloader.ao in Threat & Vulnerability Discussions
- False positive - Threat ID 86672 - NewPOSThing Command and Control Traffic Detection in Threat & Vulnerability Discussions
- Potential false positive AV for MS VisualStudio update in Threat & Vulnerability Discussions
- False Positive in Threat & Vulnerability Discussions
- False positive - Atlassian Confluence Remote Code Execution Vulnerability 92632 in Threat & Vulnerability Discussions
Like what you see?
Show your appreciation!
Click Like if a post is helpful to you or if you just want to show your support.
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!
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks