Skip to content

Issues: shieldfy/API-Security-Checklist

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

12 Open 31 Closed
12 Open 31 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Security Headers
#189 opened Nov 1, 2023 by beyhantanerr
Expand on the authentication suggestion
#179 opened Feb 12, 2023 by petrdvorak
HTTP Headers
#174 opened Dec 1, 2022 by tautology0
request integrity & replay enhancement
#170 opened Oct 29, 2022 by agrandville
1
JWT token should be stored securely if they are used as auth for browser users. enhancement
#153 opened Jun 18, 2021 by h4cker39
Should mention CORS enhancement
#119 opened May 21, 2019 by yippibrian
Should add "Content-Disposition" to response header?
#104 opened Mar 14, 2018 by nevermoe
Correlation with external (prior) guidelines enhancement
#27 opened Jul 11, 2017 by geovanisouza92
Suggestion: Always set charset in response header enhancement
#25 opened Jul 11, 2017 by ngyikp
1
Why no word about range, type and length checks? enhancement
#11 opened Jul 9, 2017 by baybal
1
Rationales enhancement
#8 opened Jul 9, 2017 by erlkonig
6
Don't recommend JWT enhancement
#6 opened Jul 9, 2017 by sethherr
47
ProTip! Find all open issues with in progress development work with linked:pr.