Skip to content

Commit c206c0f

Browse files
committed
NIFI-5927 Added SECURITY.md to project root.
Removed reference to Jasypt from cryptography section of README.md. Fixed JCraft link for Chrome browser. This closes apache#3243. Signed-off-by: Andrew Lim <[email protected]>
1 parent c5c2b30 commit c206c0f

File tree

2 files changed

+57
-4
lines changed

2 files changed

+57
-4
lines changed

README.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -171,12 +171,11 @@ source code.
171171

172172
The following provides more details on the included cryptographic software:
173173

174-
Apache NiFi uses BouncyCastle, Jasypt, JCraft Inc., and the built-in
175-
java cryptography libraries for SSL, SSH, and the protection
174+
Apache NiFi uses BouncyCastle, JCraft Inc., and the built-in
175+
Java cryptography libraries for SSL, SSH, and the protection
176176
of sensitive configuration parameters. See
177177
http://bouncycastle.org/about.html
178-
http://www.jasypt.org/faq.html
179-
http://jcraft.com/c-info.html
178+
http://www.jcraft.com/c-info.html
180179
http://www.oracle.com/us/products/export/export-regulations-345813.html
181180
for more details on each of these libraries cryptography features.
182181

SECURITY.md

+54
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
<!--
2+
Licensed to the Apache Software Foundation (ASF) under one or more
3+
contributor license agreements. See the NOTICE file distributed with
4+
this work for additional information regarding copyright ownership.
5+
The ASF licenses this file to You under the Apache License, Version 2.0
6+
(the "License"); you may not use this file except in compliance with
7+
the License. You may obtain a copy of the License at
8+
http://www.apache.org/licenses/LICENSE-2.0
9+
Unless required by applicable law or agreed to in writing, software
10+
distributed under the License is distributed on an "AS IS" BASIS,
11+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12+
See the License for the specific language governing permissions and
13+
limitations under the License.
14+
-->
15+
# Security Vulnerability Disclosure
16+
17+
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.
18+
19+
## Table of Contents
20+
21+
* [Disclosure Policy](#disclosure-policy)
22+
* [Exclusions](#exclusions)
23+
* [Reporting Methods](#reporting-methods)
24+
* [Publishing](#publishing)
25+
26+
## Disclosure Policy
27+
28+
* 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.
29+
* Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
30+
* 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.
31+
32+
## Exclusions
33+
34+
While researching, we'd like to ask you to refrain from:
35+
* Denial of service
36+
* Spamming
37+
* Social engineering (including phishing) of Apache NiFi staff or contractors
38+
* Any physical attempts against Apache NiFi property or data centers
39+
40+
## Reporting Methods
41+
42+
NiFi accepts reports in multiple ways:
43+
44+
* 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*.
45+
* 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.
46+
47+
## Publishing
48+
49+
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:
50+
* An email is sent to the same addresses as the release announcement ([email protected], [email protected], [email protected]), [email protected], and [email protected]
51+
* The [Mitre Common Vulnerabilities and Exposures (CVE) database](https://cveform.mitre.org/)
52+
* The [Apache NiFi Security Page](https://nifi.apache.org/security.html)
53+
54+
Thank you for helping keep Apache NiFi and our users safe!

0 commit comments

Comments
 (0)