Intern Spotlight: Maggie Gibson

Maggie Gibson
September 1, 2015
#Company

This year, MongoDB welcomed 34 university students to our intern program in Engineering and Marketing. In this series, we'll introduce you to some of the talented students who are helping us transform development and operations for how we run applications today.

We had the chance to sit down with Maggie Gibson who is working as the Corporate Communications Intern on the Corporate Marketing Team.

Where are you originally from, where do you go to school and what year are you?

I was born and raised in New York City and I am a rising senior at Trinity College in Hartford, CT.

What activities are you involved with at school?

I am the President of my A Cappella group, the Trinitones. I am also a member of Amnesty International and work as a Student Admissions Associate in the Admissions Office.

What department are you working in this summer?

This summer I’m working as the Corporate Communications intern. I work on a lot of projects including (but not limited to) tracking media coverage, researching industry trends and writing blog posts.

Why did you choose to intern at MongoDB?

I knew this summer I wanted to explore the communications industry. MongoDB was new for me and I was excited to learn about both the technology itself and the growing industry. I could also tell from the interview process that MongoDB was a fun place to work with a supportive team. The Corporate Marketing team was driven, passionate, funny, welcoming, and would ensure that I got a lot out of my time with them, which I really valued.

Best thing about the MongoDB office?

All the free food.

Favorite intern event?

It’s a tie between the company wide picnic and the trapeze trip! I also love the Intern Speaker Series where we get to talk with MongoDB executives.

What does a typical day look like for you?

Honestly, every day is different, which I love. Typically, I get in about 9:00am and track any news and press about MongoDB. I work on multiple projects throughout the day like researching industry trends, working on presentation decks, drafting social copy and writing blog posts. The Corporate Marketing team touches every department, and every day I get to work on many different projects with people across the company.

If you could add one snack to the office what would it be?

Jolly Ranchers.

What is the most challenging part of your job?

The most challenging part for me was also the most exciting -- entering an industry that I had limited prior knowledge of. I had to learn about new terminology, new companies, new websites, and a lot of other information. It required a lot of time, effort, and flexibility adapting to a new environment. Even though I’ve learned a lot and challenged myself, I’m still learning every day.

What is the one thing you couldn’t live without?

My planner. As much as I love technology, if I don’t write things down and make lists my head will explode.

If you could travel anywhere in the world, where would it be?

I’ve always wanted to visit South Africa and Australia. I love traveling and exploring new cultures.

Favorite App?

Snapchat.

Favorite TV show to binge watch?

Friends and Gilmore Girls.

Interested in a career at MongoDB? Check out our careers page or email campus@mongodb.com.
MongoDB Careers

About the Author - Maggie Maggie Gibson is a rising senior at Trinity College and the Corporate Communications Intern at MongoDB this summer.

← Previous

MongoDB 3.0.6-rc2 is released

MongoDB 3.0.6-rc2 is out and is ready for testing. This is a release candidate containing only fixes since 3.0.5. The next stable release 3.0.6 will be a recommended upgrade for all 3.0 users. Fixed in this release: SERVER-19464 $sort stage in aggregation doesn’t call scoped connections done () SERVER-19644 Seg Fault on cloneCollection (specifically gridfs) SERVER-19673 Excessive memory allocated by WiredTiger journal SERVER-19805 MMap memory mapped file address allocation code cannot handle addresses non-aligned to memory mapped granularity size SERVER-19987 Limit the size of the per-session cursor cache 3.0 Release Notes   Downloads All Issues As always, please let us know of any issues. – The MongoDB Team

August 31, 2015
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