Skip to content
Closed
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
5 changes: 2 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Contributor

@andrewmlim andrewmlim Jan 4, 2019

Choose a reason for hiding this comment

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

I noticed that this jcraft link doesn't work in Chrome (Version 71.0.3578.98), but does for Safari and FireFox. Chrome requires:

http://www.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.
Expand Down
54 changes: 54 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -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 [security@nifi.apache.org](mailto:security@nifi.apache.org). 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 (dev@nifi.apache.org, users@nifi.apache.org, announce@apache.org), security@nifi.apache.org, and oss-security@lists.openwall.com
* 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!