OWASP / OWASP/www-project-api-security-testing-framework

[FEATURE] Logging of evidence

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

Nobody has claimed this yet.

enhancement help wanted
Dominant language
Java
Stars
150
Forks
41
Avg merge
2d 5h
Merged PRs (30d)
3

Description

First of all: great tool! ALready found some problems that needed fixing. So thank you for that! I have a suggestion below.

Problem Statement

I got some warnings about "ASTF-API2-2023 Missing Authentication Controls". I have added tons of debugging but could not find the culprit. Every request seemed to have a JWT Authorization header. So, I was looking to inspect the evidence of this problem outside my software (Laravel/Lumen Rest API). Unfortunately the ASTF tool itself did not supply these requests/responses.

Proposed Solution

A command line option to enable logging the http-requests and responses; would be great to be able to supply filename and export to JSON or HAR e.g.

Alternative Solutions

Currently I had to install OWASP ZAP and enable the proxy, run the ASTF through the proxy and inspect results.

Related OWASP API Security Standards

None

Additional Context

The OWASP ZAP proxy could supply some inspiration possibly?

Would you be willing to implement this feature?

  • I'm willing to submit a PR for this feature
  • I would need guidance to implement this feature
  • [ x] I'm not able to implement this feature

Greetings Martin

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

Start by locating the command-line option handling and the code that sends HTTP requests and receives responses in the ASTF tool. Define the export behavior for a configurable filename and JSON or HAR output; done means captured requests and responses can be inspected outside the tested application.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
cli, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.