-
Notifications
You must be signed in to change notification settings - Fork 19
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
Amazon Security lake integration as source #128
Comments
OCSF v1.1.0 was released recently |
@AlexRuiz7 I am eagerly looking for the features. Any idea on release date? |
This is part of the 4.9.0 release, which is planned for Q3 2024. This project is currently on internal testing. The code and the documentation are already in this repo, so feel free to test it and report any issues you find with us so we can fix that before the release. We'd appreciate that. |
Description
Amazon Security Lake is a centralized repository of security data for AWS environments, SaaS providers, on premises, cloud sources, and third-party sources stored in your AWS account.
All the entities listed previously can read or write security lake through subscription or source integrations, respectively. Wazuh already provides an integration as a subscriber, and is listed in the Amazon Security Lake partners program.
We want to create a new integration for Amazon Security Lake, this time as a source, meaning that the designed security data hosted in
wazuh-indexer
will end up in the security lake for other third-party services to consume and analyze.Functional requirements
Non-functional requirements
Implementation restrictions
Plan
Tasks
This task list follows from the plan:
The text was updated successfully, but these errors were encountered: