The cloud is the future of networking. Over the last few years, we’ve heard from more and more of our customers that they are considering public or private cloud as an option to either supplement or replace some of their traditional data centers. As the industry leading provider of network test access points and purpose-built packet brokers, I realized that Garland Technology needed to develop a cloud TAP solution that would provide our customers with the same level of access to their data in the cloud, that we have traditionally provided with our hardware solutions.
I’m excited to announce the private preview of Garland Prisms, the most advanced, easiest, and most affordable way to get cloud packets to your tools and teams. Born in the cloud, Garland Prisms is a 100% passive cloud TAP solution that works with any Public or Private Cloud, providing the essential traffic visibility needed for security and DevOps monitoring and inspection.
There are inherently blind spots in Public and Private Cloud workloads. Providers offer limited access to these workloads, to acquire, process, and distribute packet data in the cloud. Furthermore, the visibility they do provide is expensive and complicated for users to learn. This leads to limited application and network monitoring for troubleshooting, diagnostics, as well as security monitoring for threat hunting and forensics.
Prisms solves this problem for users deploying Public and Private Clouds all in one platform, with 3 simple steps; Acquire, Process and Distribute packets from VMs and containers in any cloud.
Acquire
Packet traffic is collected from dynamic resources, including Windows and Linux VMs, containers, and container services. Our nextgen, zero-touch sensor uses generic mirrors to see all of your traffic.
Process
Garland Prisms processes traffic by aggregating and filtering the packets using leading-edge, elastic processing services inside your subscription, minimizing impact on resources and exit charges from your cloud provider.
Distribute
Garland Prisms allows you to distribute processed cloud packet traffic to any IP address via a GRE/VXLAN encapsulation - in the Cloud or on-prem in your data center. Distribution and replication to individual tools or load balanced clusters in-cloud, or to legacy tools on-premise (off-cloud) in private data centers ensures maximum flexibility and investment protection.
Garland Prisms is cloud native; it was developed in the cloud, for the cloud. Through a Global SaaS Manager deployed in AWS, there is one simple and easy to use management platform for both Public and Private environments. Prisms is also platform agnostic, with a single multi-cloud environment that works across VMware, Hyper-V, and KVM private clouds, and AWS, Azure, Google, and IBM public clouds. Along with our simplified licensing model, this creates a frictionless deployment whether you are using one cloud workload or many.
Garland Prisms is the ideal solution for both Public and Private Cloud environments. With a powerful processing function, flexible distribution and a solution architected for the cloud, Prisms is by far the easiest and most affordable solution for enterprises today.
Looking to add visibility to your cloud deployment, but not sure where to start? Join us for a brief network Design-IT consultation or demo. No obligation - it’s what we love to do!
If the inline security tool goes off-line, the TAP will bypass the tool and automatically keep the link flowing. The Bypass TAP does this by sending heartbeat packets to the inline security tool. As long as the inline security tool is on-line, the heartbeat packets will be returned to the TAP, and the link traffic will continue to flow through the inline security tool.
If the heartbeat packets are not returned to the TAP (indicating that the inline security tool has gone off-line), the TAP will automatically 'bypass' the inline security tool and keep the link traffic flowing. The TAP also removes the heartbeat packets before sending the network traffic back onto the critical link.
While the TAP is in bypass mode, it continues to send heartbeat packets out to the inline security tool so that once the tool is back on-line, it will begin returning the heartbeat packets back to the TAP indicating that the tool is ready to go back to work. The TAP will then direct the network traffic back through the inline security tool along with the heartbeat packets placing the tool back inline.
Some of you may have noticed a flaw in the logic behind this solution! You say, “What if the TAP should fail because it is also in-line? Then the link will also fail!” The TAP would now be considered a point of failure. That is a good catch – but in our blog on Bypass vs. Failsafe, I explained that if a TAP were to fail or lose power, it must provide failsafe protection to the link it is attached to. So our network TAP will go into Failsafe mode keeping the link flowing.
Single point of failure: a risk to an IT network if one part of the system brings down a larger part of the entire system.
Heartbeat packet: a soft detection technology that monitors the health of inline appliances. Read the heartbeat packet blog here.
Critical link: the connection between two or more network devices or appliances that if the connection fails then the network is disrupted.