Run and interpret an assessment

Describe the approved target and question clearly. Example: “Review the authorised staging application for exposed services and common web weaknesses.” Avoid asking to test everything without defined scope.

Profiles and depth influence check selection. Plan, runtime and deployment availability affect execution; selecting a profile does not prove every associated tool ran.

The scan route combines planning and execution. Review scan detail, task logs and events. Include skipped checks, interruptions and errors in the interpretation.

A failed or stopped run may contain valid findings but has incomplete coverage. Record that limitation. HTTP success alone is not proof of completed testing.

Check the affected endpoint, identity, conditions and observed result. Severity helps prioritise; exposure and business context determine the next action.

After remediation, repeat the relevant check under comparable conditions. Preserve the original observation and retest. A generated report does not demonstrate that a weakness was repaired.