Cyber insurance questionnaire: answering the web application questions from evidence
A renewal worksheet that keeps your web application evidence (the last test report, the retest ledger, access and backup records) apart from the exact wording of your insurer's questions, with one worked answer for a control that is only partly in place.
It is not insurance advice or legal advice: what your insurer requires and what your policy covers are questions for your broker.
On this page
Cyber insurance renewal worksheet for web applications
Not insurance advice and not legal advice. Copy the worksheet into a document or spreadsheet.
How to use itHide the instructions
Fill in Part A for each website or web application from documents you hold, copy each question or policy term from your own form into Part B word for word, and answer it only from Part A. Part C works one invented question through an invented test report and retest ledger as an illustration. What your insurer requires, and whether you are covered, are questions for your broker or insurer.
cyber-insurance-security-checklist.txt
Introduction18 lines
Part A. Common web application evidence55 lines
Part B. Insurer-specific questions and policy terms9 lines
Part C. Worked illustration38 lines
Whole template126 lines
CYBER INSURANCE RENEWAL WORKSHEET: WEB APPLICATION EVIDENCE Not insurance advice and not legal advice. This worksheet organises evidence you already hold, so you can answer accurately whatever your own proposal form or renewal questionnaire asks about your websites and web applications. It does not tell you what your insurer requires, whether you are covered, whether a claim would be paid or how any answer affects your premium. Put those questions to your broker or insurer. HOW TO USE IT 1. Fill in Part A for each customer-facing website or web application, from documents you can produce. Update it whenever one of those documents changes, not only at renewal. 2. When the renewal form arrives, copy each question or policy term that touches your websites, applications, access, backups or incidents into Part B, word for word, with its number. 3. Answer each Part B line only from Part A lines. If no Part A line supports an answer, its status is not checked or not in place. 4. Send every broker follow-up to your broker in one message before anyone signs, and file the reply with this worksheet. CONTROL STATUS (choose one per line) In place: true for every system, account and date the question covers, and you can produce the evidence. Partly in place: true for some systems, accounts or dates but not all. Name the exceptions. Not in place: not true today. Note whether a change is planned, who owns it and the month it is due. Not checked: nobody has confirmed it yet. Treat it as unknown, not as yes. A control status describes a control. Findings from a test carry their own retest outcome instead: fixed, partially fixed, still reproducible or not retested. Keep the two vocabularies apart. COLUMNS FOR EVERY LINE Status: ____ | Wording in your own form or policy, copied exactly with its number: ____ | Evidence and its date: ____ | Gap owner: ____ | Broker follow-up: ____ PART A. COMMON WEB APPLICATION EVIDENCE Repeat Part A for each website or application. Name: ____ Hostnames: ____ Built by: ____ Hosted by: ____ A1 Latest penetration test or security review report Record: provider ____ testing dates ____ report date and version ____ did the provider build or host it (yes / no) ____ Can support: a statement about this application, on the hostnames in its scope, for the testing dates. Cannot support: other websites, staff email, laptops, the office network, backups, or anything released after the testing dates. Status: ____ | Wording: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ A2 Scope as tested, and what the report left out Record: hostnames, roles and environment tested ____ items the report lists as out of scope or not performed ____ Can support: the outer edge of any answer built from A1. Cannot support: anything on the excluded list. Status: ____ | Wording: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ A3 Retest ledger Record, one row per finding: finding id ____ rating ____ outcome (fixed / partially fixed / still reproducible / not retested) ____ retest date ____ build retested ____ Can support: which findings were confirmed fixed on the retested build. Cannot support: a fix nobody retested, or the application as it has changed since the retest. Status: ____ | Wording: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ A4 Open items and the plan to close them Record: each finding not marked fixed, what will close it, who owns it and the month it is due ____ Can support: an accurate answer to a question about outstanding issues. Cannot support: "all issues resolved" while any row here is open. Status: ____ | Wording: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ A5 Administrator accounts Record: every account with administrator rights to the application, the hosting control panel, the domain registrar and the code repository; named or shared; multi-factor sign-in on (yes / no); the date the list was checked ____ Can support: who can change the application, and how each of them signs in, on the date checked. Status: ____ | Wording: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ A6 Multi-factor sign-in settings Record: a dated screenshot or export of the setting for each system in A5, and for the email account that receives password reset links ____ Check: does your form define what counts as a second factor? If it does, compare each setting with that definition ____ Status: ____ | Wording: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ A7 Backups of this application Record: what is backed up (database / uploaded files / configuration) ____ how often ____ where each copy is kept ____ one copy held outside the hosting account (yes / no) ____ date and result of the last test restore ____ Can support: a statement about this application's backups. Cannot support: backups of laptops, email or other business systems. Status: ____ | Wording: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ A8 Updates and patching Record: the date the platform, plugins and dependencies were last updated ____ open security alerts and how old each one is ____ who is responsible ____ Status: ____ | Wording: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ A9 Outside services, and who runs which control Record: the host, payment provider, sign-in service, email delivery service and any other service the application relies on; which controls each runs for you; the date you read its published security documents ____ Can support: answers about controls a provider runs on your behalf. Name the provider rather than presenting the control as your own. Status: ____ | Wording: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ A10 Incident register for this application Record: incidents and near misses in the period your form looks back over, or "none recorded", with the date you checked and who checked ____ Status: ____ | Wording: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ A11 Other web properties Record: every other site or subdomain on your domains (marketing site, landing pages, old campaign sites), who runs each one, and whether it has been tested ____ Why: a question that says "all internet-facing" or "all websites" reaches these too. Status: ____ | Wording: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ PART B. INSURER-SPECIFIC QUESTIONS AND POLICY TERMS Fill in one block for each question or term taken from your own documents: the proposal form or renewal questionnaire, the policy schedule, the policy wording and any endorsements. B__ Document, with its version or date: ____ Question or clause number: ____ Wording, copied exactly: ____ Definitions the document gives for words used in it (check any glossary): ____ Systems and period the question covers, as you read it: ____ (if you are unsure, make it a broker follow-up) Part A lines that answer it: ____ Draft answer, written in full before choosing any box: ____ Status: ____ | Evidence and date: ____ | Gap owner: ____ | Broker follow-up: ____ Questions about staff email, devices, the office network, phishing training or how payments are approved are answered from your IT provider's and finance team's records, not from Part A. Add them to Part B and name that source in the evidence column. PART C. WORKED ILLUSTRATION Everything in Part C is invented to show the method: the business, the question, the report and the ledger. The question is not quoted from any insurer's form, and the answer is not a recommended wording for yours. The business: an invented booking company. Customer portal and API at bookings.lab.test, built by an outside agency. Marketing site on a hosted website builder. Renewal date: 1 December 2026. The question (invented): "Q14. Have all internet-facing applications been penetration tested by an independent third party within the last 12 months, with all critical and high vulnerabilities remediated? Yes / No" What Part A already holds A1: tested by an external provider that did not build or host the portal. Testing dates 4 to 8 August 2026. Report version 1.0, dated 15 August 2026. A2: scope was the customer portal and its API on bookings.lab.test, customer and staff roles, staging environment. Not included: the marketing site, staff email, the office network. A3: retest of 20 October 2026, on build 3.9.2. F-01 Critical. A customer could open another customer's booking by changing an ID. Outcome: fixed. F-02 High. A staff member could raise their own role to administrator. Outcome: fixed. F-03 High. Password reset links could be used more than once. Outcome: partially fixed. Links now expire, but one link still works more than once before it expires. F-04 Medium. Spreadsheet formulas in the bookings export ran when the file was opened. Outcome: still reproducible. F-05 Medium. Error pages showed internal file paths. Outcome: fixed. F-06 Low. A cookie on the gift card page lacked a protective setting. Outcome: not retested, because the gift card feature was switched off before the retest. A11: the marketing site has not been tested. Step 1. Split the question into the claims it bundles together. (a) All internet-facing applications tested: partly. The portal and API were; the marketing site was not. (b) By an independent third party: yes, for the portal. The tester did not build or host it, and the report says so. (c) Within the last 12 months: yes. Testing ran from 4 to 8 August 2026. (d) All critical and high findings remediated: partly. F-01 and F-02 were fixed on retest; F-03 is partially fixed. Step 2. Choose the status: partly in place. Neither Yes nor No is accurate on its own. Step 3. Write the answer in full before touching the box: "Our customer booking portal and its API (bookings.lab.test) were penetration tested from 4 to 8 August 2026 by an external provider that did not build or host them (report version 1.0, 15 August 2026). The provider's retest on 20 October 2026, on build 3.9.2, recorded the critical finding and one of the two high findings as fixed. The other high finding was recorded as partially fixed; the remaining change is scheduled for release in December 2026 and will be retested after it ships. Our marketing website, which runs on a hosted website builder, was not part of the test." Step 4. Complete the columns. Status: partly in place Wording: Q14, copied exactly as above Evidence and date: report version 1.0, 15 August 2026; retest ledger, 20 October 2026, build 3.9.2 Gap owner: the agency's lead developer (the F-03 change and its retest); the operations manager (whether to test the marketing site) Broker follow-up: "Q14 is only partly true for us. How does the insurer want that answered: a box plus an attached note, or some other way? Does it want the retest summary? Does our marketing site count as an internet-facing application for this question?" Step 5. Keep what the question did not ask about on the record. F-04 is still reproducible and F-06 was not retested. Neither is critical or high, so Q14 does not reach them, but both stay in A4 with an owner, and the broker can be asked whether the insurer wants to hear about open findings below high. BEFORE ANYONE SIGNS - Every Part B line has a status, an evidence date and an owner. - Every partly in place and not checked line has a broker follow-up, and the broker has replied. - Dates and system names in each draft answer match the documents exactly. - If a line changes between signing and the date cover starts, tell your broker and write down when you did.
What a cyber insurance questionnaire is, and what this page is not
A cyber insurance questionnaire is the set of questions you answer about your business and its systems when you apply for cyber cover or renew it.
Your broker might send it as a PDF, a page in an online portal or part of a renewal pack. The Chubb form this page reads, for example, is titled a proposal form, and it says it allows Chubb to gather the needed information to assess the risks related to your information systems. Whatever the title, each answer is a statement your business makes to an insurer.
This page is not insurance advice and it is not legal advice. Cover, wording and requirements can differ by insurer, by policy and by business, so nothing here tells you what your insurer requires, whether you are covered, whether a claim would be paid, or whether any control or test changes your premium.
Those questions belong with your broker or your insurer, and the worksheet on this page has a column for them on every line.
What the page does is narrower. It helps you answer the questions that touch your website and web applications truthfully, from documents you can produce: the latest test report, the ledger showing which findings were retested and with what outcome, and the access, backup and incident records behind each control.
The worksheet keeps that evidence apart from the wording of any one insurer's questions, so the same evidence serves the next renewal, and the next customer who sends a security questionnaire.
Keep the evidence apart from the insurer's wording
Two kinds of material go into a renewal answer, and they age at different speeds.
The first is evidence about your systems: reports, ledgers, settings and records, each with a date on it. It belongs to your business and stays true until something changes. The second is the wording of the question in front of you: which systems it reaches, what period it looks back over, and how it defines its terms.
That belongs to one document from one insurer, and the next form you are sent may say it differently.
Answers drift when the two are mixed. A team that answers each form from memory can tick Yes for a control one year and write a qualified answer for the same control the next, with nobody able to say which was right.
The worksheet separates them on purpose. Part A holds the evidence for each web application. Part B copies each question or policy term exactly as your own documents give it, and every Part B answer points back to the Part A lines that support it.
If no Part A line supports an answer, that tells you something before the form is signed rather than after.
Copy the wording exactly, because the small words decide which evidence counts. "All", "every", "internet-facing", "critical systems", "independent", "regularly" and "in the last 12 months" each move the edge of the question. A paraphrase in your own words quietly widens or narrows it, and an accurate answer to the paraphrase may not be an accurate answer to the question that was asked.
- Part A, common evidence: the last test or review report, the scope it covered, the retest ledger, open items, administrator accounts, multi-factor sign-in settings, backups, updates, outside services, the incident register and any untested web properties.
- Part B, insurer-specific: the question or clause number, the wording copied exactly, any definitions the document gives, the systems and period it covers, the Part A lines that answer it, and a draft answer written in full.
- Every line, in both parts: a control status, the evidence and its date, a gap owner and a broker follow-up.
One published proposal form, read closely
To show what reading a form closely looks like, here is one published example.
It is one form, not a picture of the market. On 14 November 2026 we opened Chubb Insurance Australia's Cyber ERM Short MarketPlace Cyber Proposal Form, whose footer reads "Published 11/2023". Chubb's other forms, other insurers' forms and later versions of this one may ask different questions, so read the version you are actually given.
Its underwriting questions 2 to 10 are answered Yes or No. Among them: whether, within the last 3 years, you have had any cyber incidents, data breaches or privacy complaints, or become aware of any matter that could lead to a claim under a cyber insurance policy; whether, to the best of your knowledge, you comply with all relevant privacy laws and regulations in the jurisdictions in which you operate; whether your corporate network and email either cannot be accessed remotely or use multi-factor authentication where remote access is required; whether backups of business or mission critical systems are made at least weekly and stored offline; and whether you have a security tool protecting computers and handheld devices and an email security solution.
Apart from a field for your website, none of its questions mentions penetration testing, vulnerability scanning, websites or web applications. A test bought only to answer that form would have no question to answer. The questions it does ask are answered from records such as your IT provider's settings, your backup records and your incident register.
If the form in front of you does ask about testing, the rest of this page applies; either way, read the form before booking anything.
Two more details on that form are worth looking for in yours. Its glossary defines multi-factor authentication and says a shared secret key, an IP or MAC address, a VPN, a monthly reauthentication procedure or VOIP authentication are not considered secure second factors, so if your second factor is one of those, raise it with your broker before answering.
And in its declaration the signing officers declare that, to the best of their knowledge and belief, the statements in the proposal are true, and that notice will be given as soon as practicable if any of the information changes between the date of the proposal and the proposed date of inception of the insurance.
Under the heading "Not a Renewable Contract", the form also says cover under the policy terminates at the expiry of the period of insurance, and that for similar insurance for a later period it will be necessary to complete a new proposal form before the current policy ends.
For cover arranged on that form, a later period means a fresh set of answers, which is the moment Part A of the worksheet is built for.
What the Insurance Contracts Act 1984 says about disclosure
The Chubb form above asks you to read its notice on the duty of disclosure before completing it, so it helps to know where the law sets out a duty of disclosure.
The Insurance Contracts Act 1984 (Cth) deals with it in Part IV, headed "Disclosures, misrepresentations and use of certain information". The sections below are taken from Compilation No. 33 on the Federal Register of Legislation, which shows the Act as amended and in force on 8 October 2026. They are paraphrased closely, not interpreted.
- Section 21(1): subject to the Act, an insured has a duty to disclose to the insurer, before the relevant contract of insurance is entered into, every matter known to the insured that the insured knows to be relevant to the insurer's decision whether to accept the risk and, if so, on what terms, or that a reasonable person in the circumstances could be expected to know to be so relevant.
- Section 21(2): the duty does not require disclosure of a matter that diminishes the risk, that is of common knowledge, that the insurer knows or in the ordinary course of its business as an insurer ought to know, or as to which the insurer has waived compliance.
- Section 11(9)(b): subject to subsection (10), a reference in the Act to entering into a contract of insurance includes, for a contract other than life insurance, the parties agreeing to renew, extend or vary it.
- Section 20E: the division containing that duty of disclosure applies to contracts that are not consumer insurance contracts. Section 11AB(1) says a contract is a consumer insurance contract if the insurance is obtained wholly or predominantly for the personal, domestic or household purposes of the insured, and for consumer insurance contracts section 20B(1) sets a different duty: to take reasonable care not to make a misrepresentation to the insurer before the contract is entered into.
- Section 22(1): before a contract of insurance is entered into, the insurer must clearly inform the insured in writing of the general nature and effect of the duty of disclosure, and that the duty applies until the proposed contract is entered into.
Where the text stops and advice begins
That is what the sections say. How they apply to your policy, whether a particular fact is one your insurer needs to hear, and what would follow if an answer turned out to be wrong are questions about your circumstances, and this page does not answer them. Ask your broker, and a lawyer where the answer matters, before anyone signs.
The worksheet has a narrower job: to make sure that whatever you do tell an insurer about your web applications is accurate, dated and backed by a document you can produce, and that anything you are unsure of reaches your broker as a question rather than reaching the form as a guess.
Reading your test report as renewal evidence
A penetration test report is direct evidence about one web application, and it is narrower than it first looks.
It speaks for the application named in its scope, on the hostnames listed, for the roles and accounts used, during the testing dates. It is not evidence about the marketing site on another platform, staff email, laptops, the office network, backups or anything released after testing finished. Read each part for what it lets you say:
- Testing dates: the window the report describes. When a question asks when you were last tested, give these dates, not the date the report was issued or the invoice was paid.
- Report date and version: the document you are citing. Quote the version, so whoever reads your answer later can find the same one.
- Scope and exclusions: the applications, hostnames, roles and environment that were in, and what the report lists as out of scope or not performed. Every exclusion is an edge on any answer you build from the report.
- Who did the work: whether the provider also built or hosts the application. A review by the builder or host is not an independent test, and the report should say which kind of work it describes. A question that asks for an independent tester is answered by that line, not by the findings.
- Findings: what was found on the build tested, at the time it was tested, with a rating for each.
- Checks that found nothing: true for the requests, accounts and build tested, and no wider. They do not show that the application has no other weaknesses.
When the question reaches wider than the report
Questions written in broad terms, such as "all internet-facing applications", "your network" or "critical systems", can reach past any one report. Answer the part the report covers, name the part it does not, and record each uncovered system in Part A as a gap with an owner, rather than letting one report stand for everything.
Line A11 exists for exactly this: the landing page on a website builder, the old campaign subdomain, the booking widget someone else hosts.
The retest ledger: fixed, or only reported as fixed
Questions about findings turn on what happened after the report, which is why the retest ledger sits in Part A beside it.
On this site, a retest records one of four outcomes for each finding: fixed, partially fixed, still reproducible or not retested. A developer's message saying a fix has shipped is not one of the four, however confident it sounds.
Read the ledger line by line before answering anything about remediation. Partially fixed means part of the problem is still there, so while one critical or high finding carries it, a question asking whether all critical and high findings were remediated has no clean Yes.
Not retested means the retest produced no evidence about that finding either way, so it belongs with the open ones rather than the fixed ones. Still reproducible means the original problem was shown to remain, whatever the ticket says.
Note the build and date of the retest too. The ledger describes the build that was retested. If a large release has gone out since, the ledger still shows what was fixed, but it no longer describes the application as it runs today, and an answer about the current state of the application should say which build the evidence covers.
Answering when a control is only partly in place
Controls in a working business can be uneven: multi-factor sign-in on staff email but not on an old shared login, daily database backups but nothing for uploaded files, one application tested and another not.
A Yes or No box hides that unevenness. When the truthful answer is "partly", ticking Yes because most of it is true misstates the gap, and ticking No because some of it is not misstates the control. Write the partial answer out in full first, then ask your broker how the insurer wants it given on the form.
A partial answer that a reader can check names four things:
- Coverage:the systems, accounts or sites the control applies to, by name.
- Exceptions:each system, account or site it does not apply to, by name, with the reason.
- Evidence:the document behind both lists, and its date.
- Change:what will close each exception, who owns it and the month it is due, included only when that change is actually planned.
An invented example: multi-factor sign-in
An illustration, not a real business: "Multi-factor sign-in is enforced for every staff email account, the hosting control panel and the domain registrar, as shown in exports dated 3 November 2026. One shared login to the booking portal's administration area does not use it.
The operations manager is replacing that login with named accounts that do, due in December 2026." Each sentence maps to a line in Part A, and the exception is stated rather than left for someone else to discover.
Check the answer against the form's own definitions
If the form defines a term, such as what counts as a second factor or which systems are critical, your evidence has to meet that definition rather than the everyday meaning of the word. Where you cannot tell whether your setup meets it, write it up as a broker follow-up instead of deciding alone.
The same applies to a line marked not checked: find out before signing, because a guess written as Yes is still a statement your business made.
A renewal run sheet, from notice to inception
The worksheet works best when Part A is current before the form arrives.
This sequence keeps the evidence ahead of the paperwork:
- When the renewal notice arrives, ask your broker for the current form or questionnaire and any changed policy wording, rather than working from last year's copy.
- Copy every question that touches your websites, applications, access, backups or incidents into Part B, with its number and any definitions the document gives.
- Bring Part A up to date, and check each evidence date against the period each question looks back over.
- Mark a status on every line, write each draft answer in full, and give every partly in place or not checked line an owner.
- Send the broker follow-up column to your broker in one message, and keep the reply with the worksheet.
- If a test or retest would change an answer, check whether the test, the fixes and the retest can all finish before the form is signed. A test whose findings are still open when you answer adds open items to your answers rather than removing any.
- After signing, keep the worksheet to hand until cover starts. If a line changes in that time, tell your broker and record the date you did.
After the form is signed
File the completed worksheet with the signed form, the broker's replies and copies of the evidence each answer relied on. At the next renewal, Part A is mostly done already, and you have a record of exactly what was said and on what basis. The same Part A answers the web application questions in a customer's security questionnaire, without starting again.
Where Clever Ops fits, and where it does not
Clever Ops tests what customers reach through a browser or an API: websites, WordPress sites and WooCommerce stores, custom web applications and their APIs, apps made with AI builders, and AI chatbots and agents.
A report from us gives you the Part A evidence for the application tested: the scope as tested and its exclusions, the testing dates, each finding with its ratings, the checks that found nothing with the limits on them, and, after the retest, an outcome for every finding in the ledger vocabulary above.
If Clever Ops built or hosts the application, the work is a security review rather than an independent test, and the report records who built and who hosts it.
Clever Ops does not give insurance advice, tell you what an insurer requires, or fill in your proposal form. Questions about staff email, devices, the office network, phishing training or payment approvals are answered from your IT provider's and finance team's records, and testing internal networks, staff devices or phishing belongs with specialists in those fields.
If your broker or insurer asks for a CREST-accredited tester, Clever Ops is not CREST accredited, so we refer that work to a provider that is.
If the reason you are reading this is an incident in progress, Clever Ops does not provide incident response: read what your policy says about notifying the insurer and choosing a responder before you engage an incident response provider.
When a test is the right next step, bring the exact wording that prompted it to a free scoping call. The written scope and quote that follow name the targets, environment, roles and exclusions, so the report that comes back can be read against the question you actually have to answer.
Frequently asked questions
The questions you answer about your business and its systems when you apply for or renew cyber insurance. The one published form this page reads, Chubb's Short MarketPlace Cyber Proposal Form, is titled a proposal form and includes questions on incident history, multi-factor authentication for remote access, backups, and device and email security. Other forms can ask different things, so read the form you are given for what it asks.
This page cannot tell you, because it depends on your insurer, your policy and the form you are given. Read the questions first. The Chubb Short MarketPlace form we read on 14 November 2026 has no question about penetration testing at all. If your form does ask about testing, the worksheet shows how to answer from a report and retest ledger; if you are unsure what it is asking, ask your broker before booking a test.
This page cannot answer that, and neither can a tester. Those are questions for your broker. What a test does give you is dated evidence about one application, which lets you answer the questions about that application accurately.
Ask your broker first whether the insurer wants it, and in what form. The complete report includes the steps to reproduce each finding, open ones included, so the executive summary, the scope as tested and the retest ledger may be enough to support your answers. Whatever you send, check that its dates and system names match your written answers exactly.
Write the partial answer in full first: what the control covers, what it does not, the evidence and its date, and any change that is actually planned. Then ask your broker how the insurer wants it given, such as a note attached to the form. Do not pick whichever box is closer to true without asking.
Tell your broker, and record when you did. Chubb's Short MarketPlace form, for example, has the signing officers declare that notice will be given as soon as practicable if any of the information changes between the date of the proposal and the proposed date of inception. Read your own form's declaration for what it says.
No. It is a way to organise evidence about your web applications. It does not tell you what your insurer requires, whether you are covered or whether a claim would be paid, and it paraphrases sections of the Insurance Contracts Act 1984 without applying them to your situation. Take those questions to your broker, and to a lawyer where the answer matters.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.