Bring your requirements.
Define the scope of your review, the standards you work to, and the evidence your team needs to make a decision.
Discuss your requirementsReview workflow example
Make a policy easier to inspect.
Adjust a tiny sample policy, then inspect the lines that need attention. Passing this demonstration is not compliance certification.
Policy source scanner
1
{2
"project": "*",!3
"reviewOwner": "example-team"✓4
}Scope Limit the review to the intended resource.
Ownership Make follow-up responsibility explicit.
Requirements you may bring
Give the review a clear scope.
These are discussion topics, not statements of certification. Ask the team about the availability, scope, and applicability of supporting materials.
Assurance reviewSOC 2Share the report, review period, and service scope your procurement process requires.
Management systemISO 27001Discuss the certificate scope and supporting materials your organization needs to assess.
Data protectionGDPRBring your data processing requirements and review the relevant contractual terms with the team.
Healthcare requirementsHIPAADiscuss your intended workload, information handling, and contractual requirements before deployment.
Payment requirementsPCI DSSDefine the payment data involved, your intended architecture, and the evidence your review requires.
Privacy requirementsCCPAShare your privacy and data handling requirements to identify the materials needed for your review.
From requirements to a decision
Make the next step specific.
01 / ScopeDescribe the workload, the information it handles, and the environments involved.
02 / NeedsIdentify the controls, standards, and contractual terms your team must evaluate.
03 / EvidenceRequest the relevant materials and confirm their scope and current applicability.
04 / ReviewDocument remaining questions and the decisions needed before deployment.
Put your review in motion.
Bring your requirements to the team and discuss the materials you need.