You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the initiative: Elastic Agent and Beats FIPS Compliance, one of the responsibilities of the Deployment and Devices team is to investigate the required development for OSQueryManager and OSQueryd to be inline with the Elastic requirement.
Note: Early understanding is that osqueryd binary is not controlled by Elastic. OSQueryManager pulls the most recent release and incorporates that within its release CI pipeline when packaging the final binary
Spike:
Investigate if osqueryd does have FIPS binary support
Work with the team managing the requirement to see what exceptions are needed if we can not control osqueryd binary
Investigate alternatives, including upstreaming changes, packaging osqueryd separately or any other way to get FIPS compliance
The text was updated successfully, but these errors were encountered:
Parent Ticket:
https://github.com/elastic/ingest-dev/issues/4046
Description
Due to the initiative: Elastic Agent and Beats FIPS Compliance, one of the responsibilities of the Deployment and Devices team is to investigate the required development for OSQueryManager and OSQueryd to be inline with the Elastic requirement.
Note: Early understanding is that osqueryd binary is not controlled by Elastic. OSQueryManager pulls the most recent release and incorporates that within its release CI pipeline when packaging the final binary
Spike:
osqueryd
does have FIPS binary supportThe text was updated successfully, but these errors were encountered: