使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/vaquarkhan/fullstack-development-agent-skills --skill api-gateway-and-edge-security开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
仓库原始内容
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
API Gateway And Edge Security
Use When
- Exposing APIs to public clients or partners
- Centralized edge policy is required for governance
Workflow
- Define route-level authn and authz requirements.
- Configure request validation and schema enforcement at edge.
- Apply IP, token, and tenant-aware rate limiting.
- Add WAF, bot mitigation, and abuse detection rules.
- Emit security audit logs and anomaly alerts.
Required Checks
- Unauthorized traffic is blocked before backend invocation
- Sensitive headers and payload fields are sanitized
- Rate limits protect downstream services under burst traffic
Decision Framework
- Enforce server-side authorization as the source of truth for access decisions.
- Use least-privilege scopes and role mappings by default.
- If tokens are used, define validation, rotation, and revocation behavior explicitly.
- If external identity providers are involved, define outage and fallback behavior.
Common Rationalizations And Rebuttals
- "Client checks are enough." -> Client logic is bypassable; enforce checks on backend boundaries.
- "Broad scopes are easier to manage." -> Broad scopes increase blast radius and compliance risk.
- "We can add audit logs later." -> Missing audit evidence blocks incident and compliance response.
Evidence Pack
- Negative test cases for unauthorized and malformed access attempts
- Scope-to-permission mapping with owner approval
- Token/session lifecycle flow and revocation behavior proof
- Audit and security monitoring evidence for sensitive operations
Exit Criteria
- Edge security posture is enforceable and monitored
- API consumers receive consistent error and quota semantics
