Skip to content
Akamai audit and configuration: protection that is actually active

Akamai audit and configuration: protection that is actually active

On Akamai, a policy left in alert mode or a module paid for but never tuned is protection you pay for without benefiting from it. Our experts audit your configuration, fix the gaps and can run it for you up to 24/7.

Observation before blocking

Every tightened rule is measured before it is enforced, so your customers are never wrongly blocked.

Gaps ranked by severity

For each gap: the risk, the fix to apply and the estimated effort.

Remediation, operations and SOC

Remediation, acceptance testing, then Akamai alerts handled by our SOC up to 24/7.
# They chose our expertise

/ Our Clients

Logo
Logo
Logo
Logo
Logo
Logo
Logo
Logo
Logo
Logo
Logo
Logo
Logo
Logo
Logo
Logo
Logo
Logo

/
The 3 most common Akamai configuration mistakes

The contract is signed and the platform is running, but the actual level of protection depends entirely on the tuning.

Protection stuck in observation mode

Protection stuck in observation mode

App & API Protector policies left in alert mode since deployment, exceptions added for a false positive and never reviewed.
A poorly mapped attack surface

A poorly mapped attack surface

Exposed APIs missing from the inventory, and therefore unprotected, and an origin server reachable without going through Akamai.
Modules paid for but never used

Modules paid for but never used

Bot management or API Security switched on without tuning, alerts generated by the thousand that nobody reads.
The 3 most common Akamai configuration mistakes
/

What we check in your Akamai configuration

Eight areas reviewed, from security policies to how well your contract matches your usage.

WAF policies

WAF policies

Alert or blocking mode, rule updates, exceptions and rate controls.

Bot management

Bot management

Bot categories, the action applied to each, legitimate customers wrongly blocked.

API inventory

API inventory

Discovered APIs versus protected APIs, undocumented APIs, schema validation.

Origin and anti-DDoS

Origin and anti-DDoS

Origin access restricted to Akamai, Prolexic network protection if subscribed.

Delivery configurations

Delivery configurations

Cache rules, active versions, differences between staging and production.

Certificates and TLS

Certificates and TLS

Validity, renewal, versions and cipher suites.

Control Center access

Control Center access

Users, roles and API clients.

Contract versus actual usage

Contract versus actual usage

Modules paid for but unused, and conversely needs left uncovered.

/ How the audit works

Four steps. We never switch a rule to blocking without measuring what it would block.

1

Scoping and access

Scope (properties, policies, APIs) and a dedicated named account on Control Center. No changes without your approval.

Scoping Access
2

Analysis and external tests

Review of policies and exceptions, analysis of security logs, checks from the internet.

Audit Logs
3

Report and debrief

Gaps ranked by severity, risk explained in plain language, fix to apply. Verbal debrief with your teams.

Report Debrief
4

Remediation and acceptance

Every tightened rule runs in observation before blocking, then every fix is verified in acceptance testing.

Remediation Acceptance

/
What you receive at the end of the audit

A report built to be used: every gap is linked to a specific action, with a dedicated section on what you pay for without using.

  • An executive summary your leadership can read
  • The list of gaps, ranked: critical, important, improvement
  • For each gap: the risk, the fix to apply and the estimated effort
  • A prioritised remediation plan
  • Acceptance testing after remediation, to check every gap is closed
What you receive at the end of the audit
# After the audit

/ What happens after the audit?

The audit tells you what to fix. We can also do it for you, then keep your policies up to date as your applications evolve.

Policy remediation

Policy remediation

We apply the plan rule by rule, in observation before any blocking, then verify every fix in acceptance testing.

Operations up to 24/7

Operations up to 24/7

Continuous rule tuning and incident handling, from business hours to 24/7 on-call.

SOC integration

SOC integration

Akamai logs analysed by our analysts: a tool whose alerts nobody reads protects nothing.

Broader security audit

Broader security audit

Penetration testing and architecture review, to cover what Akamai cannot see.

/
Why entrust your Akamai to Castelis?

A security tool whose alerts nobody acts on protects nothing. Our teams tune policies methodically, observation before blocking, and connect Akamai to a complete detection and response chain.

  • Over 25 years of experience and more than 500 projects delivered
  • Over 80 people at Castelis, a hunik group company bringing together 7 specialist firms
  • Castelis is ISO 27001:2022 certified

Using another CDN as well? We also audit Cloudflare and bunny.net.

Why entrust your Akamai to Castelis?

/ Related technologies

Akamai fits into a wider detection and response chain, which we build around your architecture.

Akamai Microsoft Sentinel Cloudflare bunny.net Splunk QRadar CrowdStrike MISP Kibana
Icon Stack tailored to your architecture and compliance obligations.

/
Frequently asked questions

Akamai is an internet infrastructure services provider founded in 1998 and listed on Nasdaq under the symbol AKAM. Its platform, present in more than 700 cities according to the vendor, covers application security (firewall, API protection, anti-DDoS), content delivery and cloud computing: security rules and caching are applied as close to the user as possible. The company generated 4.21 billion dollars in revenue in 2025, with more than 11,500 employees. It is mostly found where downtime is costly: banking, insurance, retail, media, healthcare and public services.

The vendor’s support handles incidents on the platform. Regular review of your policies, your exceptions and your actual exposure depends on your contract, and is often left to you. Yet this is where protection erodes: an exception added for a false positive, an API deployed without being inventoried, a policy never switched to blocking. The audit gives you an independent view.

No. During the audit, we analyse your policies, configurations and security logs without changing anything. No fix is applied without your approval, and every tightened rule first runs in observation to measure what would be blocked before blocking it.

A dedicated named account for our experts on Akamai Control Center, with the permissions needed for the audit and then, if you ask us to handle remediation, for its implementation. Access is removed at the end of the engagement.

A WAF, or web application firewall, filters web requests to block known attacks. A WAAP, for web application and API protection, adds API security, bot management and protection against application-layer DDoS attacks. Akamai’s App & API Protector is a WAAP: the audit checks that each of these protections is actually tuned, not just switched on.

It depends on the number of properties, policies and APIs to cover, and on the modules subscribed. The initial scoping sets the scope and the schedule before any commitment.

The audit is quoted after an initial scoping call, based on the scope and the modules to cover. Remediation and operations are covered by a separate proposal, if you would like us to handle them.

No. Akamai detects and blocks at application and network level, and produces a large volume of logs and alerts. Someone still has to analyse them, qualify the attacks and tune the rules. We connect Akamai logs to our managed SOC so that detection leads to an effective response.

CONTACT

Get your Akamai configuration checked