At R6 Security we truly strive for transparent, fluent & easily understandable solutions.

Our headquarters and management are located in Silicon Valley, our R&Ð is in Europe. We are building upon open source technologies such as Kubernetes, Envoy, Nginix, and Vitesse, amongst others.

Do I need to change my infrastructure to use Phoenix?

Not at all. Phoenix is a non-intrusive solution. Although currently we prefer cloud native deployments (Kubernetes, Envoy, Ambassador, Istio, etc).

What is the performance overhead of your technology?

Dependent on the size of the time windows you leave for hackers; usually negligible.

What kind of applications can we use Phoenix for?

At the moment we provide it for Kubernetes environments, Envoy proxy and DNS servers (Layer 3 and Layer 4). We are planning to extend to Layer 2 in Q3 2021.

Do you change the operating system or applications binary?

We do not change the operating system at all. We change how the application loads into the memory as it loads, without affecting anything in the application.

What specific problems does Phoenix solve?

Phoenix was designed to counter route control, ransomware, defacement attacks in a simple and effective way. We developed an architecture where zero trust and node-based technologies apply. A proper MITRE ATTACK framework is available upon request.

What is the problem with existing DNS infrastructure?

The current infrastructure is working on legacy architecture, where latency is a significant problem. Controlling the route resolution, dependency on trust in authoritative sources are causing DNS hijacking to be one of the easiest ways to attack.

What is the problem with existing Kubernetes infrastructure?

Kubernetes is getting very popular with the user and fan community growing. The whole system is complex enough to cause users to make mistakes in configuration. There are lots of vulnerabilities still open and it takes a real expert to navigate through this. We have automated this for you.

What underlying technology do you use?

Phoenix takes advantage of new technologies - such as Kubernetes, Envoy, F5 NGINX  to create its Moving Target Defense play in a fast, scalable and cost-effective way.

What is moving target defense?

Known as MTD, this strategy introduces a dynamic, constantly evolving attack surface across multiple system dimensions. This increases uncertainty for bad actors and complicates their attacks. In the end, hackers can’t attack what they don’t see.

What problems does it solve that DNSSEC does not?

We are big fans of DNSSEC. It would be great if it were not based on signatures and being applied everywhere. We don't rely on signatures and basically apply zero trust in our offering. No matter if a hacker gets in and infects the DNS server... we make it self healing! We are also easy to apply, way easier than DNSSEC.

Okay, okay… but where do we fit into the classic Gartner categories?

Our technology can protect applications, OS and eventually networks. We believe we are part of the classic CWPP (Cloud Workload Protection Platform) playground.