One ASM job, done properly. One fixed price.

A new F5 Advanced WAF (ASM) policy built for one application: modelled, put into learning, staged and moved toward blocking, then handed over documented. The natural front door to a managed subscription.

• Delivered remotely, no site visit required
• Application modelled, template chosen, policy put into learning
• Staging review and staged move toward blocking
• Handover documentation for the finished policy

An audit of an existing Advanced WAF policy: enforcement state, signatures, entities, false positives and OWASP coverage, delivered as a prioritised findings report. The fastest way to find out what a policy is really doing.

• Delivered remotely
• Enforcement, signatures, entities and staging reviewed
• False-positive and OWASP-coverage assessment
• Prioritised findings and recommendations report

A device-wide F5 attack signature update across the whole ASM module. A signature update lands on every policy on the box, not just the ones under management, so this is priced per module, not per policy. We review the current signature state first and confirm the price.

• Priced per ASM module: base plus a per-policy unit
• Current signature state reviewed and the price confirmed up front
• Every policy on the module checked for safe staging before import
• Signatures applied, held in staging and reviewed against live traffic
• Learning suggestions and false positives worked through, then promoted to blocking with a before/after note

Which current F5 security advisories affect your applications, and whether your ASM policies and signatures already cover them. A fast, repeatable check that feeds straight into a signature update or a policy change.

• Delivered remotely
• Applications and policies mapped to current F5 advisories
• WAF/signature coverage assessed per exposure
• Remediation path and closure report

A tested iRule or Local Traffic Policy for Advanced WAF: selective policy bypass, header handling, custom logging or request steering. Where appropriate we convert the iRule to a Local Traffic Policy, the modern, HTTP-specific way to do the same job.

• Delivered remotely
• Local Traffic Policy created or adjusted, or an existing iRule converted where appropriate
• iRule written or adjusted where a Local Traffic Policy cannot do the job
• Tested against real requests before it ships
• Documentation of behaviour and attachment point