Skip to content
2 changes: 1 addition & 1 deletion _posts/2023-11-09-14.0.1-release.md
Original file line number Diff line number Diff line change
Expand Up @@ -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]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Sorry for not answering earlier. Yes, that is the rationale. I don't know if that is a good idea as we have not been announcing security fixes consistently on the blog.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Anyway, we can remove this keyword later so it should probably not block this PR.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I agree -- if it turns out to be a problem we can remove the keyword

---
<!--
{% comment %}
Expand Down
46 changes: 46 additions & 0 deletions _posts/2026-02-09-arrow-security-model.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,46 @@
---
layout: post
title: "Introducing a Security Model for Arrow"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Upon reflection, I am not sure what we have written is really a 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

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

What we have here is more like how the ASF defines it rather than what Wikipedia makes it sound like. I don't have any issues with the current language but also have no experience in this field.

Copy link
Copy Markdown
Contributor

@alamb alamb Feb 5, 2026

Choose a reason for hiding this comment

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

Thanks -- that is a good reference. I agree per the ASF definition we have defined a security model and thus the current PR content / title is good

date: "2026-02-09 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.
Comment thread
pitrou marked this conversation as resolved.

The Arrow security model covers a core subset of the Arrow specifications:
the [Arrow Columnar Format](https://arrow.apache.org/docs/dev/format/Columnar.html),
the [Arrow C Data Interface](https://arrow.apache.org/docs/dev/format/CDataInterface.html) and the
[Arrow IPC Format](https://arrow.apache.org/docs/dev/format/Columnar.html#serialization-and-interprocess-communication-ipc).
It sets expectations and gives guidelines for handling data coming from
untrusted sources.

The specifications covered by the Arrow security model are building blocks for
all the other Arrow specifications, such as Flight and ADBC.

The ideas underlying the Arrow security model were informally shared between
Arrow maintainers and have informed decisions for years, but they were left
undocumented until now.

Implementation-specific security considerations, such as proper API usage and
runtime safety guarantees, will later be covered in the documentation of the
respective implementations.
16 changes: 13 additions & 3 deletions security.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 [private@arrow.apache.org](mailto:private@arrow.apache.org).
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 for untrusted data, as some apparent security
issues can actually be usage issues.

Second, please follow the standard [vulnerability reporting process](https://apache.org/security/#reporting-a-vulnerability)
outlined by the Apache Software Foundation. We will assess your report, follow
up with our evaluation of the issue, and fix it as soon as possible if we deem
it to be an actual security vulnerability.

<hr class="my-5">

Expand Down