Alex Bauer

8 results

Debunking MongoDB Myths: Security, Scale, and Performance

MongoDB has come a long way since its founding in 2007. Many people first encountered MongoDB during its early years. They formed opinions about the database based on impressions from 2012 to 2014. However, much has changed since then. Over the past eleven years, MongoDB has made significant strides. Foremost being the launch of MongoDB Atlas in 2016. It has placed a substantial focus on improving the four critical areas that matter most to businesses and developers alike: security, durability, availability, and performance. Security: Protecting sensitive data from unauthorized access and ensuring regulatory compliance. Durability: Ensuring data remains intact and reliable, even during system failures or unexpected disruptions. Availability: Minimizing downtime and maintaining system operation, no matter what happens. Performance: Delivering fast, consistent application response times and scaling efficiently to meet growing demand. These advancements have earned the trust of some of the world’s largest enterprises, including Toyota , Cisco , Wells Fargo , Bosch , and Verizon . Yet despite this progress, outdated myths regarding MongoDB persist—particularly in these four foundational areas. In this blog, we will tackle those misconceptions head on and set the record straight about MongoDB’s security, durability, availability, and performance. Let’s dive in. Myth 1: “MongoDB is not as secure as a relational database” One of the most persistent myths about MongoDB is that it is not secure—certainly not as secure as traditional relational databases. This misconception likely stems from a series of ransomware attacks in the mid-2010s. Hackers exploited unsecured databases that lacked proper authentication and were left exposed on default TCP ports. While these incidents highlighted poor configuration practices, they have unfairly cast a shadow over MongoDB’s contemporary security capabilities. MongoDB provides robust, intelligent security features designed to protect sensitive data at every stage of its lifecycle. MongoDB encrypts data both in transit and at rest , just like other leading NoSQL and relational databases. However, what sets MongoDB apart is its ability to keep data encrypted while in use. With Queryable Encryption , an industry-first innovation unique to MongoDB, sensitive data can remain encrypted even while it is queried. This eliminates the need to decrypt the data and reduces exposure to threats. MongoDB also supports flexible authentication and authorization that seamlessly integrates with many identity management systems. Features like role-based access control and fine-grained permissions ensure users only have access to what they are authorized for. Concurrently, intuitive configuration makes these controls easy to implement. Beyond encryption and access control, MongoDB includes powerful auditing tools to monitor database activity and advanced network security features, such as IP allow-listing and private networking . Together, these capabilities provide comprehensive protection against unauthorized access and help organizations meet strict compliance requirements. Best of all, these advanced security features are included by default in both MongoDB Atlas and MongoDB Enterprise Advanced at zero cost. MongoDB’s approach simplifies security management while minimizing expenditure. This allows teams to focus on building applications with confidence that their data is protected. Myth 2: “MongoDB’s multi-cloud capabilities do not set it apart from other databases” At first glance, the claim that MongoDB is multi-cloud may not sound special. After all, plenty of databases are available through more than one cloud provider - however, this should not be confused with them all being multi-cloud . True multi-cloud supports ‘cross-cloud’ deployments, i.e. the ability to deploy individual nodes of a single cluster across multiple cloud providers. This distinction is often obfuscated by those vendors unable to run their clusters in such a configuration. Support for multi-cloud clusters in Atlas became generally available in October of 2020. MongoDB Atlas enables deployment not only on Amazon Web Services (AWS), Microsoft Azure, or Google Cloud but also across all three clouds simultaneously with a single cluster. It is possible to set up and configure cross-cloud deployments solely from the Atlas management console. No further configuration is required via the individual cloud providers. This is more than just a convenience; it is a transformative capability that eliminates the boundaries between cloud providers. With MongoDB Atlas, it is as if AWS, Azure, and Google Cloud operate as one unified cloud environment. Why does this matter? For starters, deploying a single database cluster across multiple clouds removes the operational complexity of managing data replication and migration between providers. Seamless data mobility can be achieved. The hardest part of any application to move—the data—now becomes the easiest. Multicloud also enables the creation of application architectures that exploit the best services from multiple cloud providers simultaneously. In addition, cross-cloud deployments deliver unmatched resiliency. With cross-cloud failover, in the event of an outage, data can be automatically switched to another cloud provider in the same geographic region. Thus ensuring uninterrupted service. Finally, MongoDB Atlas provides the flexibility to meet regional and cloud provider preferences with ease. Atlas spans 115+ supported regions across all three major cloud providers . This makes it easy to meet customer demands or comply with local regulations using a single database. MongoDB Atlas gives us the ability to run our database on multiple clouds through the same service. With Atlas, we have the freedom from lock-in—each client can choose where they are the most comfortable hosting their data. Gary Hoberman, CEO and Founder - Unquork Myth 3: “I get that MongoDB is built for horizontal scaling, but it is so painful to scale” Horizontal scaling, also known as scale-out, is a core strength of MongoDB. It allows workloads to be distributed by adding more nodes as data and applications expand. However, some beliefs have perpetuated that scaling MongoDB is difficult and complex. The reality? MongoDB makes scaling not just possible, but seamless—whether scaling out horizontally or scaling up vertically. With MongoDB Atlas, vertical scaling—or scale-up—is simple. By enabling auto-scaling , MongoDB Atlas dynamically adjusts cluster resources to meet workload demands. Adding more RAM, CPU, or storage capacity can be performed automatically and on-demand. This ensures optimal performance without continual manual intervention or oversight. If you need to move beyond vertical scaling, MongoDB offers three flexible ways to scale horizontally : Hashed sharding : Data is distributed randomly across nodes using a hashed shard key. This ensures an even distribution of data and workloads to prevent bottlenecks. Ranged sharding : Data is distributed based on ranges of a specific field. This enables fine-grained control over how data is divided. This approach is especially useful for preventing hotspots in workloads. Zone sharding : Data is distributed geographically. This enables compliance with data residency requirements and reduces latency by keeping data closer to users. What happens if the initial sharding strategy does not go as planned? MongoDB addresses this challenge with the ability to refine shard keys and reshard a collection with zero downtime. This ensures data distribution strategies can adapt as needs evolve, all without disrupting applications or users. Myth 4: “Since MongoDB is built for flexibility, it must not be very performant” One common misconception about MongoDB is that its flexibility and versatility must come at the expense of performance. After all, can such an agile database—one built for developers to model data however they want—really deliver the speed and efficiency of a performance-first solution? MongoDB is designed to provide both; unmatched flexibility and exceptional performance —all while keeping costs low. MongoDB’s performance stems from its intelligent architecture and powerful features. Ad hoc queries, indexing , and real-time aggregations make it easy to access and analyze data quickly. How fast are queries? Primary key or indexed queries typically execute in milliseconds. Even complex queries that are not indexed remain efficient. Performance typically is dependent on factors like collection size and machine specifications. What about workloads like search and analytics? Some developers might assume these would compete for resources and degrade performance on operational tasks. However, MongoDB solves this with workload isolation . This feature ensures that operational and nonoperational workloads are separated. This enables each to run at peak performance without requiring costly and time-consuming extract, transform, and load (ETL) processes. Network latency? For globally distributed applications, MongoDB’s hedged reads enable the nearest replica nodes to be read from rather than waiting for a response from distant nodes. This reduces latency and ensures applications remain highly responsive. MongoDB’s real-world performance is backed by incredible use cases: Amadeus processes 630 million bookings per year. Idealo supports 200,000 queries and 60,000 updates per second. Temenos achieves 150,080 transactions per second. This was before the release of MongoDB 8.0 , the most performant version of the database yet. MongoDB 8.0 has delivered: 36% faster reads 32% faster reads and updates 56% faster bulk inserts A stunning 200% improvement for time series queries MongoDB Atlas doesn’t just solve our performance issues. It makes life easier for web developers, who can build and maintain simpler, more straightforward code. Moutia Khatiri, CTO - Tech Accelerator, L’Oreal MongoDB Today MongoDB has evolved far beyond the myths perpetuated during its early years. MongoDB 8.0 delivers robust capabilities across security, durability, availability, and performance. It encrypts sensitive data throughout its lifecycle and enables seamless cross-cloud deployments. It simplifies horizontal and vertical scaling and powers some of the world’s most demanding applications. These capabilities solidify MongoDB’s position as the database of choice for modern applications. Read about more MongoDB myths and misconceptions in our previous two posts in this series: Debunking MongoDB Myths: Enterprise Use Case Busting the Top Myths About MongoDB vs Relational Databases Don't be held back by outdated misconceptions. Experience the innovation and performance of MongoDB. Start using MongoDB Atlas for free today . Or, to learn more about MongoDB, head over to MongoDB University and take our free Intro to MongoDB course .

March 10, 2025

Advancing Encryption in MongoDB Atlas

Maintaining a strong security posture and ensuring compliance with regulations and industry standards are core responsibilities of enterprise security teams. However, satisfying these responsibilities is becoming increasingly complex, time-consuming, and high-stakes. The rapid evolution of the threat landscape is a key driver of this challenge. In 2024, the percentage of organizations that experienced a data breach costing $1 million or more jumped from 27% to 36%. 1 This was partly fueled by a 180% surge from 2023 to 2024 in vulnerability exploitation by attackers. 2 Concurrently, regulations are tightening. Laws like the Health Insurance Portability and Accountability Act (HIPAA) 3 and the U.S. Securities and Exchange Commission’s cybersecurity regulations 4 have introduced stricter security requirements. This has raised the bar for compliance. Thousands of enterprises rely on MongoDB Atlas to protect their sensitive data and support compliance efforts. Encryption plays a crucial role on three levels; securing data at rest, in transit, and in use. However, security teams need more than solely strong encryption. Flexibility and control are essential to align with an organization’s specific requirements. MongoDB is introducing significant upgrades to MongoDB Atlas encryption to meet these needs. This includes enhanced customer-managed key (CMK) functionality and support for TLS 1.3. This post explores these improvements, along with the planned deprecation of outdated TLS versions, to strengthen organizations’ security postures. Why customer-managed keys (CMKs) matter Customer-managed keys (CMKs) are a security and data governance feature that delivers enterprises full control over the encryption keys protecting their data. With CMKs, customers can define and manage their encryption strategy. This ensures they have ultimate authority over access to their sensitive information. MongoDB Atlas customer key management provides file-level encryption, similar to transparent data encryption (TDE) in other databases. This customer-managed encryption-at-rest feature works alongside always-on volume-level encryption 5 in MongoDB Atlas. CMKs ensure all database files and backups are encrypted. MongoDB Atlas also integrates with AWS Key Management Service (AWS KMS), Azure Key Vault , and Google Cloud KMS . This ensures customers have the flexibility to manage keys as part of their broader enterprise security strategy. Customers using CMKs retain complete control of their encryption keys. If an organization needs to revoke access to data due to a security concern or any other reason, it can do so immediately by freezing or destroying the encryption keys. This capability acts as a “kill switch,” ensuring sensitive information becomes inaccessible when protection is critical. Similarly, an organization can destroy the keys to render the data and backups permanently unreadable and irretrievable. This may be applicable should they choose to retire a cluster permanently. Announcing CMK over private networking As part of a commitment to deliver secure and flexible solutions for enterprise customers, MongoDB is introducing CMKs over private networking. This enhancement enables organizations to manage their encryption keys without exposing their key management service (KMS) to the public internet. Using CMKs in MongoDB Atlas previously required Azure Key Vault and AWS KMS to be accessible via public IP addresses prior to today. While functional, this posed challenges for customers who need to keep KMS traffic private. It forced those customers to either expose their KMS endpoints or manage IP allow lists. By using private networking, customers can now: Eliminate the need for public IP exposure. Simplify network management by removing the need to manage allowed IP addresses. This reduces administrative effort and misconfiguration risk. Align with organizational requirements that mandate the use of private networking. Customer key management over private networking is now available for Azure Key Vault and AWS KMS . Customers can enable and manage this feature for all their MongoDB Atlas projects through the MongoDB Atlas UI or the MongoDB Atlas Administration API . More enhancements are coming for MongoDB customer key management in 2025. These include secretless authentication mechanisms and CMKs for search nodes. MongoDB Atlas TLS enhancements advance encryption in transit Securing data in transit is equally vital as a foundation of encryption at rest with CMKs. To address this, MongoDB Atlas enforces TLS by default. This ensures encrypted communication across all aspects of the platform, including client connections. Now MongoDB is reinforcing its TLS implementation with key enhancements for enterprise-grade security. MongoDB is in the process of rolling out fleetwide support for TLS 1.3 in MongoDB Atlas. The latest version of the cryptographic protocol offers several advantages over its predecessors. This includes stronger security defaults, faster handshakes, and reduced latency. Concurrently, TLS versions 1.0 and 1.1 are being deprecated. The rationale for this is known weaknesses and their inability to meet modern security standards. MongoDB is aligning with industry best practices by standardizing on TLS 1.2 and 1.3. This ensures a secure communication environment for all MongoDB Atlas users. Additionally, MongoDB now offers custom cipher suite selection, giving enterprises more control over their cryptographic configurations. This feature lets organizations choose the cipher suites for their TLS connections, ensuring compliance with their security requirements. Achieving encryption everywhere This post covers how MongoDB secures data at rest with CMKs and in transit with TLS. However, what about data in use while it’s being processed in a MongoDB Atlas instance? That’s where Queryable Encryption comes in. This groundbreaking feature enables customers to run expressive queries on encrypted data without ever exposing the plaintext or keys outside the client application. Sensitive data and queries never leave the client unencrypted. This ensures sensitive information is protected and inaccessible to anyone without the keys, including database administrators and MongoDB itself. MongoDB is committed to providing enterprise-grade security that evolves with the changing threat and regulatory landscapes. Organizations now have greater control, flexibility, and protection across every stage of the data lifecycle with enhanced CMK functionality, TLS 1.3 adoption, and custom cipher suite selection. As security challenges grow more complex, MongoDB continues to innovate to enable enterprises to safeguard their most sensitive data. To learn more about these encryption enhancements and how they can strengthen your security posture, visit MongoDB Data Encryption . 1 PwC , October 2024 2 Verizon Data Breach Investigations Report , 2024 3 U.S. Department of Health and Human Services , December 2024 4 U.S. Securities and Exchange Commission , 2023 5 MongoDB Atlas Security White Paper , Encryption at Rest section page 12

March 5, 2025

Secure by Default: Mandatory MFA in MongoDB Atlas

On March 26, 2025, MongoDB will start rolling out mandatory multi-factor authentication (MFA) for MongoDB Atlas users. While MFA has long been supported in Atlas, it was previously optional. MongoDB is committed to delivering customers the highest level of security, and the introduction of mandatory MFA adds an extra layer of protection against unauthorized access to MongoDB Atlas. Note: MFA will require users to provide a second form of authentication, such as a one-time passcode or biometrics. To ensure a smooth transition, users are encouraged to set up their preferred MFA method in advance. This process should take around three minutes to set up. If MFA is not configured by March 26, 2025, users will need to enter a one-time password (OTP) sent to their registered email each time they log in. Why are we making MFA mandatory? Stealing users’ credentials is a key tactic in the modern cyberattack playbook. According to a Verizon report, stolen credentials have been involved in 31% of data breaches in the past decade, and credential stuffing is the most common attack type for web applications. 1 Credential stuffing is when attackers use stolen credentials obtained from a data breach on one service to attempt to log in to another service. These breaches are particularly harmful, taking an average of 292 days to detect and contain. 2 This rise in cyber threats has rendered password-only security inadequate. Organizations of all sizes trust MongoDB Atlas to safeguard their mission-critical applications and sensitive data. These range from global enterprises to individual developers. Therefore, to strengthen account security and to reduce the risk of unauthorized access, MongoDB is introducing mandatory MFA. The impact of MFA A large-scale study by Microsoft measured the effectiveness of MFA to prevent cyberattacks on enterprise accounts. The findings indicated enabling MFA reduces the risk of account compromise by 99.22%. For accounts with previously leaked credentials, MFA still lowered the risk by 98.56%. This makes MFA one of the most effective defenses against unauthorized access. By default, requiring MFA strengthens the security of all MongoDB Atlas accounts. By reducing the risk of compromised accounts being used in broader attacks, this proactive step protects individual users and enhances MongoDB Atlas’s overall security. Ensuring strong authentication practices across the Atlas ecosystem maintains the integrity of mission-critical applications and sensitive data— and a safer experience for everyone is the result. Preparing for mandatory MFA MFA will be a prerequisite for all users when logging into MongoDB services using Atlas credentials. These services include: MongoDB Atlas user interface MongoDB Support portal MongoDB University MongoDB Forums Atlas supports the following MFA methods: Security key or biometrics: FIDO2 (WebAuthn) compliant security keys (e.g., YubiKey ) or biometric authentication (e.g., Apple Touch ID or Windows Hello) One-time password (OTP) and push notifications: Provided through the Okta Verify app Authenticator apps: Such as Twilio Authy , Google Authenticator , or Microsoft Authenticator for generating time-based OTPs Email: For generating OTPs MongoDB encourages users to choose phishing-resistant MFA methods, such as security keys or biometrics. Strengthening security with mandatory MFA Requiring MFA is a significant step that enhances MongoDB Atlas’s default security. Multi-factor authentication protects users from credential-based attacks and unauthorized access. Making MFA’s additional layer of authentication mandatory ensures greater account security. This safeguards mission-critical applications and data. To ensure a smooth transition, users are encouraged to set up their preferred MFA method before March 26, 2025. For detailed setup instructions, refer to the MongoDB documentation . And, please visit the MongoDB security webpage and Trust Center to learn more about MongoDB’s commitment to security.

February 28, 2025

Simplify Security At Scale with Resource Policies in MongoDB Atlas

Innovation is the gift that keeps on giving: industries that are more innovative have higher returns, and more innovative industries see higher rates of long-term growth 1 . No wonder organizations everywhere strive to innovate. But in the pursuit of innovation, organizations can struggle to balance the need for speed and agility with critical security and compliance requirements. Specifically, software developers need the freedom to rapidly provision resources and build applications. But manual approval processes, inconsistent configurations, and security errors can slow progress and create unnecessary risks. Friction that slows down employees and leads to insecure behavior is a significant driver of insider risk. Paul Furtado Vice President, Analyst, Gartner Enter resource policies , which are now available in public preview in MongoDB Atlas. This new feature balances rapid innovation with robust security and compliance. Resource policies allow organizations to enable developers with self-service access to Atlas resources while maintaining security through automated, organization-wide ‘guardrails’. What are resource policies? Resource policies help organizations enforce security and compliance standards across their entire Atlas environment. These policies act as guardrails by creating organization-wide rules that control how Atlas can be configured. Instead of targeting specific user groups, resource policies apply to all users in an organization, and focus on governing a particular resource. Consider this example: An organization subject to General Data Protection Regulation (GDPR) 2 requirements needs to ensure that all of their Atlas clusters run only on approved cloud providers in regions that comply with data residency and privacy regulations. Without resource policies, developers may inadvertently deploy clusters on any cloud provider. This risks non-compliance and potential fines of up to 20 million euros or 4% of global annual turnover according to article 83 of the GDPR. But, by using resource policies, the organization can mandate which cloud providers are permitted, ensuring that data resides only in approved environments. The policy is automatically applied to every project in the organization, preventing the creation of clusters on unauthorized cloud platforms. Thus compliance with GDPR is maintained. The following resource policies are now in public preview: Restrict cloud provider: Limit Atlas clusters to approved cloud providers (AWS, Azure, Google Cloud). Restrict cloud region: Restrict cluster deployments in approved cloud providers to specific regions. Block wildcard IP: Reduce security risk by disabling the use of 0.0.0.0/0 (or “wildcard”) IP address for cluster access. How resource policies enable secure self-service Atlas access Resource policies address the challenges organizations face when trying to balance developer agility with robust security and compliance. Without standardized controls, there is a risk that developers will configure Atlas clusters to deviate from corporate or external requirements. This invites security vulnerabilities and compliance gaps. Manual approval and provisioning processes for every new project creates delays. Concurrently, platform teams struggle to enforce consistent standards across an organization, increasing operational complexity and costs. With resource policies, security and compliance standards are automatically enforced across all Atlas projects. This eliminates manual approvals and reduces the risk of misconfigurations. Organizations can deliver self-service access to Atlas resources for their developers. This allows them to focus on building applications instead of navigating complex internal review and compliance processes. Meanwhile, platform teams can manage policies centrally. This ensures consistent configurations across the organization and frees time for strategic initiatives. The result is a robust security posture, accelerated innovation, and greater efficiency. Automated guardrails prevent unauthorized configurations. Concurrently, centralized policy management streamlines operations and ensures alignment with corporate and external standards. Resource policies enable organizations to scale securely and innovate without compromise. This empowers developers to move quickly while simplifying governance. iA Financial Group, one of Canada’s largest insurance and wealth management firms, uses resource policies to ensure consistency and compliance in MongoDB Atlas. “Resource Policies have allowed us to proactively supervise Atlas’s usage by our IT delivery teams,” said Geoffrey Céré, Solution Architecture Advisor at iA Financial Group. “This has been helpful in preventing non-compliant configurations with the company’s regulatory framework. Additionally, it saves our IT delivery teams time by avoiding unauthorized deployments and helps us demonstrate to internal audits that our configurations on the MongoDB Atlas platform adhere to the regulatory framework.” Creating resource policies Atlas resource policies are defined using the open-source Cedar policy language , which combines expressiveness with simplicity. Cedar’s concise syntax makes writing and understanding policies easy, streamlining policy creation and management. Resource policies can be created and managed programmatically through infrastructure-as-code tools like Terraform or CloudFormation, or by integrating directly using the Atlas Admin API. To explore what constructing a resource policy looks like in practice, let’s return to our earlier example. This is an organization subject to GDPR requirements that wants to ensure all of their Atlas clusters run on approved cloud providers only. To prevent users from creating clusters on Google Cloud (GCP), the organization could write the following policy named “ Policy Preventing GCP Clusters .” This policy forbids creating or editing a cluster when the cloud provider is Google Cloud. The body defines the behavior of the policy in the human and machine-readable Cedar language. If required, ‘ gcp ’ could be replaced with ‘ aws ’. Figure 1. Example resource policy preventing the creation of Atlas clusters on GCP. Alternatively, the policy could allow users to create clusters only on Google Cloud with the following policy named “Policy Allowing Only GCP Clusters”. This policy uses the Cedar clause “unless” to restrict creating or editing a cluster unless it is on GCP. Figure 2. Example resource policy that restricts cluster creation to GCP only. Policies can also have compound elements. For example, an organization can create a project-specific policy that only enforces the creation of clusters in GCP for the Project with ID 6217f7fff7957854e2d09179 . Figure 3. Example resource policy that restricts cluster creation to GCP only for a specific project. And, as shown in Figure 4, another policy might restrict cluster deployments on GCP as well as on two unapproved AWS regions: US-EAST-1 and US-WEST-1. Figure 4. Example resource policy restricting cluster deployments on GCP as well as AWS regions US-EAST-1 and US-WEST-1. Getting started with resource policies Resource policies are available now in MongoDB Atlas in public preview. Get started creating and managing resource policies programmatically using infrastructure-as-code tools like Terraform or CloudFormation. Alternatively, integrate directly with the Atlas Admin API. Support for managing resource policies in the Atlas user interface is expected by mid-2025. Use the resources below to learn more about resource policies. Feature documentation Postman Collection Atlas Administration API documentation Terraform Provider documentation AWS CDK AWS Cloud Formation documentation 1 McKinsey & Company , August 2024 2 gdpr.eu

February 10, 2025

Strengthen Data Security with MongoDB Queryable Encryption

MongoDB Queryable Encryption is a groundbreaking, industry-first innovation developed by the MongoDB Cryptography Research Group that allows customers to encrypt sensitive application data, store it securely in an encrypted state in the MongoDB database, and perform equality and range queries directly on the encrypted data—with no cryptography expertise required. Adding range query support to Queryable Encryption significantly enhances data retrieval capabilities by enabling more flexible and powerful searches. Queryable Encryption is available in MongoDB Atlas, Enterprise Advanced, and Community Edition. Encryption: Protecting data through every stage of its lifecycle Encryption is a critical security method for ensuring protection of sensitive data and compliance with regulations like GDPR, CCPA, and HIPAA. It involves rendering data unreadable to anyone without the decryption key. It can protect data in three ways: in-transit (over networks), at-rest (when stored), and in-use (during processing). While encryption in-transit and at-rest are standard for all databases and are well-supported by MongoDB , encryption in-use presents a unique challenge. Encryption in-use is difficult because encrypted data is unreadable—it looks like random characters and symbols. Traditionally, the database can’t run queries on encrypted data without decrypting it first to make it readable. However, if the database doesn’t have a decryption key, it has to send encrypted data back to the application or system (i.e., the client) that has the key so it can be decrypted before querying. This is a pattern that doesn’t scale well for real-world applications. This puts organizations in a difficult spot: in-use encryption is important for data privacy and regulatory compliance, but it's hard to implement. In the past, companies have either chosen not to encrypt sensitive data in-use or have employed less secure workarounds that complicate their operations. MongoDB Queryable Encryption: Safeguarding data in use without sacrificing efficiency MongoDB Queryable Encryption solves this problem. It allows organizations to encrypt their sensitive data, like personally identifiable information (PII) or protected health information (PHI), and to run equality and range queries directly on that data without having to decrypt it. Queryable Encryption was developed by the MongoDB Cryptography Research Group , drawing on their pioneering expertise in cryptography and encrypted search, and Queryable Encryption has been peer-reviewed by leading cryptography experts worldwide. Unmatched in the industry, MongoDB is the only data platform that allows customers to run expressive queries directly on non-deterministically encrypted data. This represents a groundbreaking advantage for customers, allowing them to maintain robust protection for their sensitive data without sacrificing operational efficiency or developer productivity by still enabling expressive queries to be performed on it. Organizations of all sizes, across all industries, can benefit from the impactful outcomes enabled by Queryable Encryption, such as: Stronger data protection: Data stays encrypted at every stage—whether in-transit, at-rest, or in-use—reducing the risk of sensitive data exposure or breaches. Enhanced regulatory compliance: Provides customers with the necessary tools to comply with data protection regulations like GDPR, CCPA, and HIPAA by ensuring robust encryption at every stage. Streamlined operations: Simplifies the encryption process without needing costly custom solutions, specialized cryptography teams, or complex third-party tools. Solidified separation of duties: Supports stricter access controls, where MongoDB and even a customer's database administrators (DBAs) don’t have access to sensitive data. Use cases for Queryable Encryption MongoDB Queryable Encryption has many use cases for organizations that host sensitive data, regardless of their size or industry. The recent addition of range query support to Queryable Encryption broadens those use cases even wider. Here are some examples to help illustrate how Queryable Encryption could be used to protect and query sensitive data: Financial Services Credit Scoring: Assess creditworthiness by querying encrypted data such as credit scores and income levels. For example, segment your customers based on credit scores between 600 and 750. Fraud Detection: Detect anomalies by querying encrypted transaction amounts for values that exceed typical spending patterns, such as transactions above $10,000. Insurance Risk Assessment: Personalize policy offerings by querying encrypted client data for risk levels within specified ranges, enhancing customer service without exposing sensitive information. Claims Processing: Automate claims processing by querying encrypted claims data for amounts within specific ranges or for claims within time periods, streamlining operations while safeguarding information. Healthcare Medical Research: Execute range-based searches on encrypted medical records, such as querying encrypted datasets for patients within specific age ranges or for abnormal lab results for medical research. Billing and Insurance Processing: Perform secure range queries on encrypted billing data to process insurance claims and payments while protecting patient financial details. Education Grading Systems: Process encrypted student scores to award grades within specific ranges, ensuring compliance with FERPA while protecting student privacy and maintaining data security. Financial Aid Distribution: Analyze encrypted income data within certain ranges to determine eligibility for scholarships and financial aid. Comprehensive data protection at every stage With Queryable Encryption, MongoDB offers unmatched protection for sensitive data throughout its entire lifecycle—whether in-transit, at-rest, or in-use. Now, with the addition of range query support, Queryable Encryption meets even more of the demands of modern applications, unlocking new use cases. To get started, explore the Queryable Encryption documentation .

October 16, 2024

通过独特的可查询加密技术,MongoDB为数据安全提供覆盖全生命周期的保护

MongoDB可查询加密( Queryable Encryption )由MongoDB加密研究小组(Cyptography Research Group)开发,是具有突破性意义的业界首创技术。该技术允许客户对应用中的敏感数据进行加密,不但可以将其以加密状态安全地存储在MongoDB数据库中,还可直接在加密数据上执行等值查询和范围查询,且无需具备加密专业知识。在原有可查询加密技术中增加了范围查询,进一步增强了数据检索功能,使搜索更加灵活和强大。目前,可查询加密在MongoDB Atlas、企业高级版(Enterprise Advanced)和社区版(Community Edition)中均可用。 覆盖数据安全全生命周期的加密技术 企业要确保对于敏感数据的保护并符合各种相关法律法规,如欧盟的《通用数据保护条例》 (GDPR)等,加密技术至关重要。这涉及将数据转换为任何没有解密密钥的人都无法读取的形式。加密可以通过三种方式保护数据:传输中(通过网络时)、静态(存储时)、使用中(处理期间)。传输中和静态数据的加密是所有数据库的标配( MongoDB也不例外 ),但使用中的数据加密却带来了独特的挑战。 对于使用中数据的加密之所以困难,是因为加密后的数据不可读,看起来像是一串随机的字符和符号。传统上,数据库无法直接对加密数据进行查询,而必须先将其解密为可读形式。然而,如果数据库没有解密密钥,它就必须将加密数据发送回拥有密钥的应用程序或系统(如客户端),以便在查询之前进行解密。很显然,这种模式在实际应用中不具备扩展性。 这使企业陷入两难境地:对使用中数据的加密在数据隐私保护和法规合规性方面至关重要,但却难以实现。过去,公司要么选择不对使用中的敏感数据进行加密,要么采用安全性较低的变通方法,而后者会导致操作变得更加复杂。 MongoDB 可查询加密:保护使用中的数据,且不影响效率 MongoDB 可查询加密解决了这一难题。它允许组织对敏感数据(如个人身份、医疗信息等)进行加密,并能够在不解密的情况下直接对这些数据执行等值查询和范围查询。 可查询加密由 MongoDB加密研究小组 (Cyptography Research Group)开发,得益于团队成员所具备的密码学和加密搜索领域领先的专业知识,已经通过了全球顶尖密码学专家的同行评审。让MongoDB独特于业界其他厂商的是,MongoDB是目前唯一一个允许客户直接在非确定性加密数据上运行复杂查询的数据平台。客户可以因此获得突破性的优势,能够对敏感数据进行表达式查询,在不牺牲运营效率或开发者生产力的同时,为敏感数据提供强大的保护。 各行各业、各种规模的组织都能从可查询加密带来的显著成果中受益,例如: 数据保护更强: 数据在传输、存储和使用中的每个阶段都保持加密状态,从而降低了敏感数据泄露或被攻破的风险。 增强法规合规性: 通过确保数据在每个阶段都进行加密,为客户提供遵守如GDPR等数据保护法规所需的工具。 简化操作: 无需昂贵的定制解决方案、专业的加密团队或复杂的第三方工具,即可简化加密过程。 明确的职责分离: 支持更严格的访问控制,甚至MongoDB和客户自身的数据库管理员(DBA)都无法访问敏感数据。 MongoDB 可查询加密的使用场景 MongoDB 可查询加密可广泛用于各类需要对敏感数据进行保护的组织,不论其所在行业和规模大小。而且,可查询加密新增了对范围查询的支持,这进一步扩大了使用场景。以下为部分示例,用以说明可以如何使用可查询加密来保护和查询敏感数据: 金融服务 信用评分:通过查询加密数据(如信用评分和收入水平)来评估信用度。例如,根据信用评分在某个分数范围内的客户来进行客户细分。 欺诈检测:通过查询加密的交易金额,查找超越一般消费模式的异常值,如交易金额超过10万元的交易,以此来检测欺诈行为。 保险 风险评估:通过查询加密的客户数据,在指定范围内查找风险等级,从而个性化提供保险建议,提升客户服务质量,同时不披露敏感信息。 理赔处理:通过查询加密的理赔数据,查找金额在特定范围内或特定时间段内的理赔案件,实现理赔处理自动化,在简化操作流程的同时保护信息安全。 医疗健康 医学研究:对加密的医疗记录执行基于范围的搜索,例如查询特定年龄段内的患者或医学研究中异常的实验室结果的加密数据集。 账单和保险处理:对加密的账单数据执行安全的范围查询,以处理保险索赔和支付,同时保护患者的财务信息。 教育 评分系统:处理加密的学生分数,以在特定范围内评定分数等级,保护学生隐私并维护数据安全。 经济资助分配:分析特定范围内的加密收入数据,以确定学生是否符合奖学金、助学金的资格 保护数据安全生命周期的每一个环节 MongoDB可查询加密技术,可以为敏感数据在其整个生命周期内(无论是在传输、静态还是使用中)提供无与伦比的保护。现在,通过增加对范围查询的支持,MongoDB可查询加密技术更好地满足了现代应用程序的需求,并解锁了新的使用场景。 如需了解更多信息,可登录查阅 MongoDB可查询加密网页 。

October 16, 2024

MongoDB Atlas for Government Supports GCP Assured Workloads

We’re excited to announce that MongoDB Atlas for Government now supports the US regions of Google Cloud Assured Workloads, alongside existing support for AWS GovCloud and AWS US regions. This expansion offers greater flexibility and expanded support for public sector organizations and the independent software vendors (ISVs) that serve them as they modernize applications and migrate workloads to the cloud. Furthermore, MongoDB Atlas for Government is now available for purchase through the Google Cloud Marketplace . MongoDB Atlas for Government: Driving digital transformation in the public sector MongoDB Atlas for Government is an independent, dedicated version of MongoDB Atlas, designed specifically to meet the unique needs of the U.S. public sector and ISVs developing public sector solutions. This modern database provides the versatility and scalability required to modernize legacy applications and migrate workloads to the cloud, all within a secure, fully-managed, FedRAMP authorized environment. Refer to the FedRAMP Marketplace listing for additional information about Atlas for Government. By leveraging the full functionality of MongoDB's document database and application services, Atlas for Government supports a wide range of use cases within a unified modern database, including Internet of Things, AI/ML, analytics, mobile development, single view, transactional workloads, and more. Ensuring robust resilience and comprehensive disaster recovery, Atlas for Government maintains business continuity and minimizes downtime. With a ~99.995% uptime SLA , auto-scaling to handle data consumption fluctuations, and automated backup and recovery, organizations can have peace of mind that their data is always protected. Getting started with MongoDB Atlas for Government MongoDB Atlas for Government can be used to create database clusters deployed to a single region or spanning multiple US regions. Google Cloud Assured Workloads US regions are now supported in Atlas for Government projects tagged as “Gov regions only,” allowing for the use of both traditional Google Cloud regions as well as Assured Workloads US regions. To get started, create a project in Atlas for Government and make sure to select 'Designate as a Gov Cloud regions-only project' during the project creation process. After creating the project, you can set up a MongoDB cluster in the GCP regions. To do this, start the cluster creation process and select GCP as the Cloud Provider, as shown in the figure below. You'll then be prompted to choose one or more GCP regions for your cluster. You can find more details on supported cloud providers and regions in the Atlas for Government documentation . Creating multi-cloud clusters The introduction of support for Google Cloud Assured Workloads (US regions) makes MongoDB Atlas for Government the first fully managed multi-cloud data platform authorized at FedRAMP Moderate. This means that public sector organizations and ISVs can now deploy clusters across Google Cloud Assured Workloads US regions and AWS GovCloud regions, in addition to deploying database clusters across multiple US regions. Whether prioritizing performance, cost, or specific feature sets, Atlas for Government empowers teams to deploy application architectures that simultaneously take advantage of the best-of-class services from multiple cloud providers while meeting FedRAMP requirements. Multi-cloud support also provides additional resiliency and enhanced disaster recovery, safeguarding data and applications against potential service outages and failures with automatic failover. Ensuring robust data protection and seamless continuity MongoDB Atlas for Government now supports Google Cloud Assured Workloads US regions, expanding its multi-cloud capabilities alongside existing support for AWS GovCloud and AWS US regions. This enhancement provides public sector organizations and ISVs with the flexibility to modernize applications and migrate workloads in a secure, FedRAMP authorized environment. With robust resilience, comprehensive disaster recovery, and a ~99.995% uptime SLA, Atlas for Government ensures data protection and business continuity. By offering a unified modern database for a wide range of use cases, Atlas for Government empowers teams to leverage best-in-class cloud services while meeting stringent compliance requirements. How do I get started? Visit our product page to learn more about MongoDB Atlas for Government. Or, read the Atlas for Government documentation to learn how to get started today.

August 20, 2024

Stay Compliant with MongoDB’s Latest Certifications: ISO 9001, TISAX, HDS, and TX-RAMP

Ensuring compliance with regulations and security standards across industries and regions is a crucial aspect of MongoDB’s commitment to protecting customer data. That’s why we’re excited to announce that MongoDB Atlas has achieved certifications for ISO 9001, TISAX, HDS, and TX-RAMP, further solidifying our dedication to data security and regulatory compliance for both enterprise and public sector organizations. MongoDB Atlas achieved these certifications across AWS, Azure, and Google Cloud supported regions, thus providing customers the flexibility to adopt a multi-cloud model to support their workloads. In order to achieve each of these four new certifications, MongoDB Atlas underwent independent verification of its quality management, platform security, privacy, documentation, and organizational controls. These certifications—and the independent verifications required to achieve them—help ensure that Atlas meets organizations’ compliance, regulatory, and policy objectives, including the unique compliance needs of highly regulated industries. Read on to learn more about MongoDB’s new ISO 9001, TISAX, HDS, and TX-RAMP certifications, and how they can benefit organizations of all sizes. ISO 9001 Developed by the International Organization for Standardization (ISO), ISO 9001:2015 is an international standard for quality management systems (QMS) that is widely recognized across industries and organizations of all sizes. It provides a framework and guiding principles to systematically deliver products and services at consistently high quality to customers while ensuring compliance with regulations. MongoDB Atlas’s ISO 9001:2015 certification provides assurance to customers that we have implemented a robust QMS and are committed to consistently meeting their requirements and complying with all applicable regulations. It also emphasizes the importance of process control and continual improvement at MongoDB, which leads to greater consistency in product or service quality over time. Visit the Trust Center to learn more about MongoDB's ISO 9001 certification . TISAX The Trusted Information Security Assessment Exchange, or TISAX, is a certification program for information security in the automotive industry. Based on information security requirements created by the German Association of the Automotive Industry (VDA), TISAX helps European automotive companies streamline security evaluations by providing an industry-specific security framework for assessing information security for the wide landscape of suppliers, OEMs, and partners that contribute to the automotive supply chain. There are three assessment levels of TISAX certification. MongoDB has demonstrated compliance with the assessment level 3 (AL3) TISAX certification, which is the highest assessment level available and signifies a supplier's ability to handle and protect highly sensitive data, while also maintaining high availability. MongoDB Atlas's TISAX certification assists automotive industry customers in meeting their rigorous compliance needs. Additionally, it assures these customers that their data will be safeguarded to the highest standards within MongoDB Atlas, with robust measures in place for business continuity, disaster recovery, and risk mitigation. Visit the Trust Center to learn more about MongoDB’s TISAX certification . HDS France's HDS regulations and certification, known as Hébergeur de Données de Santé (Health Data Hosting), ensure organizations comply with basic requirements for hosting personal health data. According to the French Public Health Code, any organization hosting health data from healthcare activities in France must obtain HDS certification. By securing HDS certification, MongoDB Atlas helps those customers hosting health data in France to comply with HDS regulations and instills confidence that robust security controls and practices are in place to protect this highly sensitive data. Visit the Trust Center to learn more about MongoDB’s HDS certification . TX-RAMP The Texas Risk and Authorization Management Program, or TX-RAMP, is a certification program established in Texas that ensures the security of cloud computing services used by state governmental agencies. In order to demonstrate compliance with the security criteria required for TX-RAMP certification, MongoDB Atlas was assessed by the Texas Department of Information Resources (DIR). MongoDB Atlas for Government is already TX-RAMP certified by virtue of it being FedRAMP Moderate authorized. By securing TX-RAMP certification, MongoDB Atlas simplifies procurement for public sector customers in Texas seeking to adopt MongoDB Atlas on AWS, Azure, or Google Cloud. Visit the Trust Center to learn more about MongoDB’s TX-RAMP certification . MongoDB is dedicated to securing your data. We do so through state-of-the-art technical and organizational security controls, numerous regulatory and compliance resources, and a constantly growing collection of third-party attestations and certifications. Our new ISO 9001, TISAX, HDS, and TX-RAMP certifications help us ensure compliance with regulations and security standards across diverse industries and regions, both for enterprise and public sector organizations. To learn more about MongoDB’s technical and organizational security measures, visit the Technical and Organizational Security Measures page .

May 23, 2024