You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/ti_abusech/_dev/build/docs/README.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,7 +101,6 @@ For more details, check the abuse.ch [Community First - New Authentication](http
101
101
2. In **Search field names**, search and add fields `error.message` and `data_stream.dataset` into the **Discover** view. For more details on adding fields inside **Discover**, check [Discover getting started](https://www.elastic.co/docs/explore-analyze/discover/discover-get-started).
102
102
3. Search for the dataset(s) that are enabled by this integration. For example, in the KQL query bar, use the KQL query `data_stream.dataset: ti_abusech.url` to search on specific dataset or KQL query `data_stream.dataset: ti_abusech.*` to search on all datasets.
103
103
4. Search for presence of any errors that are captured into `error.message` field using KQL query `error.message: *`. You can combine queries using [KQL boolean expressions](https://www.elastic.co/docs/explore-analyze/query-filter/languages/kql#_combining_multiple_queries), such as `AND`. For example, to search for any errors inside `url` dataset, you can use KQL query: `data_stream.dataset: ti_abusech.url AND error.message: *`.
104
-
105
104
- Since this integration supports Expiration of Indicators of Compromise (IOCs) using Elastic latest transform, the indicators are present in both source and destination indices. While this seem like duplicate ingestion, it is an implmentation detail which is required to properly expire indicators.
106
105
- Because the latest copy of indicators is now indexed in two places, that is, in both source and destination indices, users must anticipate storage requirements accordingly. The ILM policies on source indices can be tuned to manage their data retention period. For more details, check the [Reference](#ilm-policy).
107
106
- For help with Elastic ingest tools, check [Common problems](https://www.elastic.co/docs/troubleshoot/ingest/fleet/common-problems).
@@ -114,24 +113,24 @@ For more information on architectures that can be used for scaling this integrat
@@ -101,7 +101,6 @@ For more details, check the abuse.ch [Community First - New Authentication](http
101
101
2. In **Search field names**, search and add fields `error.message` and `data_stream.dataset` into the **Discover** view. For more details on adding fields inside **Discover**, check [Discover getting started](https://www.elastic.co/docs/explore-analyze/discover/discover-get-started).
102
102
3. Search for the dataset(s) that are enabled by this integration. For example, in the KQL query bar, use the KQL query `data_stream.dataset: ti_abusech.url` to search on specific dataset or KQL query `data_stream.dataset: ti_abusech.*` to search on all datasets.
103
103
4. Search for presence of any errors that are captured into `error.message` field using KQL query `error.message: *`. You can combine queries using [KQL boolean expressions](https://www.elastic.co/docs/explore-analyze/query-filter/languages/kql#_combining_multiple_queries), such as `AND`. For example, to search for any errors inside `url` dataset, you can use KQL query: `data_stream.dataset: ti_abusech.url AND error.message: *`.
104
-
105
104
- Since this integration supports Expiration of Indicators of Compromise (IOCs) using Elastic latest transform, the indicators are present in both source and destination indices. While this seem like duplicate ingestion, it is an implmentation detail which is required to properly expire indicators.
106
105
- Because the latest copy of indicators is now indexed in two places, that is, in both source and destination indices, users must anticipate storage requirements accordingly. The ILM policies on source indices can be tuned to manage their data retention period. For more details, check the [Reference](#ilm-policy).
107
106
- For help with Elastic ingest tools, check [Common problems](https://www.elastic.co/docs/troubleshoot/ingest/fleet/common-problems).
@@ -114,43 +113,6 @@ For more information on architectures that can be used for scaling this integrat
114
113
115
114
### ECS field reference
116
115
117
-
**Exported fields**
118
-
119
-
| Field | Description | Type |
120
-
|---|---|---|
121
-
|@timestamp| Event timestamp. | date |
122
-
| abusech.url.blacklists.spamhaus_dbl | If the indicator is listed on the spamhaus blacklist. | keyword |
123
-
| abusech.url.blacklists.surbl | If the indicator is listed on the surbl blacklist. | keyword |
124
-
| abusech.url.deleted_at | The timestamp when the indicator is (will be) deleted. | date |
125
-
| abusech.url.id | The ID of the indicator. | keyword |
126
-
| abusech.url.larted | Indicates whether the malware URL has been reported to the hosting provider (true or false). | boolean |
127
-
| abusech.url.last_online | Last timestamp when the URL has been serving malware. | date |
128
-
| abusech.url.reporter | The Twitter handle of the reporter that has reported this malware URL (or anonymous). | keyword |
129
-
| abusech.url.tags | A list of tags associated with the queried malware URL. | keyword |
130
-
| abusech.url.threat | The threat corresponding to this malware URL. | keyword |
131
-
| abusech.url.url_status | The current status of the URL. Possible values are: online, offline and unknown. | keyword |
132
-
| abusech.url.urlhaus_reference | Link to URLhaus entry. | keyword |
133
-
| cloud.image.id | Image ID for the cloud instance. | keyword |
134
-
| data_stream.dataset | Data stream dataset name. | constant_keyword |
135
-
| data_stream.namespace | Data stream namespace. | constant_keyword |
136
-
| data_stream.type | Data stream type. | constant_keyword |
0 commit comments