amoeba commented on code in PR #5058:
URL: https://github.com/apache/arrow-adbc/pull/5058#discussion_r4648945215


##########
docs/source/security_policy.rst:
##########
@@ -0,0 +1,72 @@
+.. 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 Policy
+===============
+
+This document outlines the security model for ADBC libraries and drivers and 
how to report vulnerabilities.
+
+Security Model
+==============
+
+The ADBC project follows the `Apache Arrow Security Model 
<arrow_security_model_>`_ and builds on it.
+
+In general, crashes, hangs, and resource exhaustion are considered bugs, not 
security vulnerabilities, unless they can be exploited to execute arbitrary 
code, escalate privileges, or disclose data the attacker should not have access 
to (such as the contents of process memory).
+
+.. _arrow_security_model: https://arrow.apache.org/docs/format/Security.html
+
+Libraries
+---------
+
+This section covers all language bindings and driver managers that live in 
this repository.
+
+- Applications should only load trusted drivers with a driver manager.
+  Issues resulting from loading a driver that behaves maliciously are not 
covered by this policy.
+- Applications should only load trusted driver manifests or connection 
profiles with a driver manager.
+  Issues resulting from loading untrusted manifests or profiles are not 
covered by this policy.
+
+Drivers

Review Comment:
   This section could go further, depending on how people feel. [PostgreSQL has 
this bit](https://www.postgresql.org/support/security/),
   
   > A security vulnerability in PostgreSQL is an issue that allows a user to 
gain access to privileges or data that they do not have permission to use, or 
allows a user to execute arbitrary code through a PostgreSQL process.
   > The PostgreSQL Security Team does not consider reports on actions a 
PostgreSQL superuser takes to be a security vulnerability. However, a report on 
an unprivileged user escalating to superuser generally qualifies as valid.
   
   In the case of the ADBC PostgreSQL driver, an issue like this would most 
likely not be an ADBC driver bug but a rather a libpq bug. But we'd still want 
to patch, though I'm not sure we'd issue ourselves a CVE. Thoughts?



-- 
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