Cloud Responsibility Coverage

Audit cloud shared-responsibility assignments.

Description

Cloud shared responsibility assigns distinct duties to providers and customers.

Cloud shared responsibility assigns distinct duties to providers and customers. A supplied checklist can show unmapped responsibilities.^[1]

Audit cloud shared-responsibility assignments.

When to use Cloud Responsibility Coverage

Use this tool to audit cloud shared-responsibility assignments.

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.

How to use Cloud Responsibility Coverage and understand its results

Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
Enter requiredResponsibilities, assignedResponsibilities 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
requiredResponsibilities	Required cloud responsibilities	list of string	Required
assignedResponsibilities	Assigned responsibilities	list of string	Required

Enter requiredResponsibilities as the nonempty expected list and assignedResponsibilities as observations, which may be empty. Trim entries, compare case-insensitively using en-US lowercase and collapse duplicates. Return matched/missing expected labels and unexpected observed labels. Output follows first occurrence order with the last duplicate’s trimmed spelling.

coverage%=100matchedUnique/expectedUnique

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": {
    "requiredResponsibilities": [
      "alpha",
      "beta",
      "gamma",
      "delta"
    ],
    "assignedResponsibilities": [
      "beta",
      "alpha",
      "extra"
    ]
  },
  "output": {
    "coveragePercent": 50,
    "matched": [
      "alpha",
      "beta"
    ],
    "missing": [
      "gamma",
      "delta"
    ],
    "unexpected": [
      "extra"
    ]
  }
}

Limitations and assumptions

No provider contract, control operation or security posture is verified. Blank entries are errors; requirements are entirely caller-supplied and items have equal weight.

Numeric inputs, where present, 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 Failover Evidence Coverage: Audit disaster-recovery failover evidence. For a complementary task, use PAM Evidence Coverage: Audit privileged-access-management evidence.

References

Cloud Responsibility Coverage — tool.io

Similar or alternative tools

Failover Evidence Coverage
Audit disaster-recovery failover evidence.
PAM Evidence Coverage
Audit privileged-access-management evidence.