Nosey Parker description fixes

[tpat13]

Current issue with the Nosey Parker parser:

The parser currently grabs a code snippet for the secret found in source code. This code snippet is taken directly from the Nosey Parker JSONL output. However, in some cases, secrets are printed out in Defect Dojo (in plaintext) if they are in the line before and after the matching secret.

Checklist

This checklist is for your information.

• Make sure to rebase your PR against the very latest dev.
• Features/Changes should be submitted against the dev.
• Give a meaningful name to your PR, as it may end up being used in the release notes.
• Your code is flake8 compliant.
• Your code is python 3.11 compliant.

[dryrunsecurity]

Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.

DryRun Security	Status	Findings
Sensitive Functions Analyzer	✅	0 findings
Configured Sensitive Files Analyzer	❌	1 findings
Sensitive Files Analyzer	❕	3 findings

Note

🔴 Risk threshold exceeded. Adding a reviewer if one is configured in .dryrunsecurity.yaml.

notification list: @mtesauro @grendel513

Tip

Get answers to your security questions. Add a comment in this PR starting with @DryRunSecurity. For example...

@dryrunsecurity What are common security issues with web application cookies?

Powered by DryRun Security

[mtesauro]

Approved