TRUST ATLAS WORKSHEET
SSP
NIST Risk Management Framework · Step 2 · Select, tailor and implement controls- Who prepares it
- Security architect + common control providers
- When to prepare it
- Before assessment
Worked example
This example uses fictional details. Use the same fields with evidence from your work.
- Service and objective
- Hosted invoice service receives orders, calculates amounts and sends PDF receipts.
- Boundary and inputs
- Accepted production order events, account identifiers and billing records
- How it works
- Payment result updates invoice status. Release pipeline deploys code with approval.
- Shared roles
- Customer controls user configuration. Hosting vendor manages physical infrastructure.
- Evidence and review
- Architecture v3, deployment records and service-owner review
Gather first
- Approved system boundary
- Architecture, data flows, controls and service commitments
- Current reporting instructions or system plan template
How to prepare it
- Explain who uses the system, the commitments it supports and how people, processes, software, infrastructure and data fit together.
- Walk through actual transactions or requests and identify the relevant controls and shared responsibilities. Cover dependencies and any criteria or requirements in the agreed template.
- Validate each section with the technical owner against live architecture, procedures and evidence. Lock the approved version and reconcile it to diagrams and control records.
Review
The written description, diagrams and control records agree. A reviewer can understand end-to-end operation.
Handoff
Send the approved draft to management and the independent evaluator. Transfer it to the prescribed system plan or report template when needed.