Security Frequently Asked Questions (FAQ)
We get asked a lot of questions, we’ve gathered them together to make it easier for you. This section is regularly updated, so be sure to check back.
Is our data encrypted?
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 2 individual recovery keys.
Is TLS always used?
Yes, JAMF Cloud and the latest versions of the JAMF Software Server (JSS) installers no longer include support for SSL v3.0. For existing and upgraded 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:
Mitigating the SSL v3.0 POODLE Vulnerability
Configuring Supported Ciphers for Tomcat HTTPS Connections
How are our passwords stored?Passwords for local JSS 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.
Who has access to our data?
Where are JAMF Cloud data centers located?
JAMF Cloud relies on Amazon Web Services (AWS) to provide infrastructure as a service (IaaS) within different geographic regions, including the United States, Germany, and Australia. Data at rest remains in the region in which the JAMF Cloud instance was created.
Does JAMF Software use a secure Software Development Lifecycle (SDLC)?
Yes. 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.
Does the JAMF Cloud JSS Hosting service have a SOC 2 Type 2 report?
We are currently preparing for a SOC 2 Type 2 report that is expected in 2016.
Does JAMF Software audit its security?
The Casper Suite is tested for common vulnerabilities prior to each public release, and independent third-party security assessments are periodically performed on key system components, including the JAMF Software Server (JSS) and client binary. For JAMF Cloud, JAMF Software relies on the Amazon Web Services (AWS) Shared Responsibility Model to ensure the security of the underlying infrastructure that is provided by AWS:
AWS Shared Responsibility Model
Can we undertake our own security testing?
Security testing on your own systems and networks is permitted within the terms of the End User License and Service Agreement (EULSA). For JAMF Cloud, our service provider requires prior written authorization before conducting any penetration testing or vulnerability assessments:
Vulnerability and Penetration Testing
Have questions that we didn't cover? Please don't hesitate to reach out to us and talk security.