domains / families / security / cross-attack-chains

cross-attack-chains

separate

Use when two or more verified findings may combine into a higher-impact authorized attack path.

When to use

• Two or more validated findings affect the same trust boundary.
• One finding exposes an identity, token, route, host, or capability needed by
• A report needs to distinguish standalone impact from compound impact.
• The next chain step cannot be tested safely and must be labeled inferred.

When not to use

• using real user data
• broad credential testing
• destructive operations
• discarding scanner labels without verification

Skill page

Source