Traps for Mac and Jamf Pro (casper) Policy Issues

Reply
L1 Bithead

Traps for Mac and Jamf Pro (casper) Policy Issues

Just curious if anyone with Traps for Mac deployed in there enviroment and has JAMF Pro/Casper are experiencing policy deployment issues.  We recently rolled out traps for mac and found that some jamff policys that contain scripts such as bash scripts to custom unix executables to perform unattended installations, Traps for mac would pause/halt the unix process and the unix process would never finish.  No log entries are send to the Traps server indicating the pause/halt on the client computer.  We are currently attempting to figure out why and a way to whitelist the jamf binary and all spawned off process as known good on the traps server if possible to stop the client side pause/halt.

 

Any suggestion would be greatly appreciated.

L3 Networker

Re: Traps for Mac and Jamf Pro (casper) Policy Issues

We deployed Traps 4.0.0, 4.0.1, 4.0.2, and 4.0.3 to MacOS machines enrolled in Jamf. We have not run into issues you are discribing since we don't have any custom bash scripts for unix executables. 

 

Could you Catelog all of your hashes of your custom executables? Whitelist in hash control? 

 

Are you saying you're getting no security alerts from ESM? 

L4 Transporter

Re: Traps for Mac and Jamf Pro (casper) Policy Issues

Since you describe this issues as part of your deployment process, would it be possible to move traps to the end of the deployment (post local system changes)? or set a condition for the install to validate before it proceeds?

 

If part of the image that is deployed to the system, Collecting the Jamf binaries (with path), and support file from the endpoint agent, should help the support team assist with creating the proper rule for your macs and enviorment.

L1 Bithead

Re: Traps for Mac and Jamf Pro (casper) Policy Issues

@mmelone- thanks for the advice.  I do not have access to make any changes or see any changes on the ESM in anyway.

 

I have escalated my issue to my internal networking team who manages this product for my company.  From what my networking team has relayed to me.  The executable does not get evaluated by the ESM and no log of the issue or interaction with the specific client is sent to the ESM so whitelisting in hash control seems impossible unless there is a manual way of doing it. We get no alarms from the client or alerts on ESM from what I am aware of from our networking team.

L1 Bithead

Re: Traps for Mac and Jamf Pro (casper) Policy Issues

@efrancis - Thanks for the advice.  We have moved the installation of Traps for mac to the end of our deployment process.  We have escalated the issue, the standalone installer, the script, client logs and server log at the time of installation to PaloAlto Support.  It seems they are a little baffled since this has been going on for over a month now.

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 Live Community as a whole!

The Live Community thanks you for your participation!