Skip to content

Stage 2 changes for RFC 0008 - threat indicator fields #1471

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

Merged
merged 8 commits into from
Jun 29, 2021
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.next.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,7 @@ Thanks, you're awesome :-) -->
* Added `event.agent_id_status` field. #1454
* `threat.enrichments` added to the experimental schema. #1457
* `process.target` and `process.target.parent` added to experimental schema. #1467
* Threat indicator fields progress to beta stage. #1471

#### Improvements

Expand Down
77 changes: 77 additions & 0 deletions code/go/ecs/threat.go

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

274 changes: 274 additions & 0 deletions docs/field-details.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -7726,6 +7726,280 @@ example: `https://attack.mitre.org/groups/G0037/`

// ===============================================================

|
[[field-threat-indicator-confidence]]
<<field-threat-indicator-confidence, threat.indicator.confidence>>

| beta:[ This field is beta and subject to change. ]

Identifies the confidence rating assigned by the provider using STIX confidence scales.

Recommended values:

* Not Specified, None, Low, Medium, High

* 0-10

* Admirality Scale (1-6)

* DNI Scale (5-95)

* WEP Scale (Impossible - Certain)

type: keyword



example: `High`

| extended

// ===============================================================

|
[[field-threat-indicator-description]]
<<field-threat-indicator-description, threat.indicator.description>>

| beta:[ This field is beta and subject to change. ]

Describes the type of action conducted by the threat.

type: keyword



example: `IP x.x.x.x was observed delivering the Angler EK.`

| extended

// ===============================================================

|
[[field-threat-indicator-email-address]]
<<field-threat-indicator-email-address, threat.indicator.email.address>>

| beta:[ This field is beta and subject to change. ]

Identifies a threat indicator as an email address (irrespective of direction).

type: keyword



example: `phish@example.com`

| extended

// ===============================================================

|
[[field-threat-indicator-first-seen]]
<<field-threat-indicator-first-seen, threat.indicator.first_seen>>

| beta:[ This field is beta and subject to change. ]

The date and time when intelligence source first reported sighting this indicator.

type: date



example: `2020-11-05T17:25:47.000Z`

| extended

// ===============================================================

|
[[field-threat-indicator-ip]]
<<field-threat-indicator-ip, threat.indicator.ip>>

| beta:[ This field is beta and subject to change. ]

Identifies a threat indicator as an IP address (irrespective of direction).

type: ip



example: `1.2.3.4`

| extended

// ===============================================================

|
[[field-threat-indicator-last-seen]]
<<field-threat-indicator-last-seen, threat.indicator.last_seen>>

| beta:[ This field is beta and subject to change. ]

The date and time when intelligence source last reported sighting this indicator.

type: date



example: `2020-11-05T17:25:47.000Z`

| extended

// ===============================================================

|
[[field-threat-indicator-marking-tlp]]
<<field-threat-indicator-marking-tlp, threat.indicator.marking.tlp>>

| beta:[ This field is beta and subject to change. ]

Traffic Light Protocol sharing markings.

Recommended values are:

* WHITE

* GREEN

* AMBER

* RED

type: keyword



example: `WHITE`

| extended

// ===============================================================

|
[[field-threat-indicator-modified-at]]
<<field-threat-indicator-modified-at, threat.indicator.modified_at>>

| beta:[ This field is beta and subject to change. ]

The date and time when intelligence source last modified information for this indicator.

type: date



example: `2020-11-05T17:25:47.000Z`

| extended

// ===============================================================

|
[[field-threat-indicator-port]]
<<field-threat-indicator-port, threat.indicator.port>>

| beta:[ This field is beta and subject to change. ]

Identifies a threat indicator as a port number (irrespective of direction).

type: long



example: `443`

| extended

// ===============================================================

|
[[field-threat-indicator-scanner-stats]]
<<field-threat-indicator-scanner-stats, threat.indicator.scanner_stats>>

| beta:[ This field is beta and subject to change. ]

Count of AV/EDR vendors that successfully detected malicious file or URL.

type: long



example: `4`

| extended

// ===============================================================

|
[[field-threat-indicator-sightings]]
<<field-threat-indicator-sightings, threat.indicator.sightings>>

| beta:[ This field is beta and subject to change. ]

Number of times this indicator was observed conducting threat activity.

type: long



example: `20`

| extended

// ===============================================================

|
[[field-threat-indicator-type]]
<<field-threat-indicator-type, threat.indicator.type>>

| beta:[ This field is beta and subject to change. ]

Type of indicator as represented by Cyber Observable in STIX 2.0.

Recommended values:

* autonomous-system

* artifact

* directory

* domain-name

* email-addr

* file

* ipv4-addr

* ipv6-addr

* mac-addr

* mutex

* port

* process

* software

* url

* user-account

* windows-registry-key

* x509-certificate

type: keyword



example: `ipv4-addr`

| extended

// ===============================================================

|
[[field-threat-software-id]]
<<field-threat-software-id, threat.software.id>>
Expand Down
Loading