-
Notifications
You must be signed in to change notification settings - Fork 4
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
🪵 Send logs to XSIAM SoC #4697
Comments
To be refined and planned into next sprint |
Waiting for team to send current error logs before planning this. |
Spoke with MP. Their code, while getting the job done is not quite ready to be reused. They're continuing to work on it. Recommend we park until the issues are worked out. If we want to go our own way, we will need a spike first to settle on an approach. |
Further, Cortex is currently struggling to ingest the logs from MP as the number of entries and the length of individual events aren't being properly tokenized. We might want to await developments on this too. |
@darren1988 Please see the attached links to my review. I created a new column that explained my rationale for the review. Reason for Potential False Positive and Reason for Medium Severity and Not False Positive |
I have completed the review and send it to SOC for review. The SOC has sent the two 71 false positives, and 17 seem not to be False Positive to MIP to come up with a plan of action. No further action required from AP. The SOC confirmed that this ticket can be closed. |
User Story
As a SoC
I want security logs from all things
So that we have a central source of security logs in order to process for threats correlations
Value / Purpose
Security Operations Center needs our logs and they will process with Palo Alto Cortex to check for bad things.
Useful Contacts
Rich, Julia
Proposal
Do what MP/CP did see thread
Additional Information
See thread here
https://docs-cortex.paloaltonetworks.com/r/Cortex-XSIAM/Cortex-XSIAM-Administrator-Guide/Ingest-Network-Route-53-Logs-from-Amazon-S3
Definition of Done
The text was updated successfully, but these errors were encountered: