-
Notifications
You must be signed in to change notification settings - Fork 495
Closed
Labels
Category: Integration qualityCategory: Quality used for SI planningCategory: Quality used for SI planningIntegration:ti_abusechabuse.chabuse.chTeam:Sit-CrestCrest developers on the Security Integrations team [elastic/sit-crest-contractors]Crest developers on the Security Integrations team [elastic/sit-crest-contractors]enhancementNew feature or requestNew feature or request
Description
Check and update following areas to improve ECS compatability.
- Required ECS fields should be mapped, the standard list of ECS fields can be found here https://www.elastic.co/guide/en/security/current/siem-field-reference.html
- Review ECS mapping and enrichment
- For threat intel indicators more fields are required for detection rules. More details: https://www.elastic.co/docs/reference/ecs/ecs-threat-usage, https://github.com/elastic/detection-rules/tree/main/rules/threat_intel
event.kind: enrichment
event.category: threat
event.type: indicator
event.module
equalsthreatintel
or matchesti_*
pattern.labels.is_ioc_transform_source: true
in transform's source data andlabels.is_ioc_transform_source: false
in destination.threat.indicator.type
exists- Based on
threat.indicator.type
, presence of other fields, namelythreat.indicator.ip
,hreat.indicator.email.address
,threat.indicator.file.hash or threat.indicator.file.pe.imphash
,threat.indicator.registry.path
, andthreat.indicator.url.full
-
Security > Intelligence
view.- Filter out events containing CEL errors, these are showing up in Intelligence view. Add fail/terminate processors and filter out inside transform
error.message: cel_failure
. - Needs
threat.feed.name
andthreat.feed.dashboard_id
fields to be populated. Last seen
column in the view is currently empty for most indicators. Check ifthreat.indicator.last_seen
can be populated.- When the document inside this view is expanded,
TLP Marking
andConfidence
is empty for all documents. Check if these can be populated.- As per Abusech Threatfox documentation, all indicators are marked as
TLP:WHITE
. threat.indicator.confidence
is only populated inthreatfox
. Inmalware
andurl
, this can be probably derived fromvirustotal.percent
. If the confidence cannot be derived, the default should beNot Specified
as per ECS.
- As per Abusech Threatfox documentation, all indicators are marked as
- Filter out events containing CEL errors, these are showing up in Intelligence view. Add fail/terminate processors and filter out inside transform
- For threat intel indicators more fields are required for detection rules. More details: https://www.elastic.co/docs/reference/ecs/ecs-threat-usage, https://github.com/elastic/detection-rules/tree/main/rules/threat_intel
System tests:
- Combine 2 configs into single config file.
- Ensure all scenarios are covered as documented in ssi: system test coverage for integrations #13453
Metadata
Metadata
Assignees
Labels
Category: Integration qualityCategory: Quality used for SI planningCategory: Quality used for SI planningIntegration:ti_abusechabuse.chabuse.chTeam:Sit-CrestCrest developers on the Security Integrations team [elastic/sit-crest-contractors]Crest developers on the Security Integrations team [elastic/sit-crest-contractors]enhancementNew feature or requestNew feature or request