Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Security document update#8233

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.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
cyber-0ps wants to merge3 commits intozaproxy:main
base:main
Choose a base branch
Loading
fromcyber-0ps:security-document-update

Conversation

@cyber-0ps
Copy link

Added direct links to reporting a bug, scan policies, and terms of use in order to make the document more robust and accessible to users of the product. Added (lack of) security advisory. Document updated with intent and scope of product use with words of caution to users while using the application.

…mer to SECURITY.md document Signed-off-by: Kuljot Biring <ksbiring1@gmail.com>
…ext, bold text for bottom of disclaimer Signed-off-byL Kuljot Biring <ksbiring1@gmail.com>
@cyber-0pscyber-0psforce-pushed thesecurity-document-update branch from2ba4609 to4231261CompareDecember 9, 2023 01:35
@kingthorin
Copy link
Member

@cyber-0ps
Copy link
Author

I agree withdevelopercertificate.org.

Copy link
Member

@kingthorinkingthorin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I'm not sure this is necessary or the correct place but here's a first quick review

@@ -1,3 +1,4 @@

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This white space change is unnecessary


##Reporting a Bug

Please report any bugs via our issue[Bug Issue Tracker](https://github.com/zaproxy/zaproxy/issues/new/choose)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Drop “issue” before the link


##Security Advisories

Currently, there are not any published security advisories.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I’m don’t think this is true/accurate, I’d have to go digging. Pretty sure we have/had at least one.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

We have had some security bugs reported which we've fixed, but we have not published ny security advisories.
Maybe we should...

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I thought one or two had assigned CVEs (via the reporter not us), which I was lumping into the 'advisory' category.


All rules are contained in add-ons so that they can be updated quickly and easily.

Active scanning is an attack on those targets.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

What targets? The text was just talking about scan rules

You should NOT use it on web applications that you do not own.

It should be noted that active scanning can only find certain types of vulnerabilities.
Logical vulnerabilities, such as broken access control, will not be found by any active or automated vulnerability scanning.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This isn’t really true, you can use the Access Control add-on to scan for those. It would be more realistic to say something about business logic issues.

All rules are contained in add-ons so that they can be updated quickly and easily.

Active scanning is an attack on those targets.
You should NOT use it on web applications that you do not own.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

The note below is more accurate, you don’t have to own it to be authorized to asses something


2. Legality and Compliance: You alone are responsible for ensuring that your use of Zaproxy complies with all applicable laws, regulations, and ethical standards. Please follow the applicable legal requirements and industry best practices at all times.

3. Privacy and Data Protection: When using Zaproxy, refrain from engaging in activities that compromise the privacy or security of data, PII and other sensitive data.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

PII and sensitive data are data. This should be shortened

@thc202
Copy link
Member

I'm not sure this is necessary or the correct place but here's a first quick review

I agree.


By using Zaproxy, you agree to comply with the terms and conditions below. Terms and conditions may be subject to change or modification at any time. Users are responsible for reviewing the terms regularly to ensure compliance with the latest version.

1. Authorized Usage: You may only use Zaproxy for the purpose of assessing the security of web applications for which you have explicit and authorized access, permission, or ownership. Unauthorized scanning is strictly prohibited and unlawful.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

We never useZaproxy in this context, so this should beZAP.
https://www.zaproxy.org/docs/developer/dev-rules-and-guidelines/#style-guidelines


5. Use of this tool may cause disruption or unintended consequences to web applications and systems. The user is responsible for any damages or issues that may arise during or after the use of this tool.


Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Zaproxy would cannot be held responsible legally for any misuse of the product, not permitted by Zaproxy policy.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I prefer the existing text.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@psiinonpsiinonpsiinon left review comments

@kingthorinkingthorinkingthorin left review comments

+1 more reviewer

@HumzAhmeHumzAhmeHumzAhme left review comments

Reviewers whose approvals may not affect merge requirements

At least 2 approving reviews are required to merge this pull request.

Assignees

No one assigned

Labels

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@cyber-0ps@kingthorin@thc202@psiinon@HumzAhme

[8]ページ先頭

©2009-2025 Movatter.jp