MongoDB University MCP Spotlight: Nestor Campos

MongoDB
October 29, 2014 | Updated: March 9, 2017
#Releases

As part of MongoDB University’s 2 Year Anniversary, we are sharing stories from our MongoDB University classes to showcase how they got started with MongoDB and where they’ve gone since graduation

This is a guest post by Nestor Campos, a software engineer and consultant from Chile who is a Certified MongoDB Developer, who will share his experience learning MongoDB through MongoDB University.

As a software engineer, I know I always need to keep my up with new technologies to stay relevant in the market.

After several years working with relational database, I found that they were not meeting the needs for all my projects, so after doing some research, I found the “non-relational”(NoSQL) databases and started experimenting with them. I decided to work with MongoDB, for its simplicity, ease of use and its wide range of use cases.

As soon as I started with MongoDB, MongoDB University opened, and I enrolled in the first course, M101P. It was difficult at first, but I learned quickly and working with MongoDB became more natural to me every day of the course.

After passing the M101 course, it was time to validate my work and get certified. I signed up to take the Developer Certification exam, studied for several months, and completed the course successfully. I was very excited and after completing the course, was motivated to continue working with MongoDB.

All of the courses and certification I’ve completed ​​through MongoDB University have helped give a new vision to the projects I work on, and opened a range of possibilities for my the entire organization.

The knowledge I built through MongoDB University allowed me to give back to the community and get ahead at work. After getting certified, I taught some workshops on Big Data. Starting next week, we are starting a large project that will involve collecting and manipulating data from social networks, and MongoDB was already defined as the core database to meet our objectives. Now I feel like a real Big Data engineer.

I am now certified as a MongoDB Developer and my goal is to become a certified MongoDB DBA next year. I hope more community members will take advantage of MongoDB certification and share the benefits of MongoDB within their organizations and to their clients.

← Previous

MMS Release Notes : RHEL7 support for MongoDB Monitoring and MongoDB Backup

Our release this week is a tiny bit delayed, for those of you who are tracking it, due to an internal MongoDB engineering conference. There’s lots going on here at HQ, including but not limited to our upcoming release of MongoDB 2.8 . As for the MMS release this week, we’ve been very busy: UI & Core Massive under-the-hood Javascript refactor Additional API functionality (users can now add host aliases) Changes to the settings page - users can now leave a group, add a group, and go to each group via their personal groups list Automation Additional instructions for command line for the automation agent. If you’ve never used the command line before, we’ve got you covered. There’s also a fancy copy-to-clipboard widget. Ability to define CNAMEs for config servers that are provisioned on own hardware (i.e. where the customer is managing DNS themselves). Backup For backup customers, you’ll notice that restore jobs now calculates download/transfer time estimate and displays it in the UI Agent improvements New backup and monitoring agents that work with RHEL7 and the newest version of Monitoring Agent will now send dbStats for all databases, even if you have more than 100 of them! Check out all these updates and more at mms.mongodb.com !

October 29, 2014
Next →

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 .

March 28, 2023