1 Minute Read | By: Mappedin
Mappedin’s commitment to keeping our customers' maps and data secure persists throughout our entire operations, and particularly, our product development. As Mappedin’s product platform grows, so do our considerations around security and privacy.
Mappedin’s backend Map Editor and CMS have always leveraged our robust permissions system to ensure that only those designated have access to map data. This access enables our customers to make changes to their maps as part of their maintenance practices. To pair with this, Mappedin has recently implemented Two-Factor Authentication and Single Sign-On via Auth0 to this system. Both Two-Factor Authentication and Single Sign-On are available to all Mappedin customers.
Mappedin’s Two-Factor Authentication system leverages best practices in its implementation. We require users logging in to use an authentication application such as Google Authenticator, Authy, or something similar, versus SMS or email. These standards follow the guidelines from NIST.
Below outlines the simple steps to implementing our Two-Factor Authentication system.
Along with Two Factor Authentication, Mappedin has expanded its SSO (Single Sign-On) capabilities and offering. It’s paramount to Mappedin that our enterprise clients are able to leverage their internal security protocols while also integrating Mappedin systems into day-to-day processes.
Mappedin has a variety of ways to configure enterprise connections such as AD, SAML 2.0, Google Workspace, and more. This capability will allow Mappedin customers to secure logins under their businesses’ protocols and with a couple of configurations on the Mappedin side and on the client side, we can enable custom SSO to get our customers up and running.
Visit mappedin.com/security to stay up to date on all the latest policies and procedures Mappedin is putting in place regarding information security, or click here for more information on our Map Editor and CMS.