StackHawk
Day 38 after signup
Product Updates: More complete coverage, less set up.
Scans that reach more of your app, with less work to set up. Plus upgrade tips.
Why it works
- Group related product changes under clear headings so readers can scan the update by topic.
- Separate upgrade-impacting changes from feature improvements, and explain what readers may need to review or adjust.
How it is built
- Brief update intro
- Coverage improvements
- Setup improvements
- Upgrade considerations
- Additional changes
Email copy
View in browser Hi there, Your coding agent acts on what the scanner reports. So our latest feature releases focus on two areas: more complete coverage, and less setup to get it. Here is the short version. Read the full update on the blog → More Complete Coverage A scan can only find what it reaches. It now reaches more. › APIs behind a base path get tested. HawkScan reads the prefix from your OpenAPI spec and tests every route at its real URL. › Single-page apps get crawled from the pages you choose. The browser-based spider starts from your seed paths and reaches the deep views. › New guide: scanning services behind mutual TLS. Step-by-step setup for apps that require a client certificate, so internal services can be in scope. Less Setup Getting to a thorough scan takes less work. › Your agent sets up authorization testing. It reads your code, finds or creates test accounts, and runs your full policy and the authorization checks in one scan. › Findings land in GitHub code scanning. One alert per finding, next to your SAST and dependency alerts, in the tab your developers already check. › Wingman runs in Codex and GitHub Copilot. The full skill set, alongside Claude Code and Cursor. See every change and how to turn it on → Before You Upgrade These changes alter behavior or need something from you. Check them before you run hawk upgrade. › Your finding counts will move. Four single-identity authorization rules are retired in favor of multi-profile testing. Check dashboards and build thresholds. › Missing variables stop the scan. A ${VARIABLE} with no value now fails with a clear error. Use ${VARIABLE:} when you mean an empty value. › codeScanningAlerts is deprecated in the GitHub Action. Use --sarif-ghas with GitHub's upload-sarif action. › Bulk triage files are checked more strictly. Re-run any hawk op scan triage --from-file files you use and fix rejected entries. › API clients should handle 409. Conflicts now return 409 with the reason. They used to return 412. › Re-run Team assignments made by API before mid-August. The endpoint reported success without saving. It now saves. › OpenAPI base paths are now applied. If the path in your spec's servers[] entry is wrong for the environment you scan, set app.openApiConf.basePath. There Is More in the Full Post SSRF alerts confirmed before they fire. Organization-shared secrets. A one-line installer for every OS. Team ownership for every new app. Read-only access for auditors. And the full list of fixes. Read the full update → We want to hear from you Have product feedback or feature requests? Email us at product@stackhawk.com. StackHawk, 1580 N. Logan St, Ste 660 PMB 36969, Denver, Colorado 80203, United States, (720) 336-8596 Manage preferences