vaquarkhan/fullstack-development-agent-skills

api-gateway-and-edge-security

Design API gateway policies for auth, rate limits, WAF controls, request validation, and zero-trust edge posture.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/vaquarkhan/fullstack-development-agent-skills --skill api-gateway-and-edge-security

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

API Gateway And Edge Security

Use When

  • Exposing APIs to public clients or partners
  • Centralized edge policy is required for governance

Workflow

  1. Define route-level authn and authz requirements.
  2. Configure request validation and schema enforcement at edge.
  3. Apply IP, token, and tenant-aware rate limiting.
  4. Add WAF, bot mitigation, and abuse detection rules.
  5. 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

관련 작업