Jamf has successfully completed a Service Organization Control 2 (SOC 2) Type 2 audit for its Jamf Pro hosted services. The organization worked with PricewaterhouseCoopers LLP to perform an in-depth audit of our controls as they relate to security, availability and confidentiality for the period March 1, 2017 to August 31, 2017.

Data in transit is encrypted using TLS with Perfect Forward Security (PFS), and data at rest uses industry standard AES-256 to encrypt fields in the database that contain sensitive information, such as passwords and FileVault individual recovery keys.

Jamf Cloud and the latest versions of Jamf Pro installers no longer include support for SSL v3.0. For existing on-premise installations, instructions are available on Jamf Nation for removing support for SSL v3.0 and configuring supported cipher suites for Tomcat HTTPS connections

Passwords for local Jamf Pro user accounts are hashed using SHA-512 with a unique, random salt for each user, and all other passwords are encrypted using industry standard AES-256 with a unique, random key for each database.

Jamf Cloud relies on Amazon Web Services (AWS) to provide infrastructure as a service (IaaS) within different geographic regions, including the United States, Germany, Japan and Australia. Data at rest remains in the region in which the Jamf Cloud instance was created.

We use an Agile methodology that incorporates cross-functional teams with members from Product Management, Engineering, Quality, and Technical Communications. Overarching Release and Quality processes ensure necessary oversight and consistency throughout the organization.

You can see the latest uptime status here.

Please email us here, and note the name and email address associated with your Grove Technologies MDM subscription or contract.