liveBook · Manning

Data encryption coverage

As explained in Data-Driven Cybersecurity

The ratio of systems protected by encryption to systems that are not protected by encryption.

Data encryption coverage compares systems protected by encryption with systems that remain unprotected. It turns encryption status into a percentage-based view of data protection and highlights machines outside the organization’s goal. section 6.4.1 section 7.3.5

Use the metric to connect technical configuration with risk and action:

  • Set encryption as mandatory and enabled by default, with users unable to disable or remove it; strive for 100% compliance. section 6.4.1
  • Track the measure to identify machines that fall outside the encryption goal and prioritize remediation. section 6.4.1
  • Treat gaps as data-protection risk because lost or stolen laptops can expose sensitive information stored on their drives. section 6.4.1

Interpreting a coverage gap

A dashboard showing any nonencrypted systems indicates that the organization has not reached its encryption goal. Report the gap, locate the affected machines, and restore mandatory encryption before sensitive data is exposed through loss or theft. section 6.4.1

How Data-Driven Cybersecurity covers it

How deep it goes
Defines a derived ratio and target, but stops short of specifying a collection method or calculation procedure.
Examples
Uses mandatory default encryption, out-of-goal machines, and stolen or misplaced laptops containing sensitive data.
What it assumes
Assumes system baselining and an inventory of encrypted and nonencrypted systems.
What you can do after
Evaluate/understand encryption gaps, identify affected machines, and report progress toward complete coverage.
How it connects
Connects system baselining, compliance metrics, data protection, and security baselines.

This explainer was generated by Manning's knowledge graph from the text of Data-Driven Cybersecurity. The section links point to the parts of the book it draws on.