Skip to content
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.

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

OWASP Top 10 API Security Assessment #23

Open
nandhued opened this issue Oct 18, 2024 · 4 comments
Open

OWASP Top 10 API Security Assessment #23

nandhued opened this issue Oct 18, 2024 · 4 comments
Assignees

Comments

@nandhued
Copy link

nandhued commented Oct 18, 2024

Part of #9

@nandhued nandhued converted this from a draft issue Oct 18, 2024
@nandhued
Copy link
Author

Doc WIP

@PrimalPimmy
Copy link
Member

@PrimalPimmy
Copy link
Member

PrimalPimmy commented Oct 22, 2024

Action items for analysis:

  • Checkout other api security projects like Akto and Astra and see their logic for API testing.
  • Check how the sentryflow logs can be used to detect attacks

@PrimalPimmy
Copy link
Member

  1. Broken Object Level Authorization

    • Check the authorization/JWT header token and see if the user is accessing another user's resources.
  2. Broken Authentication

    • Check JWT's alg header, if this is empty, the token is not valid.
  3. Broken Object Property Level Authorization

    • Could check if the IP where this request originates from is outside the enviroment.
  4. Unrestricted Resource Consumption

    • Rate limit detection through observability API. Check the timestamp and number of events.
  5. Broken Function Level Authorization

    • This usually means someone accessing a privileged endpoint. How would be check what's a privileged endpoint and what's not?
  6. Unrestricted Access to Sensitive Business Flows

    • N/A
  7. Server Side Request Forgery

    • Check for client-supplied input data sanitization. Not too tough to check for sanitization. This could also work for XSS and SQLi
  8. Security Misconfiguration

    • Internal error revealing internal code. Not something we can check everywhere.
  9. Improper Inventory Management

    • Old APIs get exploited if not depricated by newer APIs. Can't check for this using sentryflow
  10. Unsafe Consumption of APIs

    • Santization of Data to be checked to prevent SQLi, XSS, SSRF, etc. Can be done by sanitizing Request body.

@nandhued nandhued moved this from 🏗 In progress to 👀 In review in SentryFlow Nov 4, 2024
@nandhued nandhued moved this from 👀 In review to ✅ Done in SentryFlow Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

No branches or pull requests

2 participants