Skip to content

Commit 0d7326a

Browse files
pitrouamoeba
andauthored
Announce Arrow security model (#753)
1. Add a blog post announcing the [recently published](apache/arrow#48870) security model document 2. Reword security page to more explicitly outline the procedure, pointing to the security model as required reading before reporting a potential vulnerability --------- Co-authored-by: Bryce Mecum <petridish@gmail.com>
1 parent a7d4b0a commit 0d7326a

3 files changed

Lines changed: 60 additions & 4 deletions

File tree

_posts/2023-11-09-14.0.1-release.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ layout: post
33
title: "Apache Arrow 14.0.1 Release"
44
date: "2023-11-09 00:00:00"
55
author: pmc
6-
categories: [release]
6+
categories: [release, security]
77
---
88
<!--
99
{% comment %}
Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
layout: post
3+
title: "Introducing a Security Model for Arrow"
4+
date: "2026-02-09 00:00:00"
5+
author: pmc
6+
categories: [arrow, security]
7+
---
8+
<!--
9+
{% comment %}
10+
Licensed to the Apache Software Foundation (ASF) under one or more
11+
contributor license agreements. See the NOTICE file distributed with
12+
this work for additional information regarding copyright ownership.
13+
The ASF licenses this file to you under the Apache License, Version 2.0
14+
(the "License"); you may not use this file except in compliance with
15+
the License. You may obtain a copy of the License at
16+
17+
http://www.apache.org/licenses/LICENSE-2.0
18+
19+
Unless required by applicable law or agreed to in writing, software
20+
distributed under the License is distributed on an "AS IS" BASIS,
21+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
22+
See the License for the specific language governing permissions and
23+
limitations under the License.
24+
{% endcomment %}
25+
-->
26+
27+
We are thrilled to announce the official publication of a
28+
[Security Model](https://arrow.apache.org/docs/dev/format/Security.html) for Apache Arrow.
29+
30+
The Arrow security model covers a core subset of the Arrow specifications:
31+
the [Arrow Columnar Format](https://arrow.apache.org/docs/dev/format/Columnar.html),
32+
the [Arrow C Data Interface](https://arrow.apache.org/docs/dev/format/CDataInterface.html) and the
33+
[Arrow IPC Format](https://arrow.apache.org/docs/dev/format/Columnar.html#serialization-and-interprocess-communication-ipc).
34+
It sets expectations and gives guidelines for handling data coming from
35+
untrusted sources.
36+
37+
The specifications covered by the Arrow security model are building blocks for
38+
all the other Arrow specifications, such as Flight and ADBC.
39+
40+
The ideas underlying the Arrow security model were informally shared between
41+
Arrow maintainers and have informed decisions for years, but they were left
42+
undocumented until now.
43+
44+
Implementation-specific security considerations, such as proper API usage and
45+
runtime safety guarantees, will later be covered in the documentation of the
46+
respective implementations.

security.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,19 @@ description: Security
66

77
# Reporting Security Issues
88

9-
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.
10-
11-
To report a possible security vulnerability, please email [private@arrow.apache.org](mailto:private@arrow.apache.org).
9+
We take security seriously and would like our project to be as robust and
10+
dependable as possible. If you believe to have found a security bug, please do
11+
not file a public issue.
12+
13+
First, please carefully read the Apache Arrow
14+
[Security Model](https://arrow.apache.org/docs/dev/format/Security.html)
15+
and understand its implications for untrusted data, as some apparent security
16+
issues can actually be usage issues.
17+
18+
Second, please follow the standard [vulnerability reporting process](https://apache.org/security/#reporting-a-vulnerability)
19+
outlined by the Apache Software Foundation. We will assess your report, follow
20+
up with our evaluation of the issue, and fix it as soon as possible if we deem
21+
it to be an actual security vulnerability.
1222

1323
<hr class="my-5">
1424

0 commit comments

Comments
 (0)