- JSON representation
- EmailEvent
- EmailEventType
- ArtifactWithMetadata
- ArtifactInfo
- DomainArtifact
- UrlArtifact
- IpArtifact
- FileArtifact
- LoginEvent
- LoginEventType
- Application
Represents all telemetry data associated with a user for returning to the client.
JSON representation |
---|
{ "event_time": string, "chip": { object ( |
Fields | |
---|---|
event_time |
Date/time of the event. A timestamp in RFC3339 UTC "Zulu" format, with nanosecond resolution and up to nine fractional digits. Examples: |
chip |
The chip to display. |
filter_properties |
A list of filter properties associated the event. |
is_alert |
Whether or not to display this event as an alert. |
event_outcome |
Specifies the result of this event. Whether the event was allowed, blocked, etc. |
summary |
Summary data about the outcome. (e.g. why was the action blocked?) |
raw_logs_token |
A token to request raw logs, this is opaque to the client. If empty, no raw logs can be requested. |
principal_location |
The location of the principal for the user event. On a login event, this is where the login was attempted from. |
description |
Description of cause for a particular event_outcome (udm.security_result.description). |
source_udm_event_info |
The source UDM event info. |
event_number |
Alert number used to identify an alert event. |
Union field event_payload . Event type specific information exists inside this payload. The client will have different display logic for different event types below. event_payload can be only one of the following: |
|
email |
Represents an email event. |
login |
Represents a login event. |
EmailEvent
A general email event that may represent different types of email events.
JSON representation |
---|
{ "type": enum ( |
Fields | |
---|---|
type |
Required. Event type. |
sender |
Sender of the email. Either the sender or recipients field must be populated. |
recipients[] |
Recipients of the email. Either the sender or recipients field must be populated. |
email_subject |
Subject of the email. |
email_id |
Required. GUID of the email as determined by the product providing the logs. |
malicious_artifacts[] |
Required. Artifacts that are considered malicious within an email. |
related_artifacts[] |
Artifacts that aren't considered malicious within an email but are provided for more context. |
acting_asset |
The asset which this event was initiated by. Namely, which asset sent an email or clicked on the url within an email. Often times this will be an external IP. |
EmailEventType
This enum decribes what subtype the email event is.
Enums | |
---|---|
EMAIL_EVENT_TYPE_UNSPECIFIED |
Default |
EMAIL_TRANSACTION |
Represents an event where an email was detected to have mailicious components such as URLs or file hashes. |
EMAIL_URL_CLICK |
Represents an event where a user clicked on a bad URL within an email. Note: In this case, we expect "malicious_artifacts" to be of size 1. |
ArtifactWithMetadata
A distilled version of backstory.SecurityResult representing an artifact which is usually malicious. This is primarily used for UX client consumption. Contains an artifact with associated metadata. Security products may often detect malicious artifacts and provide metadata related to the artifact.
JSON representation |
---|
{
"artifact": {
object ( |
Fields | |
---|---|
artifact |
Field representing the artifact. |
security_category[] |
A standardized (as determined by UDM) security category as determined by the product. |
product_uri |
A URL that a product may provide for more information about the mailicious artifact. |
ArtifactInfo
An Artifact can be a domain, a URL, an ip address, a submission, or a file sha256 id with a list of filenames.
JSON representation |
---|
{ "id": string, // Union field |
Fields | |
---|---|
id |
A VT artifact id. (e.g. a SHA256 of a file or URL that VT uses to identify the file or URL) |
Union field data . Artifact can be one-of the following data types. data can be only one of the following: |
|
domain_artifact |
A domain artifact. |
uri_artifact |
A URL artifact. |
ip_artifact |
An IP artifact. |
file_artifact |
A file artifact. |
DomainArtifact
A domain artifact.
JSON representation |
---|
{ "domain": string } |
Fields | |
---|---|
domain |
Domain name that identifies the artifact. |
UrlArtifact
A URL artifact.
JSON representation |
---|
{ "uri": string } |
Fields | |
---|---|
uri |
URL value that identifies the artifact. |
IpArtifact
An IP artifact.
JSON representation |
---|
{ "ip_address": string, "as_owner": string, "asn": string, "country": string, "ip_subnet_range": string, "registrar": string } |
Fields | |
---|---|
ip_address |
IP address that identifies the artifact. |
as_owner |
AS Owner that this IP Address belongs to. |
asn |
ASN Id that this IP Address belongs to. |
country |
Country code of this IP address. |
ip_subnet_range |
Registered human readable IP subnet range, this IP belongs to. E.g.: 123.59.32.0/19. |
registrar |
The organization that managed allocation of these IP addresses. E.g.: LACNIC |
FileArtifact
A file artifact with all relevant information related to files.
JSON representation |
---|
{ "file_names": [ string ], "sha1": string, "sha256": string, "md5": string } |
Fields | |
---|---|
file_names[] |
List of related file names associated with this artifact. |
sha1 |
Hash information of artifact. Sha1 hash for this file artifact. |
sha256 |
Sha256 hash for this file artifact. |
md5 |
md5 for this file artifact. |
LoginEvent
A general login event that may represent different types of email events.
JSON representation |
---|
{ "login_type": enum ( |
Fields | |
---|---|
login_type |
The type of the login event. |
auth_type[] |
Required. What the login mechanism was: OTP, hardware key, or password. There may be multiple auth types, for example password and hardware key. |
source_asset |
The source asset of this login activity. |
source_user |
The source user of this activity. |
target_asset |
For a MACHINE login, we'd expect to see either target asset or target user or both. For a SSO login, we'd expect to see only a target user. For a VPN login, we'd expect to see target asset which would be the VPN server. |
target_user |
Target user for the login. See previous comment. |
target_application |
A target application is optional. We don't expect it to be present unless the LoginEventType is SSO in which case it is required. |
LoginEventType
Enum representing different types of logins.
Enums | |
---|---|
LOGIN_EVENT_TYPE_UNSPECIFIED |
Default. |
MACHINE |
Represents a user logging into a machine. It may be local or remote. |
SSO |
Represents a user using an SSO product to login, perhaps to access an application. |
VPN |
Represents a user using a VPN server to request an internal IP. |
Application
Often times, users will login to use a particular application/resource. In such cases, the products will provide information on what application the user was attempting to access.
JSON representation |
---|
{ "name": string, "uri": string, "ip": string } |
Fields | |
---|---|
name |
The application/resource name. |
uri |
The url for the application/resource. |
ip |
The ip address for the application/resource. |