Discover all opportunities of your app with AI
The payment gateway used by Module is Stripe, level 1 PCI compliance holder. Their environment meets the highest industry standards and guidelines.
Cardholder data is managed in the Stripet, using multiple encryption keys with split knowledge and dual control. A data thief would not be able to make use of information stolen from a database without also having the key. This data store cannot be connected to via the internet.
No card data stored on our side to prevent security vulnerabilities and possible data losses. Only internal identifiers used to communicate with the gateway.
Azure networking provides the infrastructure to securely connect virtual machines (VMs) to one another and to connect on-premises datacenters with Azure VMs and PaaS services. The Azure shared infrastructure hosts hundreds of millions of active VMs, so protecting the security and confidentiality of network traffic is critical.
Microsoft datacenters have extensive layers of protection to reduce the risk of unauthorized physical access to datacenter resources.
Azure is a multitenant service, meaning that your data is stored on the same physical hardware as that of other customers. Azure uses logical isolation to segregate virtual networks and processing for each customer to help ensure that your data is not combined with anyone else’s over virtual networks in Azure. This provides the scale and economic benefits of multi tenant services while rigorously preventing customers from accessing one another’s data.
Azure safeguards data for applications, platform, system, and storage using four specific methods: segregation, encryption, redundancy, and destruction.
Azure manages and controls identity and user access to enterprise environments, data, and applications by federating user identities to Azure Active Directory and enabling multifactor authentication for more secure sign-in. Microsoft uses stringent identity management and access controls to limit data and systems access to those with a genuine business need (least-privileged).
Microsoft designs, builds, and operates datacenters in a way that strictly controls physical access to the areas where your data is stored. Microsoft has hundreds of Azure datacenters in 54 regions (as of 2019), and each of these has extensive multilayered protections to ensure unauthorized users cannot gain physical access to your customer data.
Azure Cosmos DB uses hash-based message authentication code (HMAC) for authorization. Each request is hashed using the secret account key, and the subsequent base-64 encoded hash is sent with each call to Azure Cosmos DB. To validate the request, the Azure Cosmos DB service uses the correct secret key and properties to generate a hash, then it compares the value with the one in the request. If the two values match, the operation is authorized successfully and the request is processed, otherwise there is an authorization failure and the request is rejected.
Using the primary key for the account, we created user resources and permission resources per database. A resource token is associated with a permission in a database and determines whether the user has access (read-write, read-only, or no access) to an application resource in the database. None of our users can access data directly and modify it.
Azure Cosmos DB offers turnkey global distribution, which enables us to replicate data to any one of Azure's world-wide data centers. Global replication lets us scale globally and provide low-latency access to your data around the world. In the context of security, global replication ensures data protection against regional failures.
Azure Cosmos databases are backed up regularly and stored in a geo redundant store. Which allows us to restore any data loss.