Audit History

Most static alerts are false positives caused by Markdown backticks, PowerShell fences, bind addresses, HTTPS endpoint templates, and benign device redirection. The retry wrappers execute caller-supplied command strings through eval or nested PowerShell, creating command-injection risk, and the PowerShell archive path can include environment secrets. No prompt injection or malicious exfiltration intent was found.

Most static findings are Markdown examples, Azure CLI snippets, placeholders, or benign device references, so they were adjudicated as false positives. I confirmed the retry wrapper command execution paths because they run caller-provided command strings through eval or PowerShell -Command. No prompt injection or data exfiltration intent was found.

Most static findings are benign Azure CLI documentation examples, placeholder URLs, 0.0.0.0 bind addresses, relative documentation links, or .env exclusions. The executable retry wrappers contain a real command-injection risk because they accept full command strings and execute them dynamically. No prompt injection attempt was found in the reviewed files.

Most static findings are false positives from Azure CLI documentation, PowerShell examples, placeholder URLs, and required App Service bind addresses. The review confirms a high-risk command-injection concern in the retry helper scripts because they execute composed command strings that may include user-supplied Azure resource values.