Your cloud security posture is only as strong as the weakest link in your stack, and for most teams shipping applications at scale, that weak link is often hiding at the edge. Platforms like Akamai power critical functions such as DNS resolution, traffic routing, and property configurations, yet they’re often managed outside the same security workflows as cloud infrastructure. While teams spend significant energy locking down their cloud workloads, the edge layer frequently goes unaudited. A misconfigured DNS zone that exposes more than intended can undo all the hardening you've done deeper in the stack.

That's where our integration with Akamai comes in. The Wiz platform gives security and engineering teams consistent visibility across their entire infrastructure footprint, and by integrating with Akamai, this visibility is extended out to where your traffic actually enters the internet. By connecting Wiz to your Akamai environment, you can pull in Edge DNS zones and account-level metadata, and run them through the same posture analysis engine you already use for your cloud workloads. Rather than operating as isolated security tools, Wiz correlates configuration data across layers to surface what's actually exploitable, and that now includes your Akamai edge configurations.

Closing the gap between cloud and edge exposure

Modern application security can’t stop at the boundaries of your cloud environment, it has to account for how applications are actually delivered and exposed. As architectures become more distributed, the edge has become a critical part of the attack surface, but not always a well-understood one.

For developers in particular, this gap is where risk tends to hide. Edge misconfigurations are notoriously difficult to catch before they cause real damage, and the impact is showing up in real-world trends. Akamai's research documented 150 billion API attacks between 2023 and 2024, with authentication and authorization gaps among the leading causes, many of which stem from misconfigured edge behavior rather than flaws in application code. This leads to a disconnect between what teams believe they’ve secured in the cloud and how those services are actually exposed in practice.

Closing that gap requires context across layers. With the Wiz and Akamai integration, edge configuration data from Akamai is ingested into the Wiz Security Graph and analyzed alongside your existing cloud, identity, and runtime context, giving teams a unified view across layers to highlight what’s truly exploitable. An overly permissive edge rule, for example, can be evaluated in the context of the services it exposes, the identities that can access them, and the data they connect to, giving teams a single, cohesive understanding of risk from edge to runtime.

Enabling security teams to reduce risk at the edge

Wiz and Akamai together help teams stay ahead of edge risks by turning complex configuration data into actionable insights:

• Detecting Misconfigurations as they arise: A small change at the edge can have outsized impact. For example, a developer might update a DNS record to expose a new service for testing, but forget to restrict access before pushing to production. Akamai reflects that configuration, and Wiz ingests it, analyzes it in context, and flags that the service is now publicly accessible - so teams can catch and remediate the issue before it’s discovered externally.

• Prioritizing Risks Across the Stack: Not all misconfigurations carry the same level of risk. For instance, a permissive edge rule exposing a low-risk static asset has a very different business impact from one exposing an internal API tied to sensitive data. Wiz correlates Akamai edge configurations with cloud resources, identities, and data sensitivity to highlight which exposures actually create risk, so teams can focus on the highest-impact risks first.

• Bringing Developers and Security Closer Together: When a security team member flags an exposed endpoint, the root cause isn’t always obvious. A developer might have updated an Akamai routing rule that unintentionally made a backend service public. Wiz connects the Akamai configuration with the underlying service in one view, so both teams can quickly understand the issue and remediate it without back-and-forth.

• Continuous Monitoring for a Changing Edge: Edge configurations are constantly evolving: new domains are added, routing rules are updated, and traffic patterns shift. For example, a change made to support a new feature rollout might unintentionally broaden access to an internal service. As Akamai configurations update, Wiz continuously ingests and re-evaluates them, alerting teams to new exposures as they appear so they can respond in real time.

Get Started with Wiz and Akamai Today

The edge is no longer just a performance layer, it’s a critical part of your attack surface. By bridging the gap between infrastructure and exposure, the Wiz and Akamai integration helps you secure your applications from deployment to runtime.

Get started with the Wiz and Akamai integration, now in Public Preview. Joint customers can follow this guide (Login Required) to close the edge security gap in their environment.