Jamfing for Joy, attack vectors for Jamf in Enterprise

New Contributor

Salutations Jamf Nationalists,

In light of the recently published blog post in regards to directing attacks toward Jamf installations, is there any information or guidelines for fellow customers to follow to harden the (sometimes publicly) accessible web interface for the JSS?

We're eager to make sure we're following best practice to make sure we're as safe as possible. I've found the security recommendations, but I feel there is a disregard for common security practices such as two-(or multi-)factor authentication and such. I know of the SSO capabilities of the JSS, but I feel a built-in solution would be a good first step.

Any information or insight would be duly appreciated!
Best regards,