Source Security Coverage

Audit source-security control coverage.

Description

Source-security plans list controls intended to protect a reporting relationship.

Source-security plans list controls intended to protect a reporting relationship. Comparing planned and observed labels makes absent records visible.^[1]

Audit source-security control coverage.

When to use Source Security Coverage

Use this tool to audit source-security control coverage.

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.

How to use Source Security Coverage and understand its results

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
Enter requiredControls, implementedControls 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
requiredControls	Required source-security controls	list of string	Required
implementedControls	Implemented controls	list of string	Required

Supply required and observed control labels. Enter a nonempty required list and an observed list, which may be empty. Trim and lowercase entries for comparison; blank entries are errors. Deduplicate by normalized key. Return matched/missing required labels, unexpected observed labels, and coverage. Required order is preserved; the last trimmed spelling wins for duplicate keys.

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": {
    "requiredControls": [
      "alpha",
      "beta",
      "gamma"
    ],
    "implementedControls": [
      "beta",
      "alpha",
      "extra"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "alpha",
      "beta"
    ],
    "missing": [
      "gamma"
    ],
    "unexpected": [
      "extra"
    ]
  }
}

Limitations and assumptions

No threat model, control effectiveness, device state or source safety is verified.

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 Digital Security Checklist: Compare caller-supplied requirements and observations for digital security checklist. For a complementary task, use Travel Device Checklist: Compare required travel-device safeguards with enabled safeguards.

References

Source Security Coverage — tool.io

Similar or alternative tools

Digital Security Checklist
Compare caller-supplied requirements and observations for digital security checklist.
Travel Device Checklist
Compare required travel-device safeguards with enabled safeguards.