Added Ability to Edit found_by value in API

[Jino-T]

[sc-11934]

Tested and functional in API.

Not able to remove found_by value associated with finding's test.

• Ex: If finding was imported with Semgrep parser, you are unable to remove Semgrep from the found_by field.
• A separate portion of code must check to make sure that this value is always present in found_by.
• Let me know if you want me to look into this further and allow this functionality.

[dryrunsecurity]

🔴 Risk threshold exceeded.

This pull request modifies a sensitive file (dojo/api_v2/serializers.py) with detected sensitive edits; review is recommended and you can configure sensitive paths and allowed authors in .dryrunsecurity.yaml. The scanner flagged the same file twice at a failing risk threshold but the findings are non-blocking.

🔴 Configured Codepaths Edit in dojo/api_v2/serializers.py

Vulnerability	Configured Codepaths Edit
Description	Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml.

🔴 Configured Codepaths Edit in dojo/api_v2/serializers.py

Vulnerability	Configured Codepaths Edit
Description	Sensitive edits detected for this file. Sensitive file paths and allowed authors can be configured in .dryrunsecurity.yaml.

We've notified @mtesauro.

---

All finding details can be found in the DryRun Security Dashboard.

[valentijnscholten]

I wonder how this field is used/edited? In the code it looks like it's only used to maintain a list of test types that reported this finding via the set of duplicates?

[Jino-T]

Good idea Cody. I tested your suggestion and it works in the API.

Changes were made