![]() ![]() Am I correct in understanding that for every customer of Jamf Cloud, there exists a username and password which, if it became compromised, could be used to issue wipe commands to every Mac in the org (and given the potential fallout of data leaks, that'd be a best-case scenario?) That just seems like an overwhelming risk given I can't even sign into Slack without using MFA but a system with all the power of Jamf will happily let someone in with just a straight username/password? Sure, you can set up SSO but just adding /?failover to the end of the URL bypasses that. There's one item that just has me completely baffled though - Jamf Cloud allows anyone anywhere in the world to sign into your Jamf Pro instance with only a username/password. The policy runs on computers in the scope the next time they check in with Jamf Pro and meet the criteria in the General payload.We've been using on-prem for years and have occasionally been taking a look at moving to Jamf Cloud hosting for Jamf Pro. For more information, see User Interaction with Policies. (Optional) Click the User Interaction tab and configure messaging and deferral options. For more information, see Items Available to Users in Jamf Self Service for macOS. (Optional) Click the Self Service tab and make the policy available in Self Service. ![]() Use the Restart Options payload to configure settings for restarting computers.Ĭlick the Scope tab and configure the scope of the policy. Select the Local Accounts payload and click Configure.Ĭhoose an action from the Action pop-up menu.Ĭonfigure the action using the options on the pane. Use the General payload to configure basic settings for the policy, including the trigger and execution frequency.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |