-
Notifications
You must be signed in to change notification settings - Fork 474
Add fips_compatible
flag to multiple packages
#14068
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
fips_compatible
flag to multiple packages
sql_input also needs to be disabled but migration to package-spec v3+ is something we tried earlier but we couldn't migrate. |
Although we want to disable sql_input but we can't as of now because of: elastic/package-spec#901 |
Also, tests are failing as it's saying GA packages are using unreleased version: v3.4.0 of package-spec.
|
packages/oracle/manifest.yml
Outdated
@@ -12,6 +12,7 @@ conditions: | |||
version: "^8.13.0 || ^9.0.0" | |||
elastic: | |||
subscription: basic | |||
fips_compatible: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From which stack version onwards are we claiming FIPS compatibility?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a package-spec thing. For stacks, versions 8.19.0 and 9.1.0 onwards are going to be FIPS 140-2 compliant but I think the change here doesn't matter regardless of the stack.
In case we fix the modules to be compliant in future, then we can bump the stack and make this flag true.
@shmsr Since the dependency is not on this as confirmed here, are we including this for disabling fips flag ? |
As pointed by Jaime, there's no version constraint for the flag. As soon as the latest spec releases, and CI passes will make the change for sql_input. |
cbd5acf
to
57491e4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Adds a new fips_compatible
flag (set to false
) to several package manifests to prevent their use in FedRAMP High environments. It also bumps each package’s format_version
and version
, and records the change in each package’s changelog.
- Update manifest schema to 3.4.0 and bump package versions
- Add
fips_compatible: false
under theelastic
condition - Insert corresponding enhancement entries in each package’s
changelog.yml
Reviewed Changes
Copilot reviewed 14 out of 14 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
packages/sql_input/manifest.yml | Bump format & version; add fips_compatible under elastic |
packages/sql_input/changelog.yml | Add changelog entry for the new fips_compatible flag |
packages/postgresql/manifest.yml | Bump format & version; add fips_compatible under elastic |
packages/postgresql/changelog.yml | Add changelog entry for the new fips_compatible flag |
packages/oracle/manifest.yml | Bump format & version; add fips_compatible under elastic |
packages/oracle/changelog.yml | Add changelog entry for the new fips_compatible flag |
packages/mysql/manifest.yml | Bump format & version; add fips_compatible under elastic |
packages/mysql/changelog.yml | Add changelog entry for the new fips_compatible flag |
packages/mongodb/manifest.yml | Bump format & version; add fips_compatible under elastic |
packages/mongodb/changelog.yml | Add changelog entry for the new fips_compatible flag |
packages/microsoft_sqlserver/manifest.yml | Bump format & version; add fips_compatible under elastic |
packages/microsoft_sqlserver/changelog.yml | Add changelog entry for the new fips_compatible flag |
packages/azure/manifest.yml | Bump format & version; add fips_compatible under elastic |
packages/azure/changelog.yml | Add changelog entry for the new fips_compatible flag |
Comments suppressed due to low confidence (3)
packages/postgresql/manifest.yml:14
- [nitpick] Consider using consistent quoting for the
subscription
value (e.g., change to"basic"
) across all manifests to maintain style uniformity.
subscription: basic
packages/azure/manifest.yml:21
- Add or update the package’s README (or central developer docs) to include an explanation of the new
fips_compatible
flag and its effect in FedRAMP environments.
fips_compatible: false
packages/sql_input/manifest.yml:15
- Verify that the
fips_compatible
field is correctly indented under theelastic
section; incorrect indentation could cause YAML parsing errors or the flag to be ignored.
fips_compatible: false
@jsoriano / @mrodm I am still getting the error:
I thought integrations repo has been updated with the latest version of ep and hence the 3.4.0 spec, so why am I getting this error. Can you please help? |
The flag was added at the package policy level, not at the root level of the manifest. Also, it was added only for integration packages, not for input packages. I have prepared a PR with tests that illustrate where the flag is expected, and with support for input packages: elastic/package-spec#914 |
Thanks a lot @jsoriano! @tommyers-elastic For now I am leaving out |
🚀 Benchmarks reportTo see the full report comment with |
Can someone from @elastic/obs-ds-hosted-services also please review? Based on the modules that have been disabled in Beats, I have disabled them in Integrations as well. SQL input still remains as the flag is not available as of yet for input packages. |
@shmsr : Changes look good. |
The modules are using code that contains FIPS non-approved cryptographic algorithms, either directly or through dependencies. While we could have kept some modules enabled since we're unlikely to execute the non-compliant code paths (as per manual review), keeping them enabled helped us identify the problematic libraries in our dependency tree (e.g., azure). Therefore, we've disabled all modules that could potentially execute non-FIPS-compliant code paths. |
💛 Build succeeded, but was flaky
Failed CI StepsHistory
cc @shmsr |
|
Package azure - 1.28.0 containing this change is available at https://epr.elastic.co/package/azure/1.28.0/ |
Package microsoft_sqlserver - 2.13.0 containing this change is available at https://epr.elastic.co/package/microsoft_sqlserver/2.13.0/ |
Package mongodb - 1.21.0 containing this change is available at https://epr.elastic.co/package/mongodb/1.21.0/ |
Package mysql - 1.27.0 containing this change is available at https://epr.elastic.co/package/mysql/1.27.0/ |
Package oracle - 1.30.0 containing this change is available at https://epr.elastic.co/package/oracle/1.30.0/ |
Package postgresql - 1.30.0 containing this change is available at https://epr.elastic.co/package/postgresql/1.30.0/ |
Proposed commit message
Add a
fips_compatible
flag to some packages that we don't want to allow in FedRAMP env.Checklist
changelog.yml
file.