Cloudflare and service protection
Buying a web application firewall for council forms
Keep legitimate council applications moving when a managed firewall rule changes. Define test submissions, exception ownership and a support handover.

A resident uploads a site plan, presses submit and gets a block page. The firewall might be doing its job, or a legitimate application might have hit a rule. In both cases someone needs to tell the resident what happened and determine whether the council received the application.
Start with the documents residents send
List the high-value journeys behind the firewall. Include the initial form, saving a draft, uploading a permitted file, submitting and retrieving a receipt. Record the accepted sizes and file types from the service specification. Use invented applications and harmless sample documents when testing.
Ask the portal team whether an interrupted submission could leave a file without an application or an application without a payment reference. A firewall supplier can report a blocked request. Only the application owner can confirm what was saved. Put both roles in the review.
Give rule changes an owner
Cloudflare publishes managed rulesets and updates them. Ask which rulesets the quote includes, where the team reviews events and how someone learns about a change that affects an important form. Confirm those features against the proposed plan.
Write down who can approve a narrowly scoped adjustment, when it will be reviewed and how staff will tell whether it restored the resident journey. Keep an approvals record with the agreed purpose. A support ticket should never require the applicant to send their original documents to the firewall operator.
Use an ordinary application as the acceptance test
Have a tester complete the journeys in an approved test environment using the devices residents commonly use. The service desk should be able to take the time of the incident and the reference shown on screen, locate the relevant event and route it to the correct owner. Record successful receipts as well as blocks.
The most revealing question in a supplier demonstration is what the resident does next. Give the tester a deadline and a failed upload. Check that they can reach an alternative channel, preserve information already entered where possible and find out whether a repeat submission is needed. That is a service outcome the buyer can verify.