Learn more about how we empower good through innovation and alongside other organizations.

Recognizing the benefits of cloud storage and computing, former U.S. Chief Information Officer Vivek Kundra made the groundbreaking decision

In May 2012, the President of the United States issued a bold challenge to federal agencies, challenging them to optimize their digital services in order to better serve taxpayers across the country. An excerpt of the memo read:

Traditionally, organizations feel conservative and cautious about security. When companies and agencies first began making tentative moves to the cloud 15 years ago, security was one of their biggest concerns.

This post discusses the most common requirements of a data lake. Each section details the requirements followed by the technical implementation. If you are only interested in a particular requirement, directly jump to that section. An introductory read is [1] Benefits and concrete use cases of data lakes are discussed in.

You’ve made the decision to migrate to the cloud, and you’re eager to get started. But before you jump into creating a proof of concept (POC), it’s important to take a step back and think about your people. Why? In our experience, it’s common for the team—not the technology—

The General Services Administration (GSA) needed a way to keep the personal information of their more than 30 million customers safe—while making the log-in process as easy and painless as possible. In the past, government users had to create multiple logins for various agencies.

For colleges and universities around the country, the government’s embrace of the new Cybersecurity Maturity Model Certification (CMMC) means creating a plan to get compliant—or risk losing out on millions of dollars in grant and research funding. Follow along to learn the basics.