alamb commented on code in PR #753: URL: https://github.com/apache/arrow-site/pull/753#discussion_r2770648027
########## _posts/2026-02-05-arrow-security-model.md: ########## @@ -0,0 +1,46 @@ +--- +layout: post +title: "Introducing a Security Model for Arrow" Review Comment: Upon reflection, I am not sure what we have written is really a [security "model" ](https://en.wikipedia.org/wiki/Computer_security_model), in that it doesn't seem to be a formal scheme for applying security policies. I would say what we have written is more like "Security Best Practices" or a Trust Model (aka what should be trusted) perhaps @raboof could help us here with the correct terminology for this concept (maybe it is Security Model) Also, perhaps we should emphasize we are not (really) introducing a new model, instead in my mind we have instead formalized what was previously implicit. Perhaps a title such as "Introducing Security Best Practices for Apache Arrow" Would emphasize this better ########## security.md: ########## @@ -6,9 +6,19 @@ description: Security # Reporting Security Issues -Apache Arrow uses the standard process outlined by the [Apache Security Team](https://www.apache.org/security/) for reporting vulnerabilities. Note that vulnerabilities should not be publicly disclosed until the project has responded. - -To report a possible security vulnerability, please email [[email protected]](mailto:[email protected]). +We take security seriously and would like our project to be as robust and +dependable as possible. If you believe to have found a security bug, please do +not file a public issue. + +First, please carefully read the Apache Arrow +[Security Model](https://arrow.apache.org/docs/dev/format/Security.html) +and understand its implications, as some apparent security issues can actually Review Comment: It might make sense here to explicitly list untrusted sources as I think that is the core potential attack vector that has been highlighted several times Something like ```suggestion and understand its implications for untrusted data sources, as some apparent security issues can actually ``` ########## _posts/2023-11-09-14.0.1-release.md: ########## @@ -3,7 +3,7 @@ layout: post title: "Apache Arrow 14.0.1 Release" date: "2023-11-09 00:00:00" author: pmc -categories: [release] +categories: [release, security] Review Comment: Is the rationale for this to be marked with security related to the fact that this release was only a security fix? > This release contains a single security fix for PyArrow. Other implementations ########## _posts/2026-02-05-arrow-security-model.md: ########## @@ -0,0 +1,46 @@ +--- +layout: post +title: "Introducing a Security Model for Arrow" +date: "2026-02-05 00:00:00" +author: pmc +categories: [arrow, security] +--- +<!-- +{% comment %} +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. +{% endcomment %} +--> + +We are thrilled to announce the official publication of a +[Security Model](https://arrow.apache.org/docs/dev/format/Security.html) for Apache Arrow. Review Comment: Maybe it is a delay, but this page does not seem to exist (yet?): https://arrow.apache.org/docs/dev/format/Security.html <img width="782" height="454" alt="Image" src="https://github.com/user-attachments/assets/bc899fd0-bba4-45d9-af50-3c72d32b610e"; /> -- 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]
