Incoming feed - Group-IB Brand Abuse Phishing Kit#
Note
This article describes how to configure incoming feeds for a particular feed source. To see how to configure incoming feeds in general, see Create and configure incoming feeds.
Specifications |
|
---|---|
Transport types |
Group-IB Brand Abuse Phishing Kit |
Content type |
GroupIB Phishing Kit BP JSON |
Ingested data |
Ingests the Indicators from Group-IB. |
Endpoint(s) |
|
Processed data |
See Data mapping. |
Requirements#
Email address registered with Group-IB.
Group-IB API key.
Configure the incoming feed#
Create or edit an incoming feed.
Under Transport and content, fill out these fields:
Note
Required fields are marked with an asterisk (*).
Field
Description
Transport type*
Select Group-IB Brand Abuse Phishing Kit from the drop-down menu.
Content type*
Select GroupIB Phishing Kit BP JSON from the drop-down menu.
API URL*
By default, this is set to
https://bt.group-ib.com
.API key*
Set this to your Group-IB API key.
Email*
Set this to the email address associated with your Group-IB account.
SSL verification
Selected by default. Select this option to enable SSL for this feed.
Path to SSL certificate file.
Used when connecting to a feed source that uses a custom CA. Set this as the path to the SSL certificate to use when authenticating the feed source.
For more information, see SSL certificates.
Start ingesting from*
Ingest data from the feed source starting from this date and time. Use the drop-down calendar to select the date and time you want to start ingesting feed data from.
Store your changes by selecting Save.
SSL certificates#
To use an SSL certificate, it must be:
Accessible on the EclecticIQ Intelligence Center host.
Placed in a location that can be accessed by the
eclecticiq
user.Owned by
eclecticiq:eclecticiq
.
To make sure that EclecticIQ Intelligence Center can access the SSL certificate:
Upload the SSL certificate to a location on the EclecticIQ Intelligence Center host.
On the EclecticIQ Intelligence Center host, open the terminal.
Change ownership of the SSL certificate by running as root in the terminal:
chown eclecticiq:eclecticiq /path/to/cert.pem
Where
/path/to/cert.pem
is the location of the SSL certificate EclecticIQ Intelligence Center needs to access.
Data mapping#
The sections below contain non-exhaustive information about how Group-IB Brand Abuse Phishing Kit data is mapped to EclecticIQ Platform entities and observables.
For more information about the Group-IB API schema, see the Group-IB API documentation.
Map to Indicators#
Indicator field name |
Mapped from GroupIB Phishing Kit BP JSON |
Example value |
Description |
---|---|---|---|
Title |
|
adc83b19e793491b1c6ea0fd8b46cd9f32e592fc |
This is the title of the ingested Indicator. |
Analysis |
|
Brand Abuse Phishing Kit Target Brand: Brand name |
Contains information about the phishing kit. |
Types |
|
File Hash Watchlist |
Type of Indicator. |
Confidence |
|
Medium |
|
Tags |
|
Various |
See: |
Producer |
|
Various |
|
Data marking |
|
Various |
See Data marking. |
Map Admiralty Code values#
Group-IB uses the Admiralty System to assign
reliability and credibility values to
a piece of information in the admiraltyCode
field.
For example:
Object A is assigned an
admiraltyCode
value of A1 means that it comes from an information source that is “Completely reliable”, and the piece of information can be “Confirmed by other sources”.Object B that is assigned an
admiraltyCode
value of D6 means that it comes from an information source that is “Not usually reliable”, and the piece of information is evaluated as “Truth cannot be judged”.
When these objects are ingested by EclecticIQ Platform, these values are added as tags to the entities to which the Admiralty System classification applies. For example:
Object A with an
admiraltyCode
value of “A1” produces entities with these two tags attached:Admiralty Code - Completely reliable
Admiralty Code - Confirmed by other sources
Object A with an
admiraltyCode
value of “D6” produces entities with these two tags attachedAdmiralty Code - Not usually reliable
Admiralty Code - Truth cannot be judged
The table below describes how admiraltyCode
values are translated to tags on EclecticIQ Platform:
Group-IB |
EclecticIQ Platform tags |
---|---|
A |
Admiralty Code - Completely reliable |
B |
Admiralty Code - Usually reliable |
C |
Admiralty Code - Fairly reliable |
D |
Admiralty Code - Not usually reliable |
E |
Admiralty Code - Unreliable |
F |
Admiralty Code - Reliability cannot be judged |
1 |
Admiralty Code - Confirmed by other sources |
2 |
Admiralty Code - Probably True |
3 |
Admiralty Code - Possibly True |
4 |
Admiralty Code - Doubtful |
5 |
Admiralty Code - Improbable |
6 |
Admiralty Code - Truth cannot be judged |
Map reliability values to entity Confidence#
Group-IB assigns a reliability
value
to intelligence objects.
When Group-IB intelligence objects
are ingested by EclecticIQ Platform,
reliability
values are used to
set the Confidence of an entity:
Group-IB |
EclecticIQ Platform entity confidence |
---|---|
0–33 |
Low |
34–66 |
Medium |
67–100 |
High |
Producer/Information source#
Field name |
Mapped from GroupIB Phishing Kit BP JSON |
Example value |
Description |
---|---|---|---|
Identity |
|
Group-IB |
Name of organization or person that created the information. Always set to “Group-IB”. |
Roles |
|
Initial Author |
Role of information source. Always set to “Initial Author”. |
References |
|
|
One or more links that lead to source information. |
Data marking#
Field name |
Mapped from GroupIB Phishing Kit BP JSON |
Description |
---|---|---|
TLP |
|
This sets the entity TLP color using values in GroupIB Phishing Kit BP JSON. |
Supported observables#
The following table describes the observable types supported for this feed, and how they’re mapped from GroupIB Phishing Kit BP JSON:
Observable type |
Maliciousness |
Maps from GroupIB Phishing Kit BP JSON |
Related to |
---|---|---|---|
Domain |
See Map severity to observable maliciousness and as entity tag. |
|
Indicator |
Unknown |
|
Indicator |
|
Hash |
See Map severity to observable maliciousness and as entity tag. |
|
Indicator |
Organization |
Safe |
|
Indicator |
URI |
See Map severity to observable maliciousness and as entity tag. |
|
Indicator |
Map severity to observable maliciousness and as entity tag#
Group-IB assigns a severity value to intelligence objects. When that intelligence object is ingested, its severity value is inherited by the entities and observables it produces.
severity
in observables#
When Group-IB intelligence objects are
ingested to produce observables
on the EcleciticIQ Platform,
its severity
value is
used to set the Maliciousness of the observable.
The table below describes how severity
values
are translated to observable maliciousness:
Group-IB |
EclecticIQ Platform observable maliciousness value |
---|---|
|
Malicious (High confidence) |
|
Malicious (Medium confidence) |
|
Malicious (Low confidence) |