Template library
COPRSETR WORKSHEET

Cloud visibility coverage map, tested detection evidence, current CISA reporting package and signed executive scorecard

CISA SCuBA cloud security implementation · Step 6 · Prove cloud visibility, report status and keep the baseline current
Who prepares it
SOC lead + Cloud service owner + CISA or agency reporting liaison + CISO + Internal audit
When to prepare it
Continuous monitoring and reporting at the cadence required by current federal direction; monthly operational review and quarterly executive review are internal targets

Worked example

This example uses fictional details. Use the same fields with evidence from your work.

Fictional visibility row
Threat: unexpected global admin grant | event: directory role assignment | source: Entra audit | collector: agency SIEM | tenant ID included: yes | delay target: 10 min (internal) | detection: high-risk role outside change window | responder: identity on-call | test date: 19 Nov | result: alert received and triaged
Fictional executive metric
3 of 4 tenant environments have current, interpretable assessments; 82 of 90 applicable policies produced results; 7 mandatory items remain failed; 2 collection errors; 4 approved exceptions expire within 60 days. The scorecard names each owner and includes the evidence date.

Gather first

  • CISA eVRF guide and workbooks
  • M365 or Google audit sources
  • Identity provider
  • Endpoint and secure access telemetry
  • SIEM rules
  • CISA reporting instructions
  • Assessment trend
  • Exceptions and POA&Ms

How to prepare it

  1. For every security question, map the threat or policy to the required event, source product, observation point, collection method, tenant context, expected delay, retention, detection rule, responder and evidence link. Include configuration changes and user activity such as new admin role, suspicious consent, external sharing, mailbox forwarding and audit-policy changes when supported and relevant.
  2. Test each path end to end using an approved benign test: create or change a controlled setting, confirm the audit event carries the right tenant and actor, measure time to SIEM, trigger the expected detection and confirm the on-call team receives and can investigate it. Record unavailable fields, expired retention, unsupported license features and unstaffed alerts as gaps.
  3. For federal reporting, reconcile the current tenant population, applicable policy set, assessment output, exclusions, deviations and remediation status to the latest CISA instructions. Obtain required agency approvals before submission and preserve the submitted file, validation response, receipt and correction history. Build an executive view with data date, denominators, coverage, overdue exposure, repeat findings, exceptions and ownership.

Review

An independent reviewer can trace an executive metric to tenant rows, policy results, raw evidence and a tested telemetry path. Reporting identifies coverage gaps and risk acceptance instead of hiding them inside one percentage.

Handoff

CISO signs the reporting and residual-risk summary. The CIO funds recurring tool operations, log retention and corrective work; internal audit samples the evidence independently.

Use the issuer’s current instructions and any required forms when you submit.

CISA Extensible Visibility Reference Framework guidebook (opens in a new tab)

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes