← Back to Projects
API Security Case Study (AuthZ, Tokens, Abuse Prevention)
A portfolio-ready API security case study focusing on authorization, token handling, validation, rate limiting, and logging for investigation.
Current phase: Architecture & Design completed. Implementation in progress.
PlannedAPI SecurityWeb SecuritySecurity Architecture
Tech
REST APIsJWT/OAuth ConceptsLogging/AuditingPostman
Portfolio maturity20%
This reflects how complete the artifact is (writeup + evidence), not skill level.
Highlights
- Focus on authz correctness (prevent IDOR / broken access control)
- Threat model + mitigations mapped to practical controls
- Evidence: test cases, logs, and defensive validation patterns
Audience
Coming soon.
Problem / Goal
Coming soon.
Approach
Coming soon.
Threats (What I design against)
- Broken access control / IDOR
- Token leakage and replay
- Abuse via automation and rate-limit bypass attempts
Controls (How I mitigate)
- Centralized authorization checks
- Strict validation + safe error handling
- Rate limits + logging for investigation
Evidence
WRITEUPWriteup (coming soon)(Planned)
Evidence links will be added as artifacts are published (screenshots, configs, scan results, writeups).
Next steps
- Create the project writeup with concrete examples
- Add test cases and screenshots
- Add a threat model table mapped to controls