dlmarion commented on code in PR #6490:
URL: https://github.com/apache/accumulo/pull/6490#discussion_r3639565424


##########
SECURITY.md:
##########
@@ -0,0 +1,56 @@
+## Reporting a vulnerability
+
+If after reading this document you believe you have found a vulnerability or 
are unsure,
+then please follow the [reporting 
process](https://www.apache.org/security/#reporting-a-vulnerability).
+
+## High-Level Accumulo Deployment Overview
+
+Accumulo is designed to use Apache ZooKeeper for locking and coordination 
+and one or more Hadoop Compatible File System (HCFS) implementations 
+(HDFS, S3, local disk, etc.) for storage. Accumulo users could be humans 
+or machines connecting to Accumulo server processes from any location. 
+Please see the Security section of the User Manual for information 
+regarding:
+
+  * User authentication
+  * Authorizing actions and our permission scheme
+  * Labeling data and scan-time authorizations
+  * Encryption
+
+## Security Assumptions
+
+The following items are out of our control and we assume that these items
+are configured correctly and securely or are otherwise trusted.
+
+  * Network, to include network encryption components
+  * DNS
+  * Operating Systems and related compute hardware
+  * ZooKeeper and HCFS storage configured for Accumulo's use
+  * Persons or processes that can log into an environment (bare-metal or 
container)
+    where Accumulo, ZooKeeper, or HCFS-related processes are running
+  * Accumulo configuration files (e.g. accumulo-env.sh, accumulo.properties, 
logging configuration, etc.)
+  * The JVM classpath for Accumulo processes (configured in accumulo-env.sh or 
similar mechanism)
+  * User provided code that runs in the server process via an Accumulo SPI
+  * User configured JVM agents

Review Comment:
   ```suggestion
     * User configured JVM agents
     * Bulk-imported user created RFiles (these bypass server-side checks that 
are performed during live ingest)
   ```



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to