-
Notifications
You must be signed in to change notification settings - Fork 453
[vectra_cloud] Initial release of the Vectra Cloud #13646
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
base: main
Are you sure you want to change the base?
Conversation
🚀 Benchmarks reportTo see the full report comment with |
|
💚 Build Succeeded
|
@cpascale43 @janvi-elastic can we confirm that Vectra Cloud is the the correct naming/branding of the Vectra product we're integrating with? I don't think Vectra Cloud aligns with any naming on their end. |
@jamiehynds, @cpascale43 - The customer referred to this integration as 'Vectra Cloud' in their email. We also noticed that other vendors are using the same name, so we've used 'Vectra Cloud' as well for consistency. Also based on the information available on Vectra's official website and documentation, Vectra Cloud refers to the cloud-based offerings of Vectra AI. The term "Vectra UX" in the documentation likely refers to the user interface of Vectra AI’s cloud platform. Let me know your thoughts please. |
Checking with Vectra @piyush-elastic, will keep you posted here |
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
Proposed commit message
The initial release includes an audit, entity events, detection events, health and lockdown data stream and associated dashboards and visualizations.
Vectra Cloud fields are mapped to their corresponding ECS fields where possible.
Test samples were derived from documentation, which were subsequently
sanitized.
Checklist
changelog.yml
file.How to test this PR locally
Related issues
Screenshot