1. Workflows
Ask. Which workflows are included in the deployment?
Why. A defined workflow sets an actionable scope.
Weak answer. A broad assurance without a named configuration or accountable owner.
2. Detectors
Ask. Which supported sensitive-data classes are enabled?
Why. Detector configuration should reflect the data handled.
Weak answer. A broad assurance without a named configuration or accountable owner.
3. Destinations
Ask. Which destinations and groups receive each policy?
Why. Rules need explicit subject and destination context.
Weak answer. A broad assurance without a named configuration or accountable owner.
4. Actions
Ask. What action is expected for each representative input?
Why. Expected outcomes help validate the configuration.
Weak answer. A broad assurance without a named configuration or accountable owner.
5. Exceptions
Ask. Who approves exceptions and their effective windows?
Why. Time and scope keep an exception accountable.
Weak answer. A broad assurance without a named configuration or accountable owner.
6. Evidence
Ask. What content is captured and who can request access?
Why. Evidence capture and reveal are separate decisions.
Weak answer. A broad assurance without a named configuration or accountable owner.
7. Integrity
Ask. How are event chains and checkpoints reviewed?
Why. Integrity review needs owners and preserved references.
Weak answer. A broad assurance without a named configuration or accountable owner.
8. Handover
Ask. Which operating records and escalation paths are delivered?
Why. The operating team needs a maintained configuration record.
Weak answer. A broad assurance without a named configuration or accountable owner.
How to read this
| Review | Product context | Operating decision |
|---|---|---|
| Policy | Customer-defined rules and actions | Assign policy ownership |
| Records | Decisions with policy references | Define review access |
| Deployment | Supported clients and data paths | Validate configuration |