COPRSETR WORKSHEET
Approved assessment runbook, permission approval and reproducible run manifest with protected raw outputs
CISA SCuBA cloud security implementation · Step 3 · Approve and run a safe, repeatable baseline assessment- Who prepares it
- Tenant administrator + Cloud security engineer + Change manager + Security operations
- When to prepare it
- After admin consent and data handling review; repeat on the agreed monitoring cycle
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Fictional run manifest
- Run 2026-11-19-014 | tenant 8f21…c402 | cloud GCC | ScubaGear version recorded from Invoke-SCuBA -Version | ConfigFilePath hash 71ab…91d0 | operator sec-assess-02 | selected products: Exchange, Entra, SharePoint | result: 3 products complete, 1 collection error | reports: restricted/SCuBA/2026-11-19/ | raw files: 6, hashes recorded
- Safety gate
- The security architect confirms permissions, approved sign-in method, tenant domain, output storage and incident contact. A version update is reviewed in a test run before it replaces the pinned production runner.
Gather first
- Tenant register
- Tool release and prerequisites
- Current API permissions
- Admin consent
- Baseline and YAML configuration
- Approved runner
- Security logging and storage rules
How to prepare it
- Document supported host, network egress, tool install source, pinned version, dependencies, admin role, app permissions, service account or interactive identity, tenant ID and selected environment. Obtain written approval for permissions and sign-in method before use.
- For Microsoft, record the ConfigFilePath, Organization, product selection, cloud environment and approved operator identity. Use the current ScubaGear documentation for any BOD-required configuration. For Google, follow ScubaGoggles prerequisites, APIs, authentication and configuration guidance rather than copying M365 steps.
- Capture run ID, start and end time, exact command or config hash, tool and baseline version, tenant context, per-product success or error, counts of automated/manual/applicable policies, file names and cryptographic hashes. Store HTML, JSON, CSV and logs under the approved tenant evidence permissions and retention rule.
Review
A second operator can reproduce the assessment, prove which tenant and versions were evaluated, and locate outputs without searching broad collaboration channels.
Handoff
Provide a sanitized summary to the remediation owners. Restrict raw tenant configuration and identity data to approved reviewers.
Use the issuer’s current instructions and any required forms when you submit.
CISA ScubaGear documentation and prerequisites (opens in a new tab)