OWASP / OWASP/crAPI

Add a way to demonstrate insufficient logging and monitoring vulnerabilities in crAPI

Open
#123 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement hacktoberfest
Dominant language
Java
Stars
1.6k
Forks
645
Avg merge
37m
Merged PRs (30d)
1

Description

Is your feature request related to a problem? Please describe.
crAPI doesn't have the capability to demo insufficient logging and monitoring vulnerability which is OWASP API 10:2019.

Describe the solution you'd like
API10:2019 Insufficient Logging & Monitoring includes two CWEs:

We want to add the capability to demonstrate both of them.

Describe alternatives if any you've considered
NA

Additional context
NA

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by reviewing crAPI's existing API behavior and security demonstrations, then define how both CWE-223 and CWE-778 should be demonstrated; done means the feature covers both requested weaknesses.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, observability, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.