For modern security teams, tools are only half the battle. The other half? Having the bandwidth and expertise to act on what those tools uncover. That’s where co-managed services come in—and according to Patrick Sullivan, CTO of Security Strategy at Akamai, they’re no longer optional.

“Security teams have more alerts and risks being flagged than they have hours in the day,” Sullivan says.

While Akamai’s DNS Posture Management platform offers a powerful self-service model, it also recognizes the operational challenges many teams face. For organizations lacking deep DNS knowledge—or simply stretched thin—Akamai provides optional co-managed services to help close that execution gap.

This isn’t new territory for Akamai. The company already supports customers through its Security Operations Center (SOC), helping mitigate DDoS attacks, push zero-day policy updates, and manage app security configurations. Now, that same model extends to DNS.

“If an organization chooses to have an expert assist them, that help is available to co-manage things,” Sullivan explains. That support includes reviewing risks related to DNS and certificates and guiding internal teams through remediations.

The value shows up fast. “We often will be on a call synchronously as someone adds a cloud or DNS provider. A scan runs, and usually within 10 minutes we’re starting to see results,” says Sullivan.

While public DNS providers like Akamai are typically integrated on day one, internal DNS often follows in phase two. “Internal DNS is not quite as easy—it requires a bit more work—but it’s typically part of a subsequent rollout phase.”

Once in place, Akamai ensures tight integration with customer workflows, including SIEM systems and other orchestration tools, to embed security deeply into daily operations.

In a world where misconfigurations, stale records, and dangling CNAMEs remain persistent threats, DNS hygiene can’t wait on limited internal cycles. With co-managed services, security posture becomes actionable—fast.