Keeping Our Users’ Data Private is an Essential Aspect of Our Business
Our security engineers at Spot by NetApp have invested an enormous amount of time and energy into the establishment of robust security practices. Our security strategy and architecture have been designed in cooperation with the Amazon Web Services SaaS security team. With attention focused on the highest compliance regulations and following industry best practices, we provides robust security to all of our customers.
Sensitive data is encrypted at every step:
Spot never receives or transmits unencrypted account information. Spot first encrypts data within the browser then re-encrypt that data with an even more secure algorithm (GPG RSA 3072-bit) once it reaches our servers.
Only a specialized set of servers are able to read the encrypted blobs.
Web traffic is limited to the strictest protocol. All web connections are sent via 256-bit DigiCert High Assurance EV CA-1 SSL.
STRICT SECURITY AND KEY MANAGEMENT PROCEDURES
Staff members do not have the ability to decrypt encrypted account data. Spot follows extensive best practices in order to keep customers’ sensitive information secure.
TEAMED WITH AWS, GOOGLE CLOUD, AND MICROSOFT AZURE
Staff members do not have the ability to decrypt encrypted account data, and we use extensive best practices to keep your sensitive information secure. If you’d like more details about our approach to security, we’d be happy to arrange a call with a member of your team: contact us.
Authenticating and accessing our customers’ cloud accounts
3 STEP AUTHENTICATION PROCESS
Spot does not store any private keys, passwords, or authentication tokens. The authentication is being made based on the IAM Cross Account Role & External ID only. Figure 1, shows the process of forwarding a user request from the Spot SaaS platform to the customers’ AWS account.
First, the customer authenticates with a secured website. All communication outside of our website is sent via 256-bit DigiCert High Assurance EV CA-1 SSL Certificate.
Next, when the request reaches the Spot servers, the API service communicates via API SDK calls with the customer’s account via IAM Cross Account Role & UUID External IDs.
All calls within the customer’s account are secured via IAM Cross Account Role & UUID External IDs. Meaning, only Spot’s designated AWS account IDs can access this specific IAM Role, and only with an external ID that Spot has generated for the customer upon their registration.
Manage Cookie Consent
We use technologies like cookies to store and/or access device information. We do this to improve browsing experience and to show (non-) personalized ads. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.