ATTACK PROFILES

Tuning Attack Profiles

Choose the run profile and depth according to the target, its environment, and the question the team needs to answer.

scenario.yaml

# Example for an authorized staging target
  target_scope:
    assets: ["https://your-verified-target.example"]
    environments: ["staging"]
  scan_profile: quick
  attack_depth: low
  compliance_tags: ["owasp"]
 
✓ Save the scenario, run it from /runs/new, and inspect the evidence before reuse

Illustrative run configuration — adapt it in /settings/scenarios

Attack Profile Basics

The profile sets the breadth of the run; depth limits how strongly it may exercise the target.

›Use `quick` for an initial check; select `standard` or `deep` only when the question requires broader scenarios.
›Keep depth low in production and increase it only in an authorized environment that can tolerate the traffic.
›Use compliance tags to organize review; they do not turn a run into an audit or certification.
›Record each target's environment so a staging configuration is not applied to production.

Advanced Calibration

Adjust the configuration only after identifying what the initial run did not answer.

›Reserve the `deep` profile for staging or controlled environments.
›Repeat the same scenario set before and after changing a detection rule.
›Respect the API limits and the authorization granted for the target.
›Use `Idempotency-Key` when retrying after a network failure to avoid duplicate runs.

Best Practices

List allowed targets explicitly; wildcards are rejected.
Choose tags that match the current question instead of rotating them only to increase a count.
Compare equivalent runs after each change and read findings together with scores.

Loading…...