We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There is an ecs field for email.from.address which is the From field in the email header.
The mailfrom field in the smtp header is a field useful for detecting email spoofing.
Please add email.mailfrom.address to ecs. Also update the mimecast integration to extract the headerFrom field from the inbound Acc logs.
The text was updated successfully, but these errors were encountered:
@mjwolf investigate if mailfrom is a standard smtp header. find out all integration that can normalize to this field if we were to add this into ECS
Sorry, something went wrong.
MAIL FROM and RCPT TO are both fields of SMTP envelope from RFC 5321.
It's currently used in these integrations zeek, proofpoint_on_demand, cisco_secure_email_gateway, m365_defender, sublime_security.
zeek
proofpoint_on_demand
cisco_secure_email_gateway
m365_defender
sublime_security
Given this is a standard SMTP field, and used by multiple observability products, I think it makes sense to add this to ECS
mjwolf
Successfully merging a pull request may close this issue.
There is an ecs field for email.from.address which is the From field in the email header.
The mailfrom field in the smtp header is a field useful for detecting email spoofing.
Please add email.mailfrom.address to ecs. Also update the mimecast integration to extract the headerFrom field from the inbound Acc logs.
The text was updated successfully, but these errors were encountered: