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.

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

Add thank you page to SECURITY.md #165

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion CNAME
Original file line number Diff line number Diff line change
@@ -1,2 +1 @@
www.pagopa.gov.it
pagopa.gov.it
30 changes: 19 additions & 11 deletions SECURITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,10 @@ This policy describes how to send us vulnerability reports and how we ask securi
If you are the first to report a verifiable major security issue, we'll thank you with a place in our _hall of fame page_!

## Report a vulnerability
E-mail your findings to [[email protected]](mailto:[email protected]). Encrypt your findings using our [PGP key](https://www.pagopa.gov.it/publickey.txt) to prevent this critical information from falling into the wrong hands.

Give adequate information allowing the vulnerability to be reproduced, so we will be able to resolve it as quickly as possible. In particular please include at least the following information:
E-mail your findings to [[email protected]](mailto:[email protected]). You can encrypt your findings using our [PGP key](https://www.pagopa.gov.it/publickey.txt) to prevent critical information from falling in the wrong hands.

Give adequate information to reproduce the vulnerability, so we will be able to understand and resolve it as quickly as possible. In particular please include at least the following information:

- type of vulnerability;
- service or URL or IPs affected;
Expand All @@ -25,30 +26,37 @@ Give adequate information allowing the vulnerability to be reproduced, so we wil
- impact of the vulnerability together with an explanation of how an attacker could find it and exploit it.

## Guidelines

- Do not take advantage of the vulnerability or problem you have discovered.
- Do not perform any activity that can damage us or our users, disrupt the impacted system or service or cause any data leakage/loss.
- Respect the privacy of our users: you are not allowed to use any personal data for purposes other than protect our users and their data, in accordance with this policy.
- Do not perform any activity that can damage us or our users, disrupt the impacted system or service or cause any data leakage/loss. If you are unsure a test can cause harm to our systems, take a conservative approach and email your concerns directly, without doing any active testing.
- Respect the privacy of our users: you are not allowed to acquire or use any personal data for purposes other than identify a weakness in our systems, with the ultimate goal of protecting them and their data and in full accordance with this policy.
- Keep confidential any information about discovered vulnerabilities for up to 90 calendar days after you have notified pagoPA, unless mutually agreed otherwise.
- Do not place a backdoor in a system. By placing a backdoor in a system, that system becomes even more insecure.
- Do not make changes to the system or application.
- Do not use Denial of Service attacks or brute force access.
- Do not use Denial Of Service attacks or brute force access (no password guessing).
- Do not use aggressive automated scanning.
- Do not use social engineering of our employees or contractors.
- Reports about TLS ciphers, email spam, volumetric attacks, missing web security headers and "best practices" in general will **NOT** be considered as valid submissions, **unless** you are able to craft an exploit that leverages also the lack of such headers or configurations.
- Do not use social engineering of our employees or contractors (no phishing).
- Reports about TLS ciphers, email spam, potential volumetric attacks, missing web security headers and "best practices" in general will **NOT** be considered as valid submissions, **unless** you are able to craft another exploit that leverages the lack of such headers or such misconfigurations.

## What we promise

- We will respond to a valid submission within 7 business days with our evaluation of the report and an expected resolution date.
- If you have followed the instructions above, we will not take any legal action against you concerning the report.
- We will not pass on your personal details to third parties without your permission, unless it is necessary to comply with a legal obligation. Reporting under a pseudonym or anonymous is possible.
- We will not pass on your personal details to third parties without your permission, unless it is necessary to comply with a legal obligation. Reporting under a pseudonym or anonymous is also possible.
- We will keep you informed of the progress towards resolving the problem.
- For major issues, ranked so at our discretion, we can mention (if you desire) your name or acronym as the discoverer of the reported vulnerability in our _hall of fame_.
- For major issues, ranked so at our discretion, we can mention (if you desire) your name or pseudonym as the discoverer of the vulnerability in our _hall of fame_. Links to personal websites are not allowed.
- As of now, **we do NOT offer bounties** for valid submissions.

## Scope

This policy applies to the following projects directly developed or maintained by pagoPA:

- IO - [https://io.italia.it/](https://io.italia.it/)
- pagoPA - [https://www.pagopa.gov.it/](https://www.pagopa.gov.it/)
- IO - any subdomain of, including [https://io.italia.it/](https://io.italia.it/)
- pagoPA - any subdomain of, including [https://pagopa.gov.it/](https://pagopa.gov.it/)

## Hall Of Fame

- We would like to publicly thank research Anurag Kumar Rawat (Mr. Venom) for reporting a XSS vulnerability in one of our subdomains.

Thank you for helping keep pagoPA and our users safe!

Expand Down