Teleport, an Access Plane company, is announcing today that it has secured $30M in Series B funding. The company also released its latest version of its offering, Teleport 7.0 – introducing identity-based access for MongoDB . This funding round is led by Kleiner Perkins and follows the company’s record-breaking quarter, with net new annual recurring revenue up 5x and total annual recurring revenue up 2.5x, compared to the second quarter of 2020.

MongoDB is one of the most popular open-source databases. Unfortunately, this also means ubiquity of misconfigured and unsecured MongoDB deployments out in the wild. Just in recent years, we’ve seen several hacks involving thousands of MongoDB databases left exposed online without any protection, making them ripe for the hacker’s picking. It doesn’t have to be this way, though.

There’s simply no denying that Data is the currency of the future. All businesses have one or more databases and are naturally heavily reliant on them not only to store information, but also to utilise the data to make business informed decisions. Whether it’s payroll data, employee records, customer information, financial information or even inventory data today’s list of Data is endless.

MySQL brands itself as the world’s most popular open source database. As popular as MySQL database is among developers and SQL enthusiasts, it is equally popular amongst hackers. Misconfigured server access, overprivileged roles, and weak authentication schemes are the most common security issues in MySQL database. While access control features provided by MySQL are adequate enough at the SQL level, it is error-prone to manage access at the operational level.

Enterprises are undergoing a dizzying pace of digital transformation. For many organizations, real-time analytics and insights are critical to the success of their transformation, and SAP HANA has become their database of choice, making their protection a must. While SAP HANA provides a rich ecosystem of native backup and recovery tools to specialist DBAs, they are often not accessible by the backup and infrastructure teams.

The choice for persistent storage for your cloud native applications depends on many factors including how your cloud journey started and whether your applications were migrated or developed for the cloud. Also, depending on how early you started using containers and migrated to Kubernetes, your distribution or managed service may not have offered the persistent data services you needed.