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

[CrowdStrike Falcon Intelligence]: IOC enrichment failed for custom IOCs except IP #11688

Open
sitharhlaing opened this issue Nov 11, 2024 · 3 comments · May be fixed by #11703
Open

[CrowdStrike Falcon Intelligence]: IOC enrichment failed for custom IOCs except IP #11688

sitharhlaing opened this issue Nov 11, 2024 · 3 comments · May be fixed by #11703
Assignees
Labels
Integration:crowdstrike CrowdStrike needs:triage Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations]

Comments

@sitharhlaing
Copy link

Integration Name

CrowdStrike [crowdstrike]

Dataset Name

ti_crowdstrike.ioc

Integration Version

v1.1.7

Agent Version

8.13.3

Agent Output Type

elasticsearch

Elasticsearch Version

8.13.3

OS Version and Architecture

Oracle Linux Server 9.4

Software/API Version

No response

Error Message

Ignored value (The value in this field is malformed and can't be searched or filtered) --

Event Original

{"action":"no_action","applied_globally":false,"created_by":"[email protected]","created_on":"2024-11-11T09:17:03.445826361Z","deleted":false,"description":"Test hash IOC","expired":false,"from_parent":false,"host_groups":["my_host_group"],"id":"a3redactedredactedredactedredactedredactedef21","metadata":{},"modified_by":"[email protected]","modified_on":"2024-11-11T09:17:03.445826361Z","platforms":["windows"],"severity":"medium","type":"md5","value":"65efdcbd4bc64e6e48d82bfa31f710fd"}

What did you do?

I added custom IOCs of different types (hashes, domains, IPs) in crowdstrike portal
Image

What did you see?

In kibana, I found the IOC values are just enriched to IPs regardless of the original type which caused this issue if the IOC type is not IP address
Image

Just IP address IOC types are enriched as intended.
Image

What did you expect to see?

All the IOC types should enriched as intended.

Anything else?

To search, filter and correlate with ti_crowdstrike.ioc.value field, we need that field to be well enriched regardless of the IOC type.

@andrewkroh andrewkroh added Integration:crowdstrike CrowdStrike Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations] labels Nov 11, 2024
@elasticmachine
Copy link

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

@efd6 efd6 self-assigned this Nov 11, 2024
@efd6 efd6 linked a pull request Nov 11, 2024 that will close this issue
5 tasks
@efd6
Copy link
Contributor

efd6 commented Nov 11, 2024

@sitharhlaing Thank you for reporting this. I have sent a change. Unfortunately, this will require that you re-index to pick up the fix.

@kcreddy
Copy link
Contributor

kcreddy commented Nov 14, 2024

We also have ECS field threat.indicator.name of type keyword which should have a copy of the value from ti_crowdstrike.ioc.value as per ingest pipeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Integration:crowdstrike CrowdStrike needs:triage Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations]
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants