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.

Sign up for GitHub

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

Jump to bottom

Describe way to identifiy SecHub DAST scans #3649

Open
de-jcup opened this issue Nov 26, 2024 · 0 comments · May be fixed by #3770
Open

Describe way to identifiy SecHub DAST scans #3649

de-jcup opened this issue Nov 26, 2024 · 0 comments · May be fixed by #3770

Comments

@de-jcup
Copy link
Member

de-jcup commented Nov 26, 2024

Situation

With #3644 we wanted a dedicated identifier field inside sechub configuration.

But it is enough to just document that inside a web scan it is possible to define custom headers.

Wanted

It shall be clear for users how to define custom headers to determine scan is from SecHub or an attacker

Solution

Update documentation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add documentation example how to identify sechub webscans #3649 mercedes-benz/sechub
1 participant
@de-jcup