IPv4 surcharge - Your AWS bill is going up this February
Here's how to save money and be more secure!
🚀 As 2023 draws to a close, we reflect on an extraordinary year at Border0 filled with remarkable achievements.
Today we're excited to announce our official release of the Border0 Terraform provider.
Today, we're excited to unveil the latest iteration of the Border0 connector, a fully cloud-managed solution designed to make access management effortless and all managed from the Border0 Dashboard. Built on valuable feedback from our user community, this update specifically tackles the complexities of managing dynamic and ephemeral services in today's fast-paced landscape.
Today we’re excited to announce our custom policy integration. This allows you to extend our policy language, with an API call to one of your systems, allowing you to code up any policy logic you’d like.
Dynamic access control to your servers based PagerDuty schedules
In today’s blog, we’ll take a closer look at Policies in Border0 and how they can help administrators control who should have access to your services and under what conditions. We’ll also look at the real-time & continuous authorization features in Border0 and explain why this differs from most solutions today.
Amazon Relational Database Service (RDS) is a popular, fully managed database that's become the database of choice for many. These databases typically contain sensitive data, so isolating the database in private VPCs is a pretty typical and wise architecture. But this setup comes at a cost, since it’s isolated, it also makes life harder for human database administrators and engineers who need access. That's where Border0 comes in, offering the perfect combo—an isolated AWS RDS database in a private VPC for that peace-of-mind security while also providing easy access to only those who need it, as if the database was right under their desk. And the best part? No security compromises! It's a win-win!
Are you tired of constantly refreshing your monitoring and log dashboards to keep tabs on your infrastructure? Do you sometimes feel like you need a sixth sense to catch those pesky login and audit events before they cause trouble? Time to solve that! 🚀
At Border0, we believe that identity-based access is the key to securing your resources and services. That's why we're thrilled to announce our latest feature: custom identity providers.
At Border0, we understand that managing and accessing your servers and databases can be a hassle, especially when it comes to security and enforcement. That's why we're dedicated to providing low-friction access, with the added bonus of visibility and security. And to achieve this, it's important to have the right tools for the right users. That's why we're excited to introduce the Border0 Desktop App.
Welcome to the world of modern infrastructure, where things are always changing and moving at lightning speed. As engineers, we know that managing access to dynamic and ephemeral services can be a real pain. Whether you're working with multiple cloud providers, virtual machines that come and go, or using container orchestration systems like Kubernetes, keeping track of all your resources can be a daunting task. But don't worry, we've got you covered with the Border0 connector.
In this blog post, we'll take a look at how you can use Border0 to access your SSH services using your Single Sign-on (SSO) credentials. That means no need to manage, ship, and rotate SSH keys, as well as flexible policies to control who has access to your SSH servers, when and from where. Best of all, your servers can run in a private network, such as behind NAT or a private VPC, and your users will be able to access them without the need for a VPN!
In this blog, we'll look at how easy it is to make a private database available without the need for a VPN and using just Single Sign On credentials. That means no more shared credentials to access your database and flexible policies to define who has access. And, as a bonus, you'll also have session recording!
If you’re in the world of cloud infrastructure, then you’ve heard of Kubernetes. Some of you are experts already, while some of us are just learning or getting started. In this blog, we’ll introduce a mysocket controller for Kubernetes and demonstrate how easy it is to use mysocket.io as your cloud-delivered load balancer for your Kubernetes Services. If you’re a Kubernetes user already, then it should just take a minute to get this mysocket controller setup.
In this blog post we'll look at how easy it is to make internal web applications available to authenticated and authorized users without needing a VPN. It's easy and will take you just 1 minute!
TLDR: I joined Andree and the incredible team at Border0 as a strategic advisor and cannot be more elated about the team, tech, TAM, and timing of the company launch.
In this article, we'll look at Mysocket's zero-trust cloud-delivered, authenticating firewall. Allowing you to replace your trusted IP ranges with trusted identities.
In this article, we're introducing SSH-aware sockets with SSH session recording and session replay. It is part of the Mysocket long-term vision to introduce more application-aware proxies. Having these identity and application-aware proxies allows the Mysocket service to provide more granular authorization policies specific to applications as well as better reporting and logging. Make sure to also watch the demo recording of this feature
In this article, we'll introduce session management as a first-class feature, crucial for security and compliance reasons. Session management and audibility will provide you with complete visibility and audit logging. It provides real-time information such as who is visiting what resources, when, and from where. We'll also look at how mysocket does continuous access evaluation. Finally, we'll show how you can terminate live TCP sessions with the click of a button!
About nine months ago, I posted the first blog post on the mysocket website, announcing mysocket. The mysocket service has continued to evolve over the last year, both in the underlying technology, vision, and use cases. I figured it's time for a bit of a refresh and clear articulation of what Mysocket is, what problems it is solving, and where it is heading.