alopresto closed pull request #3243: NIFI-5927 Added SECURITY.md to project 
root.
URL: https://github.com/apache/nifi/pull/3243
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/README.md b/README.md
index 9f65d94337..e704b5d359 100644
--- a/README.md
+++ b/README.md
@@ -171,11 +171,10 @@ source code.
 
 The following provides more details on the included cryptographic software:
 
-Apache NiFi uses BouncyCastle, Jasypt, JCraft Inc., and the built-in
-java cryptography libraries for SSL, SSH, and the protection
+Apache NiFi uses BouncyCastle, JCraft Inc., and the built-in
+Java cryptography libraries for SSL, SSH, and the protection
 of sensitive configuration parameters. See
 http://bouncycastle.org/about.html
-http://www.jasypt.org/faq.html
 http://jcraft.com/c-info.html
 http://www.oracle.com/us/products/export/export-regulations-345813.html
 for more details on each of these libraries cryptography features.
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 0000000000..e52e6174aa
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,54 @@
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+      http://www.apache.org/licenses/LICENSE-2.0
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+# Security Vulnerability Disclosure
+
+Apache NiFi welcomes the responsible reporting of security vulnerabilities. 
The NiFi team believes that working with skilled security researchers across 
the globe is crucial in identifying weaknesses in any technology. If you 
believe you've found a security issue in our product or service, we encourage 
you to notify us. We will work with you to resolve the issue promptly.
+
+## Table of Contents
+
+* [Disclosure Policy](#disclosure-policy)
+* [Exclusions](#exclusions)
+* [Reporting Methods](#reporting-methods)
+* [Publishing](#publishing)
+
+## Disclosure Policy
+
+* Let us know as soon as possible upon discovery of a potential security 
issue, and we'll make every effort to quickly resolve the issue.
+* Provide us a reasonable amount of time to resolve the issue before any 
disclosure to the public or a third-party.
+* Make a good faith effort to avoid privacy violations, destruction of data, 
and interruption or degradation of our service. Only interact with accounts you 
own or with explicit permission of the account holder.
+
+## Exclusions
+
+While researching, we'd like to ask you to refrain from:
+* Denial of service
+* Spamming
+* Social engineering (including phishing) of Apache NiFi staff or contractors
+* Any physical attempts against Apache NiFi property or data centers
+
+## Reporting Methods
+
+NiFi accepts reports in multiple ways:
+
+* Send an email to 
[[email protected]](mailto:[email protected]). This is a private 
list monitored by the [PMC](https://nifi.apache.org/people.html). For sensitive 
disclosures, the GPG key fingerprint is *1230 3BB8 1F22 E11C 8725 926A AFF2 
B368 23B9 44E9*.
+* NiFi has a [HackerOne](https://hackerone.com/apache_nifi) project page. 
HackerOne provides a triaged process for researchers and organizations to 
collaboratively report and resolve security vulnerabilities.
+
+## Publishing
+
+Apache NiFi follows the [ASF Project Security For 
Committers](https://www.apache.org/security/committers.html) policy. Thus, any 
vulnerability is not disclosed by the project until a released version which 
mitigates the issue is available for download. Once this release is available, 
the issue is fully documented in the following locations:
+* An email is sent to the same addresses as the release announcement 
([email protected], [email protected], [email protected]), 
[email protected], and [email protected]
+* The [Mitre Common Vulnerabilities and Exposures (CVE) 
database](https://cveform.mitre.org/)
+* The [Apache NiFi Security Page](https://nifi.apache.org/security.html)
+
+Thank you for helping keep Apache NiFi and our users safe!
\ No newline at end of file


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to