--- name: public-input-threat-assessment description: Threat assessment template for public user-authored GitHub content that may contain classic manipulation or agentic attacks. --- # Public Input Threat Assessment Source: `` Reference: `` Assessor: `` Date: `` ## Public Content Reviewed | Content | User-Controlled Surface | Notes | | --- | --- | --- | | `` | `` | `` | ## Classic Manipulation / Turing Attack Checks | Check | Present | Evidence | | --- | --- | --- | | Urgency pressure or threat | `` | `` | | Flattery, social proof, or authority claim | `` | `` | | Request to skip tests, review, policy, or evidence | `` | `` | | Unsupported security or correctness claim | `` | `` | | Attempt to manipulate maintainer decision or priority | `` | `` | ## Agentic Attack Checks | Check | Present | Evidence | | --- | --- | --- | | Prompt injection or hidden instruction | `` | `` | | Tool-use steering or command execution request | `` | `` | | Credential, token, environment, or secret exfiltration attempt | `` | `` | | Poisoned logs, tests, screenshots, filenames, or model output | `` | `` | | Objective redirection or instruction hierarchy override | `` | `` | | Suspicious external link or attachment | `` | `` | ## Security Framework Routing Required: `` Route used: - `aiwg discover ""` - Selected artifact: `` Use security-engineering routing for auth, secrets, supply chain, CI, command execution, local model behavior, disclosure handling, or repository trust decisions. ## Decision Risk: `` Allowed next action: - `` Required mitigations: - ``