chore(ops): record Bot Protection challenge mode in firewall snapshot - #132
Merged
Merged
Conversation
Bot Protection flipped from log to challenge in the Vercel dashboard (2026-08-23T17:40:59Z), the last remaining lever from the traffic/cost hardening effort. All known blind spots (repo-info self-call, admin crons, badge-update prefix collision) were closed and verified before this change. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WfPnHMv3W4afwHCAnkBHnN
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
logàchallengedans le dashboard Vercel (2026-08-23T17:40:59Z), dernier levier de l'effort de durcissement trafic/coûtdocs/firewall-config.jsonresynchronisé avec l'état live de productionContexte
Tous les blind spots identifiés ont été fermés et vérifiés actifs avant ce changement : bypass du self-call
repo-info, bypass des crons admin, et la collision de préfixe/api/badgevs/api/badge-update.Seuil de rollback : repasser en
logsi challenge dépasse 500/j ET taux de résolution < 10%, mesuré viavercel metrics vercel.firewall_action.count -f "waf_rule_id eq 'managed_bot_protection'".Test plan
vercel firewall overview --jsonconfirmebot_protection.action = "challenge"en proddocs/firewall-config.jsondiff limité aux 2 lignes attendues (action + updatedAt)🤖 Generated with Claude Code
https://claude.ai/code/session_01WfPnHMv3W4afwHCAnkBHnN