Definitions
Terms used in this paper
These definitions establish how the paper uses its core terms before the argument begins.
- Evidence quality
- The combination of freshness, completeness, provenance, conflict state, and scope that determines how strongly an observation supports a conclusion.
- Evidence provenance
- The traceable origin of a control observation.
- Evidence completeness
- Whether the sources required for the underwriting conclusion are present.
- Evidence conflict
- A disagreement among credible sources that should remain visible until resolved or governed by a documented precedence rule.
1. Cyber underwriting has an information-quality problem
Underwriters routinely receive questionnaires, broker narratives, scans, security reports, attestations, and third-party scores. The challenge is not lack of information. It is determining which facts describe the insured now, how directly those facts were observed, and where the evidence is incomplete or contradictory.
A control statement such as 'MFA is enabled' can conceal material variation in scope, exception paths, privileged accounts, and observation age. Evidence quality gives the underwriter a way to evaluate the reliability of the control claim without pretending that every source deserves equal weight.
2. Four evidence properties matter before the score
Freshness asks when the relevant state was observed. Completeness asks whether the sources needed for the conclusion are present. Provenance identifies where the observation came from. Conflict asks whether credible sources disagree. These properties can be represented independently from the control's apparent state.
This distinction is especially important when data is automated. A high-volume telemetry feed can create a false sense of certainty if the most important identity source is missing or if the data is several weeks old. Automation should make information quality more visible, not less.
Read the apparent condition alongside four independent evidence questions.
Check
FreshnessWhen was the condition observed?
Check
CompletenessAre the required sources and scope present?
Check
ProvenanceWhere did the observation come from?
Check
ConflictDo credible sources disagree?
These properties establish the strength of evidence available for underwriting review and pricing decisions.
3. Control evidence should remain interpretable
An underwriter does not need a raw stream of endpoint or identity telemetry. The evidence should be summarized into facts the underwriter can use while keeping the source, scope, observation time, and important exclusions available for review.
That structure allows carriers to apply their own underwriting rules. One carrier may treat a particular exception as material while another does not. The evidence should preserve the facts without embedding one carrier's underwriting philosophy into the insured's security history.
4. Evidence quality can improve model calibration
If carriers later test operational signals against claims outcomes, missingness and evidence quality should be part of the dataset. Otherwise a weak observation may be treated as if it were a strong measurement, contaminating the apparent relationship between control state and loss.
Prospective calibration can examine not only whether a control variable separated loss cohorts, but whether the confidence of the evidence changed the signal. A model may discover that stale evidence is itself informative, or it may find no meaningful relationship. The point is to measure rather than assume.
5. Better evidence does not remove underwriting judgment
Cyber underwriting includes policy structure, limits, attachment, industry, revenue, dependencies, historical loss, legal environment, and many other variables. Evidence quality improves the cybersecurity portion of the decision; it does not replace the rest of underwriting.
The practical benefit is narrower and valuable: the carrier can spend less time debating whether a control claim is current and more time deciding what the observed state means for the risk being priced.
Evidence base
Sources and notes
External foundations are kept distinct from VitalSec implementation notes so readers can see what supports the argument independently and what documents the platform implementation.
External foundations and sources
VitalSec implementation notes
These links document how the argument is implemented or described inside VitalSec. They are not offered as independent validation of the paper's thesis.
