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

[ti_crowdstrike] Add Mapping of Hash Sha1 type Indicator #9270

Merged
merged 3 commits into from Mar 5, 2024

Conversation

mohitjha-elastic
Copy link
Contributor

@mohitjha-elastic mohitjha-elastic commented Mar 5, 2024

Type of change

  • Enhancement

What does this PR do?

1. Add the mapping of hash sha1 type indicator.
As per the API Documentation, Hash Sha1 type indicator is not mentioned in the Intel Responses but the customer are getting those in the live responses (mentioned in SDH Issue) hence adding the support for that.

2. Add the offset in the config in case of unsuccessful requests.

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.

All changes

  • Change follows the contributing guidelines
  • Supported versions of the monitoring target are documented
  • Supported operating systems are documented (if applicable)
  • Integration or System tests exist
  • Documentation exists
  • Fields follow ECS and naming conventions
  • At least a manual test with ES / Kibana / Agent has been performed.
  • Required Kibana version set to: ^8.12.0

How to test this PR locally

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

Related issues

Automated Test

test_ti_crowdstrike-0.5.1.txt

Add offset in the config in case of unsuccessful requests.
Add test data related to the hash sha1 type indicator in pipeline test.
@mohitjha-elastic mohitjha-elastic requested a review from a team as a code owner March 5, 2024 12:05
@elasticmachine
Copy link

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

Change the secret to false for token url.
@kcreddy
Copy link
Contributor

kcreddy commented Mar 5, 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.

LGTM

@elasticmachine
Copy link

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link

💚 Build Succeeded

Copy link

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

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

1 similar comment
@elasticmachine
Copy link

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

gizas pushed a commit that referenced this pull request Mar 13, 2024
* Add the mapping of hash sha1 type indicator. As per the API Documentation, Hash Sha1 type indicator is not mentioned in the Intel Responses but the users are getting those in the live responses hence adding the support for that.

* Add the offset in the config in case of unsuccessful requests.
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.

CrowdStrike Falcon Intelligence 0.4.1 Pipeline not Parsing SHA1 Intel and Resolve offset issue.
3 participants