[Filebeat] Do not run azure-eventhub input and azure module in FIPS builds#44902
Merged
ycombinator merged 4 commits intoelastic:mainfrom Jun 25, 2025
Merged
[Filebeat] Do not run azure-eventhub input and azure module in FIPS builds#44902ycombinator merged 4 commits intoelastic:mainfrom
azure-eventhub input and azure module in FIPS builds#44902ycombinator merged 4 commits intoelastic:mainfrom
Conversation
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Contributor
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
2bd14ee to
b176324
Compare
6 tasks
Contributor
|
Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services) |
Contributor
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
andrzej-stencel
approved these changes
Jun 24, 2025
58ac838 to
ff38f92
Compare
Kavindu-Dodan
approved these changes
Jun 24, 2025
azure-eventhub input and azure module in FIPS buildsazure-eventhub input and azure module in FIPS builds
ff38f92 to
80a7d96
Compare
Contributor
Author
|
@Mergifyio backport 9.1 |
Contributor
✅ Backports have been createdDetails
|
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
This PR ensures that the Filebeat
azure-eventhubinput will not start in FIPS-capable distributions of Filebeat, as the input indirectly depends on code that is not FIPS-compliant. Specifically, theazure-eventhubinput depends on thegithub.com/Azure/azure-sdk-for-go/sdk/azidentitypackage. This package, in turn, depends on thegolang.org/x/crypto/pkcs12package, which is not FIPS-compliant. Further, the SDK doesn't plan to offer a way to disable the use of this package at compile time (see Azure/azure-sdk-for-go#24336).In addition to the
azure-eventhubinput, theazuremodule will also not start in FIPS-capable distributions of Filebeat, as this module uses theazure-eventhubinput.Attempting to run a FIPS-capable distribution of Filebeat with either the
azure-eventhubinput or theazuremodule configured will result in Filebeat not starting up and an error in the Filebeat logs like so:The
o365auditinput declares itself as not being FIPS-capable by setting theExcludeFromFIPSfield on thev2.Pluginstruct totrue(see also: #45036).Checklist
I have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry inCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Disruptive User Impact
FIPS-capable artifacts of Filebeat will not start the
azuremodule or theazure-eventhubinput.