Digital Security Checklist

Compare caller-supplied requirements and observations for digital security checklist.

Description

A digital-security checklist compares intended controls with recorded observations.

A digital-security checklist compares intended controls with recorded observations. It identifies missing labels in a supplied inventory.^[1]

Compare caller-supplied requirements and observations for digital security checklist.

When to use Digital Security Checklist

Use this tool to compare caller-supplied requirements and observations for digital security checklist.

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 Digital Security Checklist 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, enabledControls 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 security controls	list of string	Required
enabledControls	Enabled 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": [
      "2fa",
      "password manager",
      "disk encryption",
      "vpn"
    ],
    "enabledControls": [
      "2fa",
      "password manager",
      "disk encryption"
    ]
  },
  "output": {
    "coveragePercent": 75,
    "matched": [
      "2fa",
      "password manager",
      "disk encryption"
    ],
    "missing": [
      "vpn"
    ],
    "unexpected": []
  }
}

Limitations and assumptions

No device, password, encryption, network or actual control effectiveness is tested.

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 Source Security Coverage: Audit source-security control coverage. For a complementary task, use Email Auth Coverage: Audit email authentication method coverage.

References

Digital Security Checklist — tool.io

Similar or alternative tools

Source Security Coverage
Audit source-security control coverage.
Email Auth Coverage
Audit email authentication method coverage.