Social Engineering Coverage Gap

Compare caller-supplied expected and observed records for social engineering coverage gap.

Description

Social-engineering scenario coverage compares a required scenario list with recorded crime-policy scenario labels.

Social-engineering scenario coverage compares a required scenario list with recorded crime-policy scenario labels. Missing labels indicate a supplied inventory gap.^[1]

Compare caller-supplied expected and observed records for social engineering coverage gap.

When to use Social Engineering Coverage Gap

Use this tool to compare caller-supplied expected and observed records for social engineering coverage gap.

Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.

How to use Social Engineering Coverage Gap and understand its results

Prepare the supplied policy terms, dates, assumptions or recorded indicators requested. Keep monetary amounts on one currency basis and select the applicable thresholds separately.
Enter socialEngineeringScenarios, crimePolicyScenarios using the field table and calculation rules, then run the tool.
Read coveragePercent, matched, missing, unexpected. 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
socialEngineeringScenarios	Social-engineering scenarios	list of string	Required
crimePolicyScenarios	Crime-policy scenarios	list of string	Required

Supply social-engineering scenarios first and crime-policy scenarios second. Trim and lowercase labels; reject blanks and require a nonempty first list. Deduplicate by normalized key, retaining first position and last trimmed spelling. Return matches/missing first-list labels, unexpected second-list labels, and percentage; the second list may be empty.

coverage%=100×matchedUnique/requiredUnique

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
coveragePercent	Coverage (%)	number; minimum: 0; maximum: 100
matched	Matched items	list of string
missing	Missing items	list of string
unexpected	Unexpected items	list of string

json

{
  "input": {
    "socialEngineeringScenarios": [
      "fraudulent instruction",
      "vendor impersonation",
      "employee theft"
    ],
    "crimePolicyScenarios": [
      "employee theft",
      "vendor impersonation"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "vendor impersonation",
      "employee theft"
    ],
    "missing": [
      "fraudulent instruction"
    ],
    "unexpected": []
  }
}

Limitations and assumptions

No policy wording, actual fraud, exclusions, sublimits or claim coverage is interpreted.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Transfer-Fraud Screen: Screen payment facts for funds-transfer fraud and response urgency. For a complementary task, use Title Policy Scope Comparison: Compare caller-supplied expected and observed records for title policy scope comparison.

References

Social Engineering Coverage Gap — tool.io

Similar or alternative tools

Transfer-Fraud Screen
Screen payment facts for funds-transfer fraud and response urgency.
Title Policy Scope Comparison
Compare caller-supplied expected and observed records for title policy scope comparison.