Platform · Cyber insurance

Cyber Insurance Data

Two cyber policies can list the same covers and differ entirely in which war and state-backed attack clause they carry.

Cyber insurance data covers published cyber policies: first-party and third-party coverage sections, sub-limits, waiting periods and exclusions. Since 31 March 2023, Lloyd's has required standalone cyber policies to exclude catastrophic state-backed cyber attacks, with market model clauses available. So the exclusion clause referenced is recorded exactly, by its reference and text, and never paraphrased. No quote is ever requested with an invented business; individual premiums are not collected.

In cyber, the exclusions have moved faster than the covers. They are where comparisons have to start.

Get a free sample See sample data

Free pilot on your own Cyber insurance list, returned in 24 hours. No card, no trial clock — and you keep the sample data either way.

cyber_sample.jsonl LIVE FEED

{"exclusion_clause_reference":"as cited in wording","exclusion_text":"verbatim","paraphrased":false} {"coverage_section":"business interruption","sub_limit":250000,"waiting_period":"8 hours"} {"market":"as stated"}

illustrative sample rows · globalthe exclusions come first · schema v1.0

Independence and trademarks. Actowiz Solutions is not affiliated with, endorsed by or connected to Cyber insurance or its owners. Cyber insurance and related marks belong to their respective owners, used here only to name the publicly accessible source this service collects from.

Our Data Powers

B2C Marketplace

amazon

D2C + Marketplace

NYKAA

D2C + Marketplace

Walmart

FMCG Marketplace

udaan

Food Delivery

Uber Eats

Quick Commerce

blinkit

Taxi Aggregator

Uber

E-Commerce

Tmall

Cyber insurance at a glance

How we handle Cyber insurance specifically

Platform-specific handling, not a generic retail template pointed at a different domain.

Scope: Standalone cyber and cyber sections
Coverage: First-party and third-party sections, as named
State-backed exclusion: Required at Lloyd's from 31 Mar 2023
So: clause_reference and text recorded exactly
Sub-limits: By section, as stated
Waiting periods: Business interruption, as stated
Source: Wordings and product documents
Quotes: Never requested with invented businesses

Platform specifics

The exclusions come first

These are the reasons a Cyber insurance dataset needs its own handling rather than a shared retail schema.

Clause references as data

Following a Lloyd's market bulletin in 2022, standalone cyber policies written at Lloyd's from 31 March 2023 must exclude losses from state-backed cyber attacks, and the market published model clauses. Outside Lloyd's, insurers use their own or similar wordings.

exclusion_clause_reference recorded exactly as the wording cites it.
exclusion_text captured verbatim with page reference.
A paraphrase is never stored in place of the text. Clause variants differ in ways that matter.
Other key exclusions — infrastructure, prior acts, betterment — recorded as worded.

Coverage sections, and what we do not do

Coverage sections

Incident response, business interruption, data restoration, extortion, liability and regulatory sections, each with sub-limits and waiting periods as stated. Section names are kept as each insurer uses them.

Liability overlap

Cyber liability sits beside other liability covers, where the limit basis matters just as much — see our liability page.

What we do not do

Paraphrase exclusions, judge whether an attack would be excluded, request quotes with invented businesses, or collect policyholder or incident data.

Scope

What we collect on Cyber insurance, and what we do not

The right column matters more than the left. Anyone can list fields; the limits are what tell you whether the dataset will hold up.

✅ What we collect

exclusion_clause_reference exactly as cited
Exclusion text verbatim with page reference
Coverage sections as each insurer names them
Sub-limits by section
Waiting periods as stated
Other key exclusions as worded
Lloyd's or non-Lloyd's recorded where stated
Document versions tracked
No invented quote requests, ever

❌ What we do not, and why

Exclusions paraphrased in place of the text
Judgements on whether an attack is excluded
Quotes requested with invented businesses
Section names mapped silently
Policyholder or incident data

Core Cyber insurance fields

The full dictionary is agreed during scoping. These are the fields specific to this platform.

Field	What it is on this platform
insurer / product	As published
market	Lloyd's or company market, where stated
coverage_section / sub_limit	As stated
waiting_period	As stated
exclusion_clause_reference	As cited
exclusion_text	Verbatim
other_exclusions	As worded
aggregate_limit	As stated
doc_version / effective_from	Document
source_ref	Document and page
observed_at	Timestamp

Use cases

What teams do with Cyber insurance data

Exclusion benchmarking

Which state-backed attack clauses each insurer uses.

Coverage comparison

Sections and sub-limits across the market.

Wording change tracking

When exclusions or sections change.

Broker research

Published product terms before placement.

The 24-hour sample — run on your sources, not ours

Send us a Cyber insurance item or category list. We run real collection against it and return the output within 24 hours, with the platform-specific fields populated so you can check them yourself rather than take our word for it.

Real extraction from your actual sources
Returned within 24 hours
Coverage and QA note included
You keep the data either way
No card, no trial clock
Named engineer on the call

Get my free sample Book a 20-min scoping call Reply within one business day. Reference calls available under NDA.

How we engage

Three ways to engage us

Same collection pipeline and QA underneath. The difference is who holds the schedule and how the data reaches you.

Managed service (most common)

We own the collection, the QA and the delivery. You receive clean data on a schedule and never touch a scraper.

Dedicated engineer assigned to your account
Site changes fixed by us, not reported to you
Scheduled delivery to your warehouse or S3
Named contact on Slack or email

Best fit: Teams who need the data, not the infrastructure.

API access

The same collection pipeline exposed as an authenticated REST endpoint your systems query directly.

On-demand and scheduled endpoints
Rate limits agreed to your load profile
Sandbox keys for integration testing
Versioned schema with deprecation notice

Best fit: Product and engineering teams building on live data.

One-time or project extraction

A defined pull for a specific question — market sizing, diligence, a pitch, a one-off audit.

Fixed scope agreed in writing upfront
Single delivery with full QA report
Methodology documented for your records
Converts to managed if you want continuity

Best fit: Research, strategy and diligence work with a deadline.

Pricing

Every engagement is quoted individually, because the honest answer depends on your scope: how many sources, how many records, how often, and how the data reaches you. We scope it with you, run a free pilot on your own sources, and then quote a fixed monthly figure — no per-request metering and no overage billing when volumes move. Request a quote and you will have a number after one call.

Cyber insurance is usually collected alongside its competitors

Almost nobody buys a single platform in isolation. Cyber insurance data becomes useful when it sits next to the competitor set on one schema, refreshed on one schedule, so a price index or availability comparison is genuinely like-for-like.

That is what insurance data covers, and a Cyber insurance-only engagement can be expanded into it without rebuilding. If you already know you need several platforms, start there instead — it is the same pipeline and usually the better scoping conversation.

FAQ

Cyber insurance data scraping: frequently asked questions

Platform-specific questions, including what cannot be collected here.

Because clause variants differ in ways that decide claims. A paraphrase would lose that.

Lloyd's required standalone cyber policies to exclude catastrophic state-backed attacks from 31 March 2023.

No. We record the wording, not coverage opinions.

Section names are kept as each insurer uses them; mappings are labelled if requested.

No. We never invent businesses.

It depends on insurers and documents.

Talk to us.

See real Cyber insurance data before you commit to anything

Send us an item or category list. We return the output within 24 hours with the platform-specific fields populated.

Get a free sample Talk to an engineer

Free pilot, no card, no obligation. If we cannot collect a field you need on this platform, the sample shows you that too.

Hear It Directly from Our Clients

Watch how businesses like yours are using Actowiz data to drive growth.

▶

1 min

★★★★★

"Actowiz Solutions offered exceptional support with transparency and guidance throughout. Anna and Saga made the process easy for a non-technical user like me. Great service, fair pricing!"

Thomas Galido

Co-Founder / Head of Product at Upright Data Inc.

▶

2 min

★★★★★

"Actowiz delivered impeccable results for our company. Their team ensured data accuracy and on-time delivery. The competitive intelligence completely transformed our pricing strategy."

Iulen Ibanez

CEO / Datacy.es

▶

1:30

★★★★★

"What impressed me most was the speed — we went from requirement to production data in under 48 hours. The API integration was seamless and the support team is always responsive."

Febbin Chacko

-Fin, Small Business Owner