Announcing MongoDB 3.2 Now Generally Available
Today MongoDB 3.2 is generally available; you can download now.
Our community is critical to ensuring the quality of our releases. Thank you to everyone who participated in our 3.2 Bug Hunt. Winners were selected based on the user impact and severity of the bugs found.
Stuart Hall | SERVER-21690
Nick Judson | SERVER-21434
To learn more about MongoDB 3.2:
- Find out more about MongoDB 3.2
- Read the What’s New in 3.2 white paper
- Register for Best Practices for Upgrading to MongoDB 3.2
- Review the 3.2 release notes
Announcing the General Availability of MongoDB 3.2 and Bug Hunt Winners
MongoDB 3.2 is now generally available for production deployments - you can download the community version or MongoDB Enterprise Server today. This is truly a giant release. MongoDB 3.2 features better support for robust, highly available multi-data center deployments, document validation to ensure you can leverage our flexible data model without sacrificing governance controls for data quality, improved tools for analytics, and much more. Click to tweet : .@MongoDB 3.2 is now generally available spr.ly/6006BrNvn Let’s take a look at what’s inside. New Storage Engines for New Use Cases We’re introducing new storage engines that extend the capabilities of MongoDB, including an in-memory storage engine for the most demanding real-time apps (currently in beta) and an encrypted storage to secure data at rest. Document Validation In MongoDB 3.2, you can now get the benefits of a flexible data model without sacrificing governance. With document validation , you can define rules on what's being stored in your database. MongoDB Compass MongoDB 3.2 introduces MongoDB Compass , a new tool that allows developers and DBAs to visualize and explore their MongoDB data without having to use the MongoDB query language. It’s a sophisticated and simple to use GUI. BI Connector The new BI Connector in 3.2 enables analysts, data scientists, and business users to visualize MongoDB data with industry-standard SQL-based BI platforms such as Tableau, Qlikview, and more. And so much more We’re only scratching the surface with the above. MongoDB 3.2 also introduces $lookup to join data across collections, enhancements to Cloud Manager and Ops Manager , partial indexes, and so much more. Learn more in our about MongoDB 3.2 page . Community Contribution & Bug Hunt Winners As always, we couldn’t have done it without the ongoing contribution and feedback from our community. Thank you to everyone who participated in the Bug Hunt and provided us with feedback on the new functionality. We’ve selected this year’s winner and honorable mention: Winner - Stuart Hall Stuart found SERVER-21690 , a 100x performance regression in text search with phrase matching with text index v3. After the bug was identified and fixed he helped us test the fix. Stuart has also reported other issues that are being investigated. Honorable Mention - Nick Judson Nick submitted SERVER-21434 , uncovering a bug in findAndModify returning unexpected results when there are multiple readers. The first prize winner and honorable mention received a $1500 and $500 Amazon gift card respectively, a free ticket to MongoDB World 2016, and a reserved front row seat at the conference. Congratulations to the winners and thanks to everyone who downloaded, tested and gave feedback on our release candidates. Learn More There are many ways to learn more about the newest version of MongoDB. Review our about MongoDB 3.2 page Read the What’s New in MongoDB 3.2 white paper Learn about 3.2 left outer joins and other aggregation enhancements in our 3 part blog series Watch the What’s New in MongoDB 3.2 on-demand webinar Review the 3.2 release notes Register for our presentation on Best Practices for Upgrading to MongoDB 3.2 The best way is to download and try it out. We’re excited for you to download MongoDB 3.2, click below: Download Community Download Enterprise
Security in Government Solutions: Why Secure By Default is Essential
Data security in government agencies is table stakes at this point. Everyone knows it’s essential, both for compliance and data protection purposes. However, most government agencies are working with solutions that require frequent security patches or built-on tools to protect their data. Today, the federal government is pushing its agencies to move to modernize their solutions and improve their security posture. For example, the DHS and Cybersecurity and Infrastructure Security Agency’s recently issued technical rule for modernization of the Protected Critical Information Infrastructure program – a program that provides legal protections for cyber and physical infrastructure information submitted to DHS. “The PCII Program is essential to CISA’s ability to gather information about risks facing critical infrastructure,” said Dr. David Mussington, Executive Assistant Director for Infrastructure Security. “This technical rule modernizes and clarifies important aspects of the Program, making it easier for our partners to share information with DHS. These revisions further demonstrate our commitment to ensuring that sensitive, proprietary information shared with CISA remains secure and protected.” So how can government agencies modernize their data infrastructure and find solutions that not only protect data but also power innovation? Let’s look into a few different strategies. 1. Why secure by default is key Secure by default means that any piece of software uses default security settings that are configured for the highest possible security out of the box. CISA Director Jen Easterly has addressed how using solutions that are secure by default is critical for any organization. “We have to have [multi-factor authentication] by default. We can't charge extra for security logging and [single sign-on],” Easterly said . “We need to ensure that we're coming together to really protect the technology ecosystem instead of putting the burden on those least able to defend themselves.” “The American people have accepted the fact that they’re constantly going to have to update their software,” she said. “The burden is placed on you as the user and that’s what we have to collectively stop.” Easterly is right. Secure-by-design solutions are vital to the success of data protection. The expectation should alway be that solutions have built-in, not bolt-on security features. One approach that’s gaining traction both in the public and private sectors is zero trust environments. In a zero trust environment, the perimeter is assumed to have been breached. There are no trusted users, and no user or device gains trust simply because of its physical or network location. Every user, device, and connection must be continually verified and audited. As the creator of zero trust, security expert John Kindervag, summed it up: “Never trust, always verify.” For government agencies, that means the underlying database must be secure by default, and it needs to limit users’ opportunities to make it less secure. 2. Security isn't just on-prem anymore; cloud is secure, too Cloud can be a scary word for public sector organizations. Trusting your sensitive data to the cloud might feel risky for those who handle some of the country’s most sensitive data. But, cloud providers are stepping up to meet the security needs of government agencies. There is no need to fear the cloud anymore. Government agencies and other public sector organizations nationwide are navigating cloud modernization through the lens of increased cybersecurity requirements outlined in the 2021 Executive Order on Improving the Nation’s Cybersecurity . “The Federal Government must adopt security best practices; advance toward Zero Trust Architecture; accelerate movement to secure cloud services, including Software as a Service (SaaS), Infrastructure as a Service (IaaS), and Platform as a Service (PaaS); centralize and streamline access to cybersecurity data to drive analytics for identifying and managing cybersecurity risks; and invest in both technology and personnel to match these modernization goals.” Also, the major cloud providers are well established, purpose-built options for government users. AWS GovCloud, for example, is more than a decade old and was “ the first cloud provider to build cloud infrastructure specifically designed to meet U.S. government security and compliance needs.” This push by the federal government toward cloud modernization and increased cybersecurity will be a catalyst in upcoming years for rapid cloud adoption and greater dependence on cloud solutions designed specifically for government users. 3. Security features purpose-built for goverment needs are essential Government agencies are held to a higher standard than those in the private sector. From data used in sometimes life-or-death missions to data for students building their futures in educational institutions (and everything in between), security has real-world consequences. Today, security is non-negotiable and like we explored above, it’s especially crucial that public sector entities have built-in security measures to keep data protected. So, what built-in features should you look for? Network isolation and access It’s critical that your data and underlying systems are fully isolated from other organizations using the same cloud provider. Database resources should be associated with a user group, which is contained in its own Virtual Private Cloud (VPC), and access should be granted by IP access lists, VPC peering, or private endpoints. Encyption in flight, at rest, and in use Encryption should be the standard. For example, when using MongoDB Atlas, all network traffic is encrypted using Transport Layer Security (TLS). Encryption for data at rest is automated using encrypted storage volumes. Customers can use field-level encryption to encrypt sensitive workloads which enables you to encrypt data in your application before you send it over the network to MongoDB clusters. Users can bring their own encryption keys for an additional level of control. Granular database auditing Granular database auditing allows administrators to answer detailed questions about systems activity by tracking all commands against the database. This ensures you always know who has access to what data and how they’re using it. Multi-factor authentication User credentials should always be stored using industry-standard and audited one-way hashing mechanisms, with multi-factor authentication options including SMS, voice call, a multi-factor app, or a multi-factor device, ensuring only approved users have access to your data. MongoDB Atlas for Government: Purpose-built for public sector As we’ve discussed, solutions that are purpose-built with built-in security are ideal for government agencies, and choosing the right one is the best way to keep sensitive data protected. MongoDB Atlas for Government on AWS GovCloud recently secured its FedRAMP Moderate authorization thanks to these security measures built into the solution. FedRAMP is a government-wide program that provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services. To ensure the utmost levels of security, Atlas for Government is an independent, dedicated environment for the U.S. public sector, as well as ISVs looking to build U.S. public sector offerings. Public Sector organizations carry a heavy burden when it comes to keeping data protected. However, with the right data platform underpinning modern applications – a platform with built-in security features – progress doesn’t mean you have to compromise on security. Want to learn more about data protection best practices for public sector organizations? Attend our upcoming webinar on April 12 for deeper insight .