Start with a decision, not a feature list
A useful evaluation answers a small number of important questions. Choose the security decision Nova should improve, the evidence needed to assess that decision, and the people who will judge the result.
- Which current workflow is slow, fragmented, or difficult to defend?
- Which environment and business scope are safe and representative for the evaluation?
- What evidence must be present before the result can be trusted?
- Who can approve access, validate findings, and decide whether the outcome is useful?
Choose what to evaluate
Select representative accounts, subscriptions, projects, clusters, or security systems without beginning with the entire estate. Record exclusions, expected blind spots, retention needs, and any restrictions on action.
Use read-only access wherever it is enough for the evaluation. Assess response actions separately, with approval from the people responsible for the affected systems.
Agree how the result will be measured
- Coverage: which intended sources and scopes produced current evidence.
- Traceability: whether a reviewer can follow a conclusion back to supporting evidence.
- Workflow: whether ownership, investigation, and the next step remain connected.
- Control: whether access and any supported actions match approved boundaries.
- Adoption: whether the intended users can understand and use the result in their normal work.