Octarine complements Istio to ensure you have the security you need to optimize the value of your Kubernetes deployments. The enterprise-grade security capabilities of Octarine give you total visibility and control over all your containers, regardless of where or how they are deployed, so you can effectively enforce policies in support of your security and compliance initiatives.
Octarine helps you visualize your overall topology and policies, so you can quickly understand what’s going on and can make good, effective decisions that align with your corporate and security policy needs. With Octarine, you have a complete picture of all your service-to-service communications. There are no gaps or guesses – you can zoom in and easily get all the details you need, down to the API-level, so you can see individual service instances, load, and failures, both current and past, to see what’s really happening.
Octarine’s policy engine makes it easy to set and quickly adapt rules based on changes observed in the environment to optimize enforcement. There are granular controls over who can create or modify rules, with a complete audit trail for all policy creation and modification. Octarine’s policy engine can also automate policy creation and tuning for you to keep access control as tight as possible, without disrupting legitimate traffic.
Octarine was designed to be deployed in a wide variety of environments, including container- based, VM-based and serverless. Since its authentication framework is implemented via a layer 7 proxy, Octarine can operate within complex network topologies, including NAT, API gateways, and proxies, which are common when interacting with services outside of a single cluster.
Octarine is able to monitor and control interactions through a broker, such as RabbitMQ, Kafka or NATS. This allows you to see how and which services are accessing the broker, providing visibility into the specific message queues (AKA topics, subjects) managed by the broker. As a result, you have control over which services can be producers and consumers from each queue.
When Istio and Octarine are deployed together, you can: