Threat actor#
A threat actor identifies an adversary who is motivated to damage a targeted victim, usually for personal gain.
A threat actor is an adversary who is motivated to damage an individual, a group, an entity or an organization. Threat actors can be individuals, groups, or organizations; they can be nation-sponsored or nation-state actors; they can be external to the targeted victims, or they can be insider threats. The motivation that drives them ranges from economic, political, ideological, to revenge and bragging. The benefits they gain from attacking a targeted victim vary from financial, to reputation damage, to intellectual property theft, and so on.
You can associate threat actors to TTPs and campaigns to understand how they plan and organize their attacks to the targeted victims. Indicators can help you track them, and relate them to observables and sightings. For example, an email address, an IP address, or a domain name associated with a real person’s identity.
Create a threat actor by selecting:
In the side navigation bar + Create > Threat actor.
Or:
(Requires Beta: Intelligence creation on the graph)
In the top navigation bar of a graph, select + and then Threat actor to create a draft entity.
Double-click to open the newly created draft entity to edit it.
Then, Configure this entity.
Configure#
The following sections the fields and options available.
Note
Required fields are marked with an asterisk (*).
General#
Field |
EIQ JSON field |
Description |
---|---|---|
Name* |
|
Descriptive title for this entity. See Titles and aliases. |
Analysis |
|
Long description. |
Types* |
|
One or more threat actor types. See Threat actor types |
Confidence* |
|
Confidence in the accuracy and trustworthiness of the information contained by this entity. Analogous to ConfidenceType. Possible values from Enumerated values: High Medium low. |
Observables#
You can create one or more new observables and link it to the currently open entity by selecting + Observable under the Observables section.
Note
If an observable you create here matches an observable rule with an ignore action, it does not appear when the you publish the entity.
In the Add observable view that appears, fill out these fields:
Field |
EIQ JSON field |
Description |
---|---|---|
Type* |
|
See Observable types |
Link name* |
||
Values(s)* |
|
Enter one or more values. One observable is created per value. Values must be comma-separated, or newline-separated, but not both. |
Maliciousness* |
Characteristics#
Characteristics are properties on an entity that provide context for the intelligence indicated by this object.
The following are characteristics available for threat actors:
Characteristics: Intent#
Set additional properties for this threat actor. Analogous to multiple properties under the ThreatActorType.
Field |
EIQ JSON field |
Description |
---|---|---|
Motivations |
|
Analogous to MotivationVocab-1.1. |
Sophistication |
|
Analogous to ThreatActorSophisticationVocab-1.0. |
Intended effects |
|
See Intended effects. |
Planning and operational support |
|
Analogous to PlanningAndOperationalSupportVocab-1.0.1. |
Characteristics: Identity#
Identity object to identify this threat actor with. Analogous to IdentityType.
Field |
EIQ JSON field |
Description |
---|---|---|
Name |
|
Name to identify this threat actor with. Creates a |
Specification |
|
Add details to describe this threat actor’s identity. See Identity: Specification. |
Identity: Specification#
Add one or more items to Specification
to flesh out the identity being described.
Content here is used to construct the XML
content in the specification_xml
field in EIQ JSON.
Analogous to
STIXCIQIdentity3.0Type
as used in
IdentityType/
CIQIdentity3.0InstanceType/
CIQ 3.0 Specifications.
Field |
Description |
---|---|
Account |
Describes a bank account or similar. Available fields:
|
Person |
Add one or more properties describing a person.
|
Organization |
Add one or more properties describing an organization.
|
Electronic address |
Add one or more electronic addresses for this targeted victim.
|
Each item added to the Specification section creates an observable with the corresponding type:
Specification field |
Resulting observable type(s) |
---|---|
Account |
|
Person |
|
Organization |
|
Electronic address |
|
Relations#
Add relationships to this entity by selecting + Relationship.
From the drop-down menu select the option corresponding to the relationship you want to create:
After selecting an option, the Search an entity dialog appears. Select one or more entities to relate to the current entity.
Note
You can narrow down the displayed entities by entering a search query, or by using the filter .
Select Select to add the selected entities as relations.
Once a relationship is added to this entity, you can:
Assign MITRE ATT&CK IDs by selecting + under the MITRE ATT&CK IDs column.
Set a Relationship type
Enter a custom relationship type by typing in the empty field and pressing ENTER to save.
Select one of these options:
Indicates malware
Is associated campaign to
I don’t know
Could be anything
Meta#
The Meta section contains configuration options that allow you to attach descriptive data to the entity.
Field |
EIQ JSON field |
Description |
---|---|---|
Estimated threat start time |
|
Estimated start of threat. See Time values. |
Estimated threat end time |
|
Estimated end of threat. See Time values. |
Estimated observed time |
|
Estimated time threat was observed. See Time values. |
Half-life |
|
See Half-life. Select one of these options:
|
Tags |
|
See tags and taxonomies. |
Source* |
|
Select one source. |
Source reliability |
|
See source reliability. Options:
|
Information source#
Field |
EIQ JSON field |
Description |
---|---|---|
Description |
|
Description of information source. |
Identity |
|
Name of this information source |
Roles |
|
One or more information source roles. Possible values:
|
References |
|
One or more URLs. |
Data marking#
Descriptive metadata for entity.
Field |
EIQ JSON field |
Description |
---|---|---|
TLP |
|
Set a TLP color for this entity. |
Terms of use |
|
Free text field allowing you to attach terms of use to an entity. Analogous to TermsOfUseMarkingStructureType. |
Simple |
|
Free text field for attaching any text to an entity. Analogous to SimpleMarkingStructureType. |
Workflow#
Use options here to apply workflow options to this entity.
Field |
Description |
---|---|
Add to dataset |
Select this option to add this entity to one or more datasets on Publish. |
Manually enrich |
Run one or more enrichers on this entity on Publish. |
Save and publish#
Tip
For more information, see Draft and published entities.
Select Publish to create this entity, and make it available under + Create > Production > Published.
For more publishing options, select More and then one of these options:
Publish and new: Publish this entity, and start creating a new entity.
Publish and duplicate: Publish this entity, and start creating a new entity using all the values set for this entity.
Select Save draft to save this entity as a draft, and make it available under + Create > Production > Drafts. You must publish an entity to use it elsewhere on EclecticIQ Intelligence Center.
For more options while saving as a draft, select More and then one of these options:
Publish and new: Save this entity as a draft, and start creating a new entity.
Publish and duplicate: Save this entity as a draft, and start creating a new entity using all the values set for this draft entity.
Appendix#
Threat actor types#
List of possible threat actor types. Analogous to ThreatActorTypeVocab-1.0.
Possible values:
Cyber Espionage Operations
Hacker
Hacker - White hat
Hacker - Gray hat
Hacker - Black hat
Hacktivist
State Actor / Agency
eCrime Actor - Credential Theft Botnet Operator
eCrime Actor - Credential Theft Botnet Service
eCrime Actor - Malware Developer
eCrime Actor - Money Laundering Network
eCrime Actor - Organized Crime Actor
eCrime Actor - Spam Service
eCrime Actor - Traffic Service
eCrime Actor - Underground Call Service
Insider Threat
Disgruntled Customer / User