Skip to content
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

New integration - ESET Threat Intelligence #9255

Merged
merged 9 commits into from
Mar 27, 2024
Merged

Conversation

MichalVisnovsky
Copy link
Contributor

What does this PR do?

PR adds integration package for ESET Threat Intelligence data feeds.

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.

Author's Checklist

  • [ ]

Copy link

cla-checker-service bot commented Mar 1, 2024

💚 CLA has been signed

@kcreddy
Copy link
Contributor

kcreddy commented Mar 4, 2024

/test

@MichalVisnovsky
Copy link
Contributor Author

I changed my primary email to the one that was in the CLA, as it was set to my personal mail. Please try building it now.

@kcreddy
Copy link
Contributor

kcreddy commented Mar 4, 2024

/test

1 similar comment
@kcreddy
Copy link
Contributor

kcreddy commented Mar 4, 2024

/test

@elasticmachine
Copy link

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

@kcreddy
Copy link
Contributor

kcreddy commented Mar 5, 2024

/test

@kcreddy
Copy link
Contributor

kcreddy commented Mar 5, 2024

@MichalVisnovsky Can you please add following line into .github/CODEOWNERS file:

/packages/ti_eset @elastic/security-service-integrations

@kcreddy
Copy link
Contributor

kcreddy commented Mar 5, 2024

/test

@kcreddy kcreddy added Team:Security-Service Integrations Security Service Integrations Team and removed Team:Security-Service Integrations Security Service Integrations Team labels Mar 5, 2024
Copy link
Contributor

@kcreddy kcreddy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for PR once again 😄
I like the dashboards, just quick question:
Were they pointing at destination index, so we are only querying the latest active indicators? if not, you can query using _index: <alias name> or with NOT labels.is_ioc_transform_source: true

packages/ti_eset/_dev/build/build.yml Outdated Show resolved Hide resolved
packages/ti_eset/_dev/build/docs/README.md Show resolved Hide resolved
packages/ti_eset/manifest.yml Outdated Show resolved Hide resolved
packages/ti_eset/_dev/build/docs/README.md Show resolved Hide resolved
packages/ti_eset/data_stream/apt/manifest.yml Outdated Show resolved Hide resolved
packages/ti_eset/manifest.yml Show resolved Hide resolved
@kcreddy
Copy link
Contributor

kcreddy commented Mar 14, 2024

/test

@kcreddy
Copy link
Contributor

kcreddy commented Mar 14, 2024

@polakovicp Looks like the CI is failing on README file. Can you run elastic-package build && elastic-package format && elastic-package lint && elastic-package check && elastic-package build and commit the README files generated.

Also, please let me know when all the review comments are answered, I can take a look again.

@polakovicp
Copy link
Contributor

@polakovicp Looks like the CI is failing on README file. Can you run elastic-package build && elastic-package format && elastic-package lint && elastic-package check && elastic-package build and commit the README files generated.

Also, please let me know when all the review comments are answered, I can take a look again.

@kcreddy thank you for your response. I found problem with paging #9372 and need some assistance :)
I'll update the PR once it's solved.

@polakovicp
Copy link
Contributor

@polakovicp Looks like the CI is failing on README file. Can you run elastic-package build && elastic-package format && elastic-package lint && elastic-package check && elastic-package build and commit the README files generated.

Also, please let me know when all the review comments are answered, I can take a look again.

PR updated. Thanks for #9372, pagination and cursor is now working as expected.
All you comments were addressed, plus did few fixes in apt pipeline.

@kcreddy
Copy link
Contributor

kcreddy commented Mar 27, 2024

/test

Copy link
Contributor

@kcreddy kcreddy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for clearing all of the requested changes.

Looks like the CI is failing on README file changes.
Can you re-run system tests: eval "$(elastic-package stack shellinit)" && elastic-package test system --generate -v followed by elastic-package build && elastic-package format && elastic-package lint && elastic-package check && elastic-package build and commit the generated files?

There are some minimum requirements for running Elastic Agent and for more information,
refer to the link [here](https://www.elastic.co/guide/en/fleet/current/elastic-agent-installation.html).

The minimum **Kibana version** required is **8.12.0**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update manifest.yml accordingly

conditions:
  kibana:
    version: "^8.12.0"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

"actions": {
"delete": {}
},
"min_age": "3d"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"min_age": "3d"
"min_age": "7d"

As per the README doc. Same for other datastreams that have 7d in README doc.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

@polakovicp
Copy link
Contributor

Thanks for clearing all of the requested changes.

Looks like the CI is failing on README file changes. Can you re-run system tests: eval "$(elastic-package stack shellinit)" && elastic-package test system --generate -v followed by elastic-package build && elastic-package format && elastic-package lint && elastic-package check && elastic-package build and commit the generated files?

@kcreddy PR updated.

@kcreddy
Copy link
Contributor

kcreddy commented Mar 27, 2024

/test

@kcreddy
Copy link
Contributor

kcreddy commented Mar 27, 2024

I ran your test locally and it seems to be an issue with pipeline tests.
Can you run eval "$(elastic-package stack shellinit)" && elastic-package test pipeline --generate -v and commit the generated file(s).

@polakovicp
Copy link
Contributor

I ran your test locally and it seems to be an issue with pipeline tests. Can you run eval "$(elastic-package stack shellinit)" && elastic-package test pipeline --generate -v and commit the generated file(s).

Updated

@kcreddy
Copy link
Contributor

kcreddy commented Mar 27, 2024

/test

@elasticmachine
Copy link

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link

💚 Build Succeeded

History

Copy link

Copy link
Contributor

@kcreddy kcreddy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍🏼

@kcreddy kcreddy merged commit bb0d25a into elastic:main Mar 27, 2024
5 checks passed
@elasticmachine
Copy link

Package ti_eset - 0.1.0 containing this change is available at https://epr.elastic.co/search?package=ti_eset

efd6 pushed a commit that referenced this pull request Apr 2, 2024
…es (#9465)

This PR aims to improve compatibility with threat intelligence and other
security integrations, including ESET Threat Intelligence #9255, by
lowercasing the ECS hash fields threat.indicator.file.hash.sha1,
file.hash.sha and related.hash, which is more in line with similar security
integrations. This would enable one to use indicator match rules more easily
as well.

Also fixes a parsing error when object_uri equals script.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants