Cyber First vs Third Party Cover Lookup
Allocate actual cyber cost categories using independent caller first/third-party maps, overlap explicitly reported and totals not summed blindly; no cyber policy coverage or incident causation conclusion.
Description
Cyber cost categories can belong to first-party, third-party, both or neither supplied maps.
Cyber cost categories can belong to first-party, third-party, both or neither supplied maps. Overlap must be visible before totals are combined.1
The returned values include Caller first party categorized cost minor, Caller third party categorized cost minor, Caller both party category ids, Caller unclassified category ids. The How section below explains the calculation, input rules and interpretation.
When to use Cyber First vs Third Party Cover Lookup
Use Cyber First vs Third Party Cover Lookup when you need to evaluate the supplied records under the calculation and evidence rules below. No policy coverage, cause attribution or disjoint-total assumption is supplied.
Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
How to use Cyber First vs Third Party Cover Lookup and understand its results
- Prepare the observed policy, claim or quote evidence and independently verified policy tables. Monetary fields use integer minor units in one currency: for a currency with 100 minor units per major unit, enter 12345 for 123.45. One basis point is 0.01 percentage points, so 10000 basis points represents 100%.
- Enter callerCyberCostCategoryIds, callerVerifiedFirstPartyFlags, callerVerifiedThirdPartyFlags, observedCyberCostCategoryIds, observedCyberCostMinor using the field table and calculation rules, then run the tool.
- Read callerFirstPartyCategorizedCostMinor, callerThirdPartyCategorizedCostMinor, callerBothPartyCategoryIds, callerUnclassifiedCategoryIds. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| callerCyberCostCategoryIds | Caller cyber cost category ids | list of string | Required |
| callerVerifiedFirstPartyFlags | Caller verified first party flags | list of number | Required |
| callerVerifiedThirdPartyFlags | Caller verified third party flags | list of number | Required |
| observedCyberCostCategoryIds | Observed cyber cost category ids | list of string | Required |
| observedCyberCostMinor | Observed cyber cost minor | list of number | Required |
Enter aligned nonempty unique nonblank catalog IDs and binary party flags, plus aligned nonempty observed IDs and integer costs 0–10¹². Exact-match every observation. Return party totals, observed IDs in both categories and unclassified IDs. Costs in both maps enter both totals.
first=sum(cost where firstFlag1); third=sum(cost where thirdFlag1) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| callerFirstPartyCategorizedCostMinor | Caller first party categorized cost minor | number |
| callerThirdPartyCategorizedCostMinor | Caller third party categorized cost minor | number |
| callerBothPartyCategoryIds | Caller both party category ids | list of string |
| callerUnclassifiedCategoryIds | Caller unclassified category ids | list of string |
{
"input": {
"callerCyberCostCategoryIds": [
"response",
"liability"
],
"callerVerifiedFirstPartyFlags": [
1,
0
],
"callerVerifiedThirdPartyFlags": [
0,
1
],
"observedCyberCostCategoryIds": [
"response",
"liability"
],
"observedCyberCostMinor": [
1000,
2000
]
},
"output": {
"callerFirstPartyCategorizedCostMinor": 1000,
"callerThirdPartyCategorizedCostMinor": 2000,
"callerBothPartyCategoryIds": [],
"callerUnclassifiedCategoryIds": []
}
}Limitations and assumptions
No policy coverage, cause attribution or disjoint-total assumption is supplied.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Numeric lists are limited to 10,000 entries; string lists to 128 strings of at most 128 characters each. The rules above may impose smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Ransomware Extortion Sublimit Checker: A ransomware sublimit budget separates modeled covered amount from compliance-review evidence. The review flag does not gate the arithmetic. For a complementary task, use BOP Package Included Perils Lookup: BOP peril checks require an independently verified included-peril map. Unknown cause evidence must remain unresolved.
References
-
Cyber First vs Third Party Cover Lookup — tool.io
Similar or alternative tools
- Ransomware Extortion Sublimit Checker
A ransomware sublimit budget separates modeled covered amount from compliance-review evidence. The review flag does not gate the arithmetic.
- BOP Package Included Perils Lookup
BOP peril checks require an independently verified included-peril map. Unknown cause evidence must remain unresolved.