Skip to content

[checkpoint_email] Populate additional ECS fields for the event types phishing, spam, and malicious_url - #15141

Merged
brijesh-elastic merged 4 commits into
elastic:mainfrom
brijesh-elastic:checkpoint_email-1.2.0
Sep 17, 2025
Merged

[checkpoint_email] Populate additional ECS fields for the event types phishing, spam, and malicious_url#15141
brijesh-elastic merged 4 commits into
elastic:mainfrom
brijesh-elastic:checkpoint_email-1.2.0

Conversation

@brijesh-elastic

Copy link
Copy Markdown
Contributor

Proposed commit message

checkpoint_email: Populate additional ECS fields for the event types phishing, spam, and malicious_url

It will parse the email.*, destination.user.*, source.user.*, and checkpoint_email.event.scan_type fields
for the phishing, spam, and malicious_url event types. All these fields are parsed using
grok patterns on the checkpoint_email.event.data field.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

How to test this PR locally

  • Clone integrations repo.
  • Install elastic package locally.
  • Start elastic stack using elastic-package.
  • Move to integrations/packages/checkpoint_email directory.
  • Run the following command to run tests.

elastic-package test

Related issues

@brijesh-elastic brijesh-elastic self-assigned this Sep 3, 2025
@brijesh-elastic
brijesh-elastic requested a review from a team as a code owner September 3, 2025 06:35
@brijesh-elastic brijesh-elastic added documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. enhancement New feature or request Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] mapping/pipeline issue Integration:checkpoint_email Check Point Harmony Email & Collaboration Team:SDE-Crest Crest developers on the Security Integrations team [elastic/sit-crest-contractors] labels Sep 3, 2025
@elasticmachine

Copy link
Copy Markdown

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

Comment thread packages/checkpoint_email/data_stream/event/fields/fields.yml Outdated
@elasticmachine

Copy link
Copy Markdown

💚 Build Succeeded

History

cc @brijesh-elastic

@brijesh-elastic
brijesh-elastic merged commit 7a13c41 into elastic:main Sep 17, 2025
9 checks passed
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Package checkpoint_email - 1.2.0 containing this change is available at https://epr.elastic.co/package/checkpoint_email/1.2.0/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. enhancement New feature or request Integration:checkpoint_email Check Point Harmony Email & Collaboration mapping/pipeline issue Team:SDE-Crest Crest developers on the Security Integrations team [elastic/sit-crest-contractors] Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

3 participants