Gigamon is launching Hawk, an elastic visibility and analytics fabric for all data-in-motion across any cloud network.
Hawk delivers:
- Elastic visibility for any cloud. Hawk’s visibility-as-code can be embedded into cloud automation to elastically scale-up and scale-out on demand. A single, consumption-based licensing model operates seamlessly across any cloud, public or private.
- Cloud visibility for network tools. Hawk provides traditional network tools with immediate, agentless visibility into layers 2-7 across any cloud network.
- Network visibility for cloud tools. Hawk delivers the “ground truth” of data-in-motion to cloud tools, such as visibility into east-west container traffic and unmanaged devices, through network application metadata.
Thanks to this elastic visibility, Gigamon Hawk radically simplifies hybrid infrastructure, eliminates security and compliance holes and provides IT teams full visibility of their cloud environments at scale. Hawk is available in a subscription, scale-as-you-grow, business model including embedded support and is comprised of:
- A suite of visibility nodes that can scale-up and scale-out as needed across any cloud network
- A cloud data warehouse for security and operational analytic applications
- A single, simple interface for either drag-and-drop manageability or programmatic orchestration
Hawk is integrated with AWS and other leading cloud platforms and tools, providing a unified view across hybrid infrastructure. Hawk for AWS includes features such as elastic visibility that automatically scales out to capture traffic from new EC2 instances, efficient distribution of mirrored traffic to multiple tool destinations, and the ability to extract and store network and application metadata in an AWS storage bucket for near real-time or historical analysis.
“Helping our customers derive value from their cloud investment and solutions is the most important aspect of our work at AWS. As organizations move workloads to the cloud, they want to ensure that they have clear visibility around potential vulnerabilities in their environment. Using AWS with Gigamon Hawk, for example by leveraging Amazon Athena to analyze application metadata collected by Hawk in S3 buckets, customers can gain the visibility they need across their hybrid – or pure cloud – infrastructure to be confident in its security, performance and scalability,” commented Scott Ward, Principal Solutions Architect at AWS.
“We are seeing most of our clients accelerate the movement of their mission-critical apps and workloads to the cloud, resulting in increasingly complex hybrid cloud infrastructures and interactions. This rising complexity challenges IT and InfoSec teams to provide the comprehensive traffic visibility and control that has become the hallmark of optimized and secure networks required to deliver the best user experience. Because traditional network monitoring tools struggle with visibility into cloud activity, increasing cloud adoption will heighten the presence and criticality of network blind spots. Here, cloud visibility and control problems can best be solved by next generation, cloud visibility solutions like those from Gigamon,” said Mark Leary, Research Director with IDC.
“While the path to the cloud varies for every enterprise, managing IT complexity is the universal challenge we have seen among the more than 700 customers who have purchased our cloud visibility fabric. We are proud to be working with AWS and other cloud leaders to deliver solutions that simplify our customers’ ability to reap the benefits of cloud adoption,” said Michael Dickman, Chief Product Officer at Gigamon. “With Hawk, we enable enterprises to simplify and secure today’s hybrid cloud networks and feel confident in their ability to scale for tomorrow’s business needs.”
The Latest
Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...
Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...
Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...
While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...
For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...
As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...
The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...
The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...
Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...
Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...