shieldfy/api-security-checklist

Checklist of the most important security countermeasures when designing, testing, and releasing your API

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 48 minutes ago
Added to GitGenius on September 2nd, 2026
Created on July 8th, 2017
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 2,651
Total Stargazers: 23,313 (+0)
Total Subscribers: 533 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 28.7 days
Mean response time: 808.8 days
90th percentile: 2449.3 days
Tracked items: 21

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 200 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (8)
  • invalid (8)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

API Security Checklist is a security reference guide that provides a comprehensive checklist of countermeasures for designing, testing, and releasing APIs.

The guide addresses the core security concerns that arise throughout an API's lifecycle. It organizes security practices into distinct categories covering authentication, access control, authorization, input validation, and processing. For authentication, it recommends avoiding Basic Auth in favor of standard approaches and emphasizes proper token generation and password storage practices. For access control, it covers rate limiting, HTTPS with modern TLS versions, HSTS headers, and IP safelisting for private APIs. Authorization guidance focuses on OAuth implementation details such as server-side redirect URI validation, state parameter usage for CSRF prevention, and scope management. Input validation guidance addresses HTTP method correctness, content-type validation, user input sanitization against common vulnerabilities like XSS and SQL injection, and the proper handling of sensitive data through Authorization headers rather than URLs. The guide also recommends using API Gateway services for caching and rate limiting policies.

This checklist suits teams building or securing APIs who want a structured reference for security best practices. It works well as an onboarding resource for developers new to API security or as an audit tool for existing APIs. The guide does not position itself against alternatives; it presents itself as a standards-based compilation of established security practices.

The project maintains translations across numerous languages, indicating sustained effort to make the material accessible to a global audience. The repository accepts contributions and updates to keep the checklist current with evolving security standards and threats.