Workflow guide
Check access and controls
Test the intended access boundary before broadening use.
Confirm the enabled version and permissions in your environment. These guides do not announce a general release.
Before you start
An authorised target, working connection, a selected policy and permission to start scans. Use a test environment and a bounded budget for the first run.
Steps
- Separate scan execution from policy administration and finding review. A visible menu item does not guarantee that the current user is authorised to operate it.
- Test both an allowed action and an action outside the assigned scope. Review access again when the user, source or policy changes.
- Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.
Check the result
Compare the observed outcome with the expected result. Keep the relevant identifier and a redacted record so a colleague can review the same case.
If it does not work
For a failed scan, inspect target availability, preflight, budgets and worker state. Keep failed or skipped checks distinct from clean findings.