Cisco Umbrella

Collect logs from Cisco Umbrella with Elastic Agent.


Version	1.22.0 (View all)
Compatible Kibana version(s)	8.12.0 or higher
Supported Serverless project types What's this?	Security Observability
Subscription level What's this?	Basic
Level of support What's this?	Elastic

This integration is for Cisco Umbrella. It includes the following datasets for receiving logs from an AWS S3 bucket using an SQS notification queue and Cisco Managed S3 bucket without SQS:

log dataset: supports Cisco Umbrella logs.

Logs

Umbrella

When using Cisco Managed S3 buckets that does not use SQS there is no load balancing possibilities for multiple agents, a single agent should be configured to poll the S3 bucket for new and updated files, and the number of workers can be configured to scale vertically.

The log dataset collects Cisco Umbrella logs.

An example event for log looks as following:

{
    "@timestamp": "2023-11-03T07:34:39.717Z",
    "agent": {
        "ephemeral_id": "95a13cca-6d60-4c87-bf43-c3e7bbbfaced",
        "id": "acba78ef-1401-4689-977c-d8c2e5d6a8fa",
        "name": "docker-fleet-agent",
        "type": "filebeat",
        "version": "8.10.1"
    },
    "aws": {
        "s3": {
            "bucket": {
                "arn": "arn:aws:s3:::elastic-package-cisco-umbrella-bucket-94360",
                "name": "elastic-package-cisco-umbrella-bucket-94360"
            },
            "object": {
                "key": "new_object_key"
            }
        }
    },
    "cloud": {
        "provider": "",
        "region": "us-east-1"
    },
    "data_stream": {
        "dataset": "cisco_umbrella.log",
        "namespace": "ep",
        "type": "logs"
    },
    "ecs": {
        "version": "8.11.0"
    },
    "elastic_agent": {
        "id": "acba78ef-1401-4689-977c-d8c2e5d6a8fa",
        "snapshot": false,
        "version": "8.10.1"
    },
    "event": {
        "agent_id_status": "verified",
        "category": "network",
        "dataset": "cisco_umbrella.log",
        "ingested": "2023-11-03T07:34:41Z",
        "kind": "event",
        "original": "\"2020-07-23 23:48:56\",\"Elastic Machine\",\"192.168.1.1\",\"67.43.156.12\",\"81.2.69.144\",\"\",\"ALLOWED\",\"https://elastic.co/blog/ext_id=Anyclip\",\"https://google.com/elastic\",\"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.89 Safari/537.36\",\"200\",\"850\",\"\",\"\",\"\",\"Business Services\",\"AVDetectionName\",\"Malicious\",\"MalwareName\",\"\",\"\",\"Roaming Computers\",\"\"",
        "type": [
            "connection"
        ]
    },
    "input": {
        "type": "aws-s3"
    },
    "log": {
        "file": {
            "path": "https://elastic-package-cisco-umbrella-bucket-94360.s3.us-east-1.amazonaws.com/new_object_key"
        },
        "offset": 0
    },
    "observer": {
        "product": "Umbrella",
        "vendor": "Cisco"
    },
    "tags": [
        "preserve_original_event",
        "cisco-umbrella",
        "forwarded"
    ]
}

Exported fields

Field	Description	Type
@timestamp	Date/time when the event originated. This is the date/time extracted from the event, typically representing when the event was generated by the source. If the event source has no original timestamp, this value is typically populated by the first time the event was received by the pipeline. Required field for all events.	date
aws.s3.bucket.arn	The AWS S3 bucket ARN.	keyword
aws.s3.bucket.name	The AWS S3 bucket name.	keyword
aws.s3.object.key	The AWS S3 Object key.	keyword
cisco.umbrella.action	Whether the request was allowed or blocked.	keyword
cisco.umbrella.amp_disposition	The status of the files proxied and scanned by Cisco Advanced Malware Protection (AMP) as part of the Umbrella File Inspection feature; can be Clean, Malicious or Unknown.	keyword
cisco.umbrella.amp_malware_name	If Malicious, the name of the malware according to AMP.	keyword
cisco.umbrella.amp_score	The score of the malware from AMP. This field is not currently used and will be blank.	keyword
cisco.umbrella.audit.after	The policy or setting after the change was made.	keyword
cisco.umbrella.audit.before	The policy or setting before the change was made.	keyword
cisco.umbrella.audit.type	Where the change was made, such as settings or a policy.	keyword
cisco.umbrella.av_detections	The detection name according to the antivirus engine used in file inspection.	keyword
cisco.umbrella.blocked_categories	The categories that resulted in the destination being blocked. Available in version 4 and above.	keyword
cisco.umbrella.categories	The security or content categories that the destination matches.	keyword
cisco.umbrella.certificate_errors	Any certificate or protocol errors in the request.	keyword
cisco.umbrella.classification	The category of attack detected by a rule that is part of a more general type of attack class, such as trojan-activity, attempted-user, and unknown.	keyword
cisco.umbrella.cves	A list of information about security vulnerabilities and exposures.	keyword
cisco.umbrella.data_classification	The data classification whose data identifier matched on the violation.	keyword
cisco.umbrella.data_identifier	The data identifier that matched on the request.	keyword
cisco.umbrella.datacenter	The name of the Umbrella Data Center that processed the user-generated traffic.	keyword
cisco.umbrella.destination_lists_id	The ID number umbrella assigns to a destination list.	keyword
cisco.umbrella.dlp_status	If the request was Blocked for DLP.	keyword
cisco.umbrella.file_action	The action taken on a file in a remote browser isolation session.	keyword
cisco.umbrella.file_label	The file name label that matched on the file properties.	keyword
cisco.umbrella.fqdns	The fully qualified domain names (FQDNs) that match the request.	keyword
cisco.umbrella.gid	Unique ID assigned to the part of the IPS which generated the event.	keyword
cisco.umbrella.identities	An array of the different identities related to the event.	keyword
cisco.umbrella.identity	The identity that made the request. An identity can be a high-level entity within your system (e.g a network) or very granular (e.g a single user)	keyword
cisco.umbrella.identity_types	The type of identity that made the request. For example, Roaming Computer or Network.	keyword
cisco.umbrella.isolate_action	The remote browser isolation state associated with the request.	keyword
cisco.umbrella.message	A brief description of the signature.	keyword
cisco.umbrella.origin_id	The unique identity of the network tunnel.	keyword
cisco.umbrella.policy_identity_type	The first identity type matched with this request. Available in version 3 and above.	keyword
cisco.umbrella.puas	A list of all potentially unwanted application (PUA) results for the proxied file as returned by the antivirus scanner.	keyword
cisco.umbrella.ruleset_id	The ID number assigned to the ruleset by Umbrella.	keyword
cisco.umbrella.severity	The severity level of the rule, such as High, Medium, Low, and Very Low.	keyword
cisco.umbrella.sha_sha256	Hex digest of the response content.	keyword
cisco.umbrella.sid	Used to uniquely identify signatures.	keyword
cisco.umbrella.signature_list_id	Unique ID assigned to a Default or Custom Signature List.	keyword
cisco.umbrella.warn_status	The warn page state associated with the request.	keyword
client.domain	The domain name of the client system. This value may be a host name, a fully qualified domain name, or another host naming format. The value may derive from the original event or be added from enrichment.	keyword
client.registered_domain	The highest registered client domain, stripped of the subdomain. For example, the registered domain for "foo.example.com" is "example.com". This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".	keyword
client.subdomain	The subdomain portion of a fully qualified domain name includes all of the names except the host name under the registered_domain. In a partially qualified domain, or if the the qualification level of the full name cannot be determined, subdomain contains all of the names below the registered domain. For example the subdomain portion of "www.east.mydomain.co.uk" is "east". If the domain has multiple levels of subdomain, such as "sub2.sub1.example.com", the subdomain field should contain "sub2.sub1", with no trailing period.	keyword
client.top_level_domain	The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com". This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".	keyword
cloud.account.id	The cloud account or organization id used to identify different entities in a multi-tenant environment. Examples: AWS account id, Google Cloud ORG Id, or other unique identifier.	keyword
cloud.availability_zone	Availability zone in which this host is running.	keyword
cloud.image.id	Image ID for the cloud instance.	keyword
cloud.instance.id	Instance ID of the host machine.	keyword
cloud.instance.name	Instance name of the host machine.	keyword
cloud.machine.type	Machine type of the host machine.	keyword
cloud.project.id	Name of the project in Google Cloud.	keyword
cloud.provider	Name of the cloud provider. Example values are aws, azure, gcp, or digitalocean.	keyword
cloud.region	Region in which this host is running.	keyword
container.id	Unique container id.	keyword
container.image.name	Name of the image the container was built on.	keyword
container.labels	Image labels.	object
container.name	Container name.	keyword
data_stream.dataset	Data stream dataset.	constant_keyword
data_stream.namespace	Data stream namespace.	constant_keyword
data_stream.type	Data stream type.	constant_keyword
destination.address	Some event destination addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the `.address` field. Then it should be duplicated to `.ip` or `.domain`, depending on which one it is.	keyword
destination.as.number	Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.	long
destination.as.organization.name	Organization name.	keyword
destination.as.organization.name.text	Multi-field of `destination.as.organization.name`.	match_only_text
destination.bytes	Bytes sent from the destination to the source.	long
destination.domain	The domain name of the destination system. This value may be a host name, a fully qualified domain name, or another host naming format. The value may derive from the original event or be added from enrichment.	keyword
destination.geo.city_name	City name.	keyword
destination.geo.continent_name	Name of the continent.	keyword
destination.geo.country_iso_code	Country ISO code.	keyword
destination.geo.country_name	Country name.	keyword
destination.geo.location	Longitude and latitude.	geo_point
destination.geo.region_iso_code	Region ISO code.	keyword
destination.geo.region_name	Region name.	keyword
destination.ip	IP address of the destination (IPv4 or IPv6).	ip
destination.mac	MAC address of the destination. The notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen.	keyword
destination.nat.ip	Translated ip of destination based NAT sessions (e.g. internet to private DMZ) Typically used with load balancers, firewalls, or routers.	ip
destination.nat.port	Port the source session is translated to by NAT Device. Typically used with load balancers, firewalls, or routers.	long
destination.port	Port of the destination.	long
dns.question.name	The name being queried. If the name field contains non-printable characters (below 32 or above 126), those characters should be represented as escaped base 10 integers (\DDD). Back slashes and quotes should be escaped. Tabs, carriage returns, and line feeds should be converted to \t, \r, and \n respectively.	keyword
dns.question.registered_domain	The highest registered domain, stripped of the subdomain. For example, the registered domain for "foo.example.com" is "example.com". This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".	keyword
dns.question.subdomain	The subdomain is all of the labels under the registered_domain. If the domain has multiple levels of subdomain, such as "sub2.sub1.example.com", the subdomain field should contain "sub2.sub1", with no trailing period.	keyword
dns.question.top_level_domain	The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com". This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".	keyword
dns.question.type	The type of record being queried.	keyword
dns.response_code	The DNS response code.	keyword
dns.type	The type of DNS event captured, query or answer. If your source of DNS events only gives you DNS queries, you should only create dns events of type `dns.type:query`. If your source of DNS events gives you answers as well, you should create one event per query (optionally as soon as the query is seen). And a second event containing all query details as well as an array of answers.	keyword
ecs.version	ECS version this event conforms to. `ecs.version` is a required field and must exist in all events. When querying across multiple indices -- which may conform to slightly different ECS versions -- this field lets integrations adjust to the schema version of the events.	keyword
error.message	Error message.	match_only_text
event.action	The action captured by the event. This describes the information in the event. It is more specific than `event.category`. Examples are `group-add`, `process-started`, `file-created`. The value is normally defined by the implementer.	keyword
event.code	Identification code for this event, if one exists. Some event sources use event codes to identify messages unambiguously, regardless of message language or wording adjustments over time. An example of this is the Windows Event ID.	keyword
event.dataset	Event dataset	constant_keyword
event.ingested	Timestamp when an event arrived in the central data store. This is different from `@timestamp`, which is when the event originally occurred. It's also different from `event.created`, which is meant to capture the first time an agent saw the event. In normal conditions, assuming no tampering, the timestamps should chronologically look like this: `@timestamp` < `event.created` < `event.ingested`.	date
event.module	Event module	constant_keyword
event.original	Raw text message of entire event. Used to demonstrate log integrity or where the full log message (before splitting it up in multiple parts) may be required, e.g. for reindex. This field is not indexed and doc_values are disabled. It cannot be searched, but it can be retrieved from `_source`. If users wish to override this and index this field, please see `Field data types` in the `Elasticsearch Reference`.	keyword
event.outcome	This is one of four ECS Categorization Fields, and indicates the lowest level in the ECS category hierarchy. `event.outcome` simply denotes whether the event represents a success or a failure from the perspective of the entity that produced the event. Note that when a single transaction is described in multiple events, each event may populate different values of `event.outcome`, according to their perspective. Also note that in the case of a compound event (a single event that contains multiple logical events), this field should be populated with the value that best captures the overall success or failure from the perspective of the event producer. Further note that not all events will have an associated outcome. For example, this field is generally not populated for metric events, events with `event.type:info`, or any events for which an outcome does not make logical sense.	keyword
event.timezone	This field should be populated when the event's timestamp does not include timezone information already (e.g. default Syslog timestamps). It's optional otherwise. Acceptable timezone formats are: a canonical ID (e.g. "Europe/Amsterdam"), abbreviated (e.g. "EST") or an HH:mm differential (e.g. "-05:00").	keyword
file.hash.sha256	SHA256 hash.	keyword
file.mime_type	MIME type should identify the format of the file or stream of bytes using https://www.iana.org/assignments/media-types/media-types.xhtml\[IANA official types], where possible. When more than one type is applicable, the most specific type should be used.	keyword
file.name	Name of the file including the extension, without the directory.	keyword
file.size	File size in bytes. Only relevant when `file.type` is "file".	long
host.architecture	Operating system architecture.	keyword
host.containerized	If the host is a container.	boolean
host.domain	Name of the domain of which the host is a member. For example, on Windows this could be the host's Active Directory domain or NetBIOS domain name. For Linux this could be the domain of the host's LDAP provider.	keyword
host.hostname	Hostname of the host. It normally contains what the `hostname` command returns on the host machine.	keyword
host.id	Unique host id. As hostname is not always unique, use values that are meaningful in your environment. Example: The current usage of `beat.name`.	keyword
host.ip	Host ip addresses.	ip
host.mac	Host MAC addresses. The notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen.	keyword
host.name	Name of the host. It can contain what hostname returns on Unix systems, the fully qualified domain name (FQDN), or a name specified by the user. The recommended value is the lowercase FQDN of the host.	keyword
host.os.build	OS build information.	keyword
host.os.codename	OS codename, if any.	keyword
host.os.family	OS family (such as redhat, debian, freebsd, windows).	keyword
host.os.kernel	Operating system kernel version as a raw string.	keyword
host.os.name	Operating system name, without the version.	keyword
host.os.name.text	Multi-field of `host.os.name`.	text
host.os.platform	Operating system platform (such centos, ubuntu, windows).	keyword
host.os.version	Operating system version as a raw string.	keyword
host.type	Type of host. For Cloud providers this can be the machine type like `t2.medium`. If vm, this could be the container, for example, or other information meaningful in your environment.	keyword
http.request.bytes	Total size in bytes of the request (body and headers).	long
http.request.method	HTTP request method. The value should retain its casing from the original event. For example, `GET`, `get`, and `GeT` are all considered valid values for this field.	keyword
http.request.mime_type	Mime type of the body of the request. This value must only be populated based on the content of the request body, not on the `Content-Type` header. Comparing the mime type of a request with the request's Content-Type header can be helpful in detecting threats or misconfigured clients.	keyword
http.request.referrer	Referrer for this HTTP request.	keyword
http.response.body.bytes	Size in bytes of the response body.	long
http.response.bytes	Total size in bytes of the response (body and headers).	long
http.response.status_code	HTTP response status code.	long
input.type	Type of Filebeat input.	keyword
log.file.path	Full path to the log file this event came from, including the file name. It should include the drive letter, when appropriate. If the event wasn't read from a log file, do not populate this field.	keyword
log.offset		long
message	For log events the message field contains the log message, optimized for viewing in a log viewer. For structured logs without an original message field, other fields can be concatenated to form a human-readable summary of the event. If multiple messages exist, they can be combined into one message.	match_only_text
network.application	When a specific application or service is identified from network connection details (source/dest IPs, ports, certificates, or wire format), this field captures the application's or service's name. For example, the original event identifies the network connection being from a specific web service in a `https` network connection, like `facebook` or `twitter`. The field value must be normalized to lowercase for querying.	keyword
network.community_id	A hash of source and destination IPs and ports, as well as the protocol used in a communication. This is a tool-agnostic standard to identify flows. Learn more at https://github.com/corelight/community-id-spec.	keyword
network.direction	Direction of the network traffic. When mapping events from a host-based monitoring context, populate this field from the host's point of view, using the values "ingress" or "egress". When mapping events from a network or perimeter-based monitoring context, populate this field from the point of view of the network perimeter, using the values "inbound", "outbound", "internal" or "external". Note that "internal" is not crossing perimeter boundaries, and is meant to describe communication between two hosts within the perimeter. Note also that "external" is meant to describe traffic between two hosts that are external to the perimeter. This could for example be useful for ISPs or VPN service providers.	keyword
network.name	Name given by operators to sections of their network.	keyword
network.protocol	In the OSI Model this would be the Application Layer protocol. For example, `http`, `dns`, or `ssh`. The field value must be normalized to lowercase for querying.	keyword
network.transport	Same as network.iana_number, but instead using the Keyword name of the transport layer (udp, tcp, ipv6-icmp, etc.) The field value must be normalized to lowercase for querying.	keyword
observer.product	The product name of the observer.	keyword
observer.type	The type of the observer the data is coming from. There is no predefined list of observer types. Some examples are `forwarder`, `firewall`, `ids`, `ips`, `proxy`, `poller`, `sensor`, `APM server`.	keyword
observer.vendor	Vendor name of the observer.	keyword
related.hash	All the hashes seen on your event. Populating this field, then using it to search for hashes can help in situations where you're unsure what the hash algorithm is (and therefore which key name to search).	keyword
related.hosts	All hostnames or other host identifiers seen on your event. Example identifiers include FQDNs, domain names, workstation names, or aliases.	keyword
related.ip	All of the IPs seen on your event.	ip
related.user	All the user names or other user identifiers seen on the event.	keyword
rule.id	A rule ID that is unique within the scope of an agent, observer, or other entity using the rule for detection of this event.	keyword
rule.name	The name of the rule or signature generating the event.	keyword
source.address	Some event source addresses are defined ambiguously. The event will sometimes list an IP, a domain or a unix socket. You should always store the raw address in the `.address` field. Then it should be duplicated to `.ip` or `.domain`, depending on which one it is.	keyword
source.as.number	Unique number allocated to the autonomous system. The autonomous system number (ASN) uniquely identifies each network on the Internet.	long
source.as.organization.name	Organization name.	keyword
source.as.organization.name.text	Multi-field of `source.as.organization.name`.	match_only_text
source.bytes	Bytes sent from the source to the destination.	long
source.domain	The domain name of the source system. This value may be a host name, a fully qualified domain name, or another host naming format. The value may derive from the original event or be added from enrichment.	keyword
source.geo.city_name	City name.	keyword
source.geo.continent_name	Name of the continent.	keyword
source.geo.country_iso_code	Country ISO code.	keyword
source.geo.country_name	Country name.	keyword
source.geo.location	Longitude and latitude.	geo_point
source.geo.region_iso_code	Region ISO code.	keyword
source.geo.region_name	Region name.	keyword
source.ip	IP address of the source (IPv4 or IPv6).	ip
source.mac	MAC address of the source. The notation format from RFC 7042 is suggested: Each octet (that is, 8-bit byte) is represented by two [uppercase] hexadecimal digits giving the value of the octet as an unsigned integer. Successive octets are separated by a hyphen.	keyword
source.nat.ip	Translated ip of source based NAT sessions (e.g. internal client to internet) Typically connections traversing load balancers, firewalls, or routers.	ip
source.nat.port	Translated port of source based NAT sessions. (e.g. internal client to internet) Typically used with load balancers, firewalls, or routers.	long
source.port	Port of the source.	long
source.registered_domain	The highest registered source domain, stripped of the subdomain. For example, the registered domain for "foo.example.com" is "example.com". This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last two labels will not work well for TLDs such as "co.uk".	keyword
source.subdomain	The subdomain portion of a fully qualified domain name includes all of the names except the host name under the registered_domain. In a partially qualified domain, or if the the qualification level of the full name cannot be determined, subdomain contains all of the names below the registered domain. For example the subdomain portion of "www.east.mydomain.co.uk" is "east". If the domain has multiple levels of subdomain, such as "sub2.sub1.example.com", the subdomain field should contain "sub2.sub1", with no trailing period.	keyword
source.top_level_domain	The effective top level domain (eTLD), also known as the domain suffix, is the last part of the domain name. For example, the top level domain for example.com is "com". This value can be determined precisely with a list like the public suffix list (http://publicsuffix.org). Trying to approximate this by simply taking the last label will not work well for effective TLDs such as "co.uk".	keyword
tags	List of keywords used to tag each event.	keyword
url.domain	Domain of the url, such as "www.elastic.co". In some cases a URL may refer to an IP and/or port directly, without a domain name. In this case, the IP address would go to the `domain` field. If the URL contains a literal IPv6 address enclosed by `[` and `]` (IETF RFC 2732), the `[` and `]` characters should also be captured in the `domain` field.	keyword
url.extension	The field contains the file extension from the original request url, excluding the leading dot. The file extension is only set if it exists, as not every url has a file extension. The leading period must not be included. For example, the value must be "png", not ".png". Note that when the file name has multiple extensions (example.tar.gz), only the last one should be captured ("gz", not "tar.gz").	keyword
url.full	If full URLs are important to your use case, they should be stored in `url.full`, whether this field is reconstructed or present in the event source.	wildcard
url.full.text	Multi-field of `url.full`.	match_only_text
url.original	Unmodified original url as seen in the event source. Note that in network monitoring, the observed URL may be a full URL, whereas in access logs, the URL is often just represented as a path. This field is meant to represent the URL as it was observed, complete or not.	wildcard
url.original.text	Multi-field of `url.original`.	match_only_text
url.path	Path of the request, such as "/search".	wildcard
url.query	The query field describes the query string of the request, such as "q=elasticsearch". The `?` is excluded from the query string. If a URL contains no `?`, there is no query field. If there is a `?` but no query, the query field exists with an empty string. The `exists` query can be used to differentiate between the two cases.	keyword
url.scheme	Scheme of the request, such as "https". Note: The `:` is not part of the scheme.	keyword
user.domain	Name of the directory the user is a member of. For example, an LDAP or Active Directory domain name.	keyword
user.email	User email address.	keyword
user.full_name	User's full name, if available.	keyword
user.full_name.text	Multi-field of `user.full_name`.	match_only_text
user.id	Unique identifier of the user.	keyword
user.name	Short name or login of the user.	keyword
user.name.text	Multi-field of `user.name`.	match_only_text
user_agent.device.name	Name of the device.	keyword
user_agent.name	Name of the user agent.	keyword
user_agent.original	Unparsed user_agent string.	keyword
user_agent.original.text	Multi-field of `user_agent.original`.	match_only_text
user_agent.os.full	Operating system name, including the version or code name.	keyword
user_agent.os.full.text	Multi-field of `user_agent.os.full`.	match_only_text
user_agent.os.name	Operating system name, without the version.	keyword
user_agent.os.name.text	Multi-field of `user_agent.os.name`.	match_only_text
user_agent.os.version	Operating system version as a raw string.	keyword
user_agent.version	Version of the user agent.	keyword

Changelog

Version	Details	Kibana version(s)
1.22.0	Enhancement View pull request Set sensitive values as secret.	8.12.0 or higher
1.21.2	Enhancement View pull request Changed owners	8.4.0 or higher
1.21.1	Bug fix View pull request Fix handling of intermediate data while processing email identities.	8.4.0 or higher
1.21.0	Enhancement View pull request ECS version updated to 8.11.0.	8.4.0 or higher
1.20.1	Bug fix View pull request Add missing fields from beats input	8.4.0 or higher
1.20.0	Enhancement View pull request Improve 'event.original' check to avoid errors if set.	8.4.0 or higher
1.19.0	Enhancement View pull request ECS version updated to 8.10.0.	8.4.0 or higher
1.18.0	Enhancement View pull request The format_version in the package manifest changed from 2.11.0 to 3.0.0. Removed dotted YAML keys from package manifest. Added 'owner.type: elastic' to package manifest.	8.4.0 or higher
1.17.0	Enhancement View pull request Add tags.yml file so that integration's dashboards and saved searches are tagged with "Security Solution" and displayed in the Security Solution UI.	8.4.0 or higher
1.16.0	Enhancement View pull request Update package to ECS 8.9.0.	8.4.0 or higher
1.15.0	Enhancement View pull request Document duration units.	8.4.0 or higher
1.14.0	Enhancement View pull request Ensure event.kind is correctly set for pipeline errors.	8.4.0 or higher
1.13.0	Enhancement View pull request Update package to ECS 8.8.0.	8.4.0 or higher
1.12.0	Enhancement View pull request Lowercase host.name field	8.4.0 or higher
1.11.1	Bug fix View pull request Handle user identities with extended email values.	8.4.0 or higher
1.11.0	Enhancement View pull request Update package-spec version to 2.7.0.	8.4.0 or higher
1.10.1	Enhancement View pull request Add Mobile Devices as hosts	8.0.0 or higher
1.10.0	Enhancement View pull request Update package to ECS 8.7.0.	8.0.0 or higher
1.9.2	Bug fix View pull request Revert Umbrella S3 multiline.	8.0.0 or higher
1.9.1	Bug fix View pull request Fix indentation.	8.0.0 or higher
1.9.0	Enhancement View pull request Add DLP and intrusion datasets.	8.0.0 or higher
1.8.0	Enhancement View pull request Release Cisco Umbrella datastream as GA.	8.0.0 or higher
1.7.0	Enhancement View pull request Split identity types.	8.0.0 or higher
1.6.2	Enhancement View pull request Add v8 proxy log CSV fields	8.0.0 or higher
1.6.1	Enhancement View pull request Added categories and/or subcategories.	8.0.0 or higher
1.6.0	Enhancement View pull request Update package to ECS 8.6.0.	8.0.0 or higher
1.5.0	Enhancement View pull request Update package to ECS 8.5.0.	8.0.0 or higher
1.4.2	Enhancement View pull request Remove duplicate field.	8.0.0 or higher
1.4.1	Bug fix View pull request Remove hint for cisco managed s3 Bucket List Prefix	8.0.0 or higher
1.4.0	Enhancement View pull request Expose Default Region setting to UI	8.0.0 or higher
1.3.3	Enhancement View pull request Use ECS geo.location definition.	8.0.0 or higher
1.3.2	Bug fix View pull request Fix proxy log CSV fields	8.0.0 or higher
1.3.1	Bug fix View pull request Set default endpoint to empty string	8.0.0 or higher
1.3.0	Enhancement View pull request Update package to ECS 8.4.0	8.0.0 or higher
1.2.2	Bug fix View pull request Fix proxy URL documentation rendering.	8.0.0 or higher
1.2.1	Enhancement View pull request Add missing proxy config to S3 input	8.0.0 or higher
1.2.0	Enhancement View pull request Enrich DNS fields	8.0.0 or higher
1.1.0	Enhancement View pull request Update package to ECS 8.3.0.	8.0.0 or higher
1.0.1	Enhancement View pull request Update to readme. added link to Cisco documentation	8.0.0 or higher
1.0.0	Enhancement View pull request Make GA	8.0.0 or higher
0.7.0	Enhancement View pull request Add Audit Logs	—
0.6.1	Bug fix View pull request Fix use of destination.ip instead of source.nat.ip in DNS logs	—
0.6.0	Enhancement View pull request Update to ECS 8.2	—
0.5.1	Enhancement View pull request Add documentation for multi-fields	—
0.5.0	Enhancement View pull request Update to ECS 8.0	—
0.4.0	Bug fix View pull request Update config to support Cisco Managed S3	—
0.3.2	Bug fix View pull request Regenerate test files using the new GeoIP database	—
0.3.1	Bug fix View pull request Change test public IPs to the supported subset	—
0.3.0	Enhancement View pull request Add 8.0.0 version constraint	—
0.2.2	Enhancement View pull request Update Title and Description.	—
0.2.1	Bug fix View pull request Fix logic that checks for the 'forwarded' tag	—
0.2.0	Enhancement View pull request Update to ECS 1.12.0	—
0.1.0	Enhancement View pull request Initial migration from Filebeat Module	—

On this page

Article navigation

Logs

Umbrella

Changelog