1Password
Collect logs from 1Password with Elastic Agent.
Version |
1.27.0 (View all) |
Compatible Kibana version(s) |
8.12.0 or higher |
Supported Serverless project types |
Security Observability |
Subscription level |
Basic |
Level of support |
Partner |
With 1Password Business, you can send your account activity to your security information and event management (SIEM) system, using the 1Password Events API.
Get reports about 1Password activity, such as sign-in attempts and item usage, while you manage all your company’s applications and services from a central location.
With 1Password Events Reporting and Elastic SIEM, you can:
- Control your 1Password data retention
- Build custom graphs and dashboards
- Set up custom alerts that trigger specific actions
- Cross-reference 1Password events with the data from other services
You can set up Events Reporting if you’re an owner or administrator.
Ready to get started? Learn how to set up the Elastic Events Reporting integration.
Events
Sign-in Attempts
Use the 1Password Events API to retrieve information about sign-in attempts. Events include the name and IP address of the user who attempted to sign in to the account, when the attempt was made, and – for failed attempts – the cause of the failure.
Exported fields
Exported fields
Field | Description | Type |
---|---|---|
@timestamp | Event timestamp. | date |
data_stream.dataset | Data stream dataset. | constant_keyword |
data_stream.namespace | Data stream namespace. | constant_keyword |
data_stream.type | Data stream type. | constant_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 |
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.category | This is one of four ECS Categorization Fields, and indicates the second level in the ECS category hierarchy. event.category represents the "big buckets" of ECS categories. For example, filtering on event.category:process yields all events relating to process activity. This field is closely related to event.type , which is used as a subcategory. This field is an array. This will allow proper categorization of some events that fall in multiple categories. | keyword |
event.created | event.created contains the date/time when the event was first read by an agent, or by your pipeline. This field is distinct from @timestamp in that @timestamp typically contain the time extracted from the original event. In most situations, these two timestamps will be slightly different. The difference can be used to calculate the delay between your source generating an event, and the time when your agent first processed it. This can be used to monitor your agent's or pipeline's ability to keep up with your event source. In case the two timestamps are identical, @timestamp should be used. | date |
event.dataset | Event dataset | constant_keyword |
event.kind | This is one of four ECS Categorization Fields, and indicates the highest level in the ECS category hierarchy. event.kind gives high-level information about what type of information the event contains, without being specific to the contents of the event. For example, values of this field distinguish alert events from metric events. The value of this field can be used to inform how these kinds of events should be handled. They may warrant different retention, different access control, it may also help understand whether the data is coming in at a regular interval or not. | keyword |
event.module | Event module | constant_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.type | This is one of four ECS Categorization Fields, and indicates the third level in the ECS category hierarchy. event.type represents a categorization "sub-bucket" that, when used along with the event.category field values, enables filtering events down to a level appropriate for single visualization. This field is an array. This will allow proper categorization of some events that fall in multiple event types. | keyword |
host.os.name | Operating system name, without the version. | keyword |
host.os.name.text | Multi-field of host.os.name . | match_only_text |
host.os.version | Operating system version as a raw string. | keyword |
input.type | Input type | keyword |
onepassword.client.app_name | The name of the 1Password app that attempted to sign in to the account | keyword |
onepassword.client.app_version | The version number of the 1Password app | keyword |
onepassword.client.platform_name | The name of the platform running the 1Password app | keyword |
onepassword.client.platform_version | The version of the browser or computer where the 1Password app is installed, or the CPU of the machine where the 1Password command-line tool is installed | keyword |
onepassword.country | The country code of the event. Uses the ISO 3166 standard | keyword |
onepassword.details.value | keyword | |
onepassword.session_uuid | The UUID of the session that created the event | keyword |
onepassword.type | Details about the sign-in attempt | keyword |
onepassword.uuid | The UUID of the event | 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 |
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.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 |
tags | List of keywords used to tag each event. | 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 |
An example event for signin_attempts
looks as following:
{
"@timestamp": "2021-08-11T14:28:03.000Z",
"agent": {
"ephemeral_id": "1e0fc736-84ed-49e4-883f-0e760641aafc",
"id": "f25d13cd-18cc-4e73-822c-c4f849322623",
"name": "docker-fleet-agent",
"type": "filebeat",
"version": "8.10.1"
},
"data_stream": {
"dataset": "1password.signin_attempts",
"namespace": "ep",
"type": "logs"
},
"ecs": {
"version": "8.11.0"
},
"elastic_agent": {
"id": "f25d13cd-18cc-4e73-822c-c4f849322623",
"snapshot": false,
"version": "8.10.1"
},
"event": {
"action": "success",
"agent_id_status": "verified",
"category": [
"authentication"
],
"created": "2023-09-25T15:46:05.478Z",
"dataset": "1password.signin_attempts",
"ingested": "2023-09-25T15:46:08Z",
"kind": "event",
"outcome": "success",
"type": [
"info"
]
},
"host": {
"os": {
"name": "Android",
"version": "10"
}
},
"input": {
"type": "httpjson"
},
"onepassword": {
"client": {
"app_name": "1Password Browser Extension",
"app_version": "1109",
"platform_name": "Chrome",
"platform_version": "93.0.4577.62"
},
"country": "AR",
"session_uuid": "UED4KFZ5BH37IQWTJ7LG4VPWK7",
"type": "credentials_ok",
"uuid": "HGIF4OEWXDTVWKEQDIWTKV26HU"
},
"related": {
"ip": [
"1.1.1.1"
],
"user": [
"OJQGU46KAPROEJLCK674RHSAY5",
"email@1password.com",
"Name"
]
},
"source": {
"ip": "1.1.1.1"
},
"tags": [
"forwarded",
"1password-signin_attempts"
],
"user": {
"email": "email@1password.com",
"full_name": "Name",
"id": "OJQGU46KAPROEJLCK674RHSAY5"
}
}
Item Usages
This uses the 1Password Events API to retrieve information about items in shared vaults that have been modified, accessed, or used. Events include the name and IP address of the user who accessed the item, when it was accessed, and the vault where the item is stored.
Exported fields
Exported fields
Field | Description | Type |
---|---|---|
@timestamp | Event timestamp. | date |
data_stream.dataset | Data stream dataset. | constant_keyword |
data_stream.namespace | Data stream namespace. | constant_keyword |
data_stream.type | Data stream type. | constant_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 |
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.category | This is one of four ECS Categorization Fields, and indicates the second level in the ECS category hierarchy. event.category represents the "big buckets" of ECS categories. For example, filtering on event.category:process yields all events relating to process activity. This field is closely related to event.type , which is used as a subcategory. This field is an array. This will allow proper categorization of some events that fall in multiple categories. | keyword |
event.created | event.created contains the date/time when the event was first read by an agent, or by your pipeline. This field is distinct from @timestamp in that @timestamp typically contain the time extracted from the original event. In most situations, these two timestamps will be slightly different. The difference can be used to calculate the delay between your source generating an event, and the time when your agent first processed it. This can be used to monitor your agent's or pipeline's ability to keep up with your event source. In case the two timestamps are identical, @timestamp should be used. | date |
event.dataset | Event dataset | constant_keyword |
event.kind | This is one of four ECS Categorization Fields, and indicates the highest level in the ECS category hierarchy. event.kind gives high-level information about what type of information the event contains, without being specific to the contents of the event. For example, values of this field distinguish alert events from metric events. The value of this field can be used to inform how these kinds of events should be handled. They may warrant different retention, different access control, it may also help understand whether the data is coming in at a regular interval or not. | keyword |
event.module | Event module | constant_keyword |
event.type | This is one of four ECS Categorization Fields, and indicates the third level in the ECS category hierarchy. event.type represents a categorization "sub-bucket" that, when used along with the event.category field values, enables filtering events down to a level appropriate for single visualization. This field is an array. This will allow proper categorization of some events that fall in multiple event types. | keyword |
host.os.name | Operating system name, without the version. | keyword |
host.os.name.text | Multi-field of host.os.name . | match_only_text |
host.os.version | Operating system version as a raw string. | keyword |
input.type | Input type | keyword |
onepassword.client.app_name | The name of the 1Password app the item was accessed from | keyword |
onepassword.client.app_version | The version number of the 1Password app | keyword |
onepassword.client.platform_name | The name of the platform the item was accessed from | keyword |
onepassword.client.platform_version | The version of the browser or computer where the 1Password app is installed, or the CPU of the machine where the 1Password command-line tool is installed | keyword |
onepassword.item_uuid | The UUID of the item that was accessed | keyword |
onepassword.used_version | The version of the item that was accessed | integer |
onepassword.uuid | The UUID of the event | keyword |
onepassword.vault_uuid | The UUID of the vault the item is in | 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 |
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.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 |
tags | List of keywords used to tag each event. | 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 |
An example event for item_usages
looks as following:
{
"@timestamp": "2021-08-30T18:57:42.484Z",
"agent": {
"ephemeral_id": "b62ebce2-8912-45ae-ab78-ca49158aae5f",
"id": "f25d13cd-18cc-4e73-822c-c4f849322623",
"name": "docker-fleet-agent",
"type": "filebeat",
"version": "8.10.1"
},
"data_stream": {
"dataset": "1password.item_usages",
"namespace": "ep",
"type": "logs"
},
"ecs": {
"version": "8.11.0"
},
"elastic_agent": {
"id": "f25d13cd-18cc-4e73-822c-c4f849322623",
"snapshot": false,
"version": "8.10.1"
},
"event": {
"action": "reveal",
"agent_id_status": "verified",
"category": [
"file"
],
"created": "2023-09-25T15:44:58.422Z",
"dataset": "1password.item_usages",
"ingested": "2023-09-25T15:45:01Z",
"kind": "event",
"type": [
"access"
]
},
"host": {
"os": {
"name": "Android",
"version": "10"
}
},
"input": {
"type": "httpjson"
},
"onepassword": {
"client": {
"app_name": "1Password Browser Extension",
"app_version": "1109",
"platform_name": "Chrome",
"platform_version": "93.0.4577.62"
},
"item_uuid": "bvwmmwxisuca7wbehrbyqhag54",
"used_version": 1,
"uuid": "MCQODBBWJD5HISKYNP3HJPV2DV",
"vault_uuid": "jaqxqf5qylslqiitnduawrndc5"
},
"related": {
"ip": [
"1.1.1.1"
],
"user": [
"OJQGU46KAPROEJLCK674RHSAY5",
"email@1password.com",
"Name"
]
},
"source": {
"ip": "1.1.1.1"
},
"tags": [
"forwarded",
"1password-item_usages"
],
"user": {
"email": "email@1password.com",
"full_name": "Name",
"id": "OJQGU46KAPROEJLCK674RHSAY5"
}
}
Audit Events
This uses the 1Password Events API to retrieve information about audit events. Events includes information about actions performed by team members such as account updates, access and invitations, device authorization, changes to vault permissions, and more.
Exported fields
Exported fields
Field | Description | Type |
---|---|---|
@timestamp | Event timestamp. | date |
data_stream.dataset | Data stream dataset. | constant_keyword |
data_stream.namespace | Data stream namespace. | constant_keyword |
data_stream.type | Data stream type. | constant_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 |
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.category | This is one of four ECS Categorization Fields, and indicates the second level in the ECS category hierarchy. event.category represents the "big buckets" of ECS categories. For example, filtering on event.category:process yields all events relating to process activity. This field is closely related to event.type , which is used as a subcategory. This field is an array. This will allow proper categorization of some events that fall in multiple categories. | keyword |
event.created | event.created contains the date/time when the event was first read by an agent, or by your pipeline. This field is distinct from @timestamp in that @timestamp typically contain the time extracted from the original event. In most situations, these two timestamps will be slightly different. The difference can be used to calculate the delay between your source generating an event, and the time when your agent first processed it. This can be used to monitor your agent's or pipeline's ability to keep up with your event source. In case the two timestamps are identical, @timestamp should be used. | date |
event.dataset | Event dataset | constant_keyword |
event.kind | This is one of four ECS Categorization Fields, and indicates the highest level in the ECS category hierarchy. event.kind gives high-level information about what type of information the event contains, without being specific to the contents of the event. For example, values of this field distinguish alert events from metric events. The value of this field can be used to inform how these kinds of events should be handled. They may warrant different retention, different access control, it may also help understand whether the data is coming in at a regular interval or not. | keyword |
event.module | Event module | constant_keyword |
event.type | This is one of four ECS Categorization Fields, and indicates the third level in the ECS category hierarchy. event.type represents a categorization "sub-bucket" that, when used along with the event.category field values, enables filtering events down to a level appropriate for single visualization. This field is an array. This will allow proper categorization of some events that fall in multiple event types. | keyword |
input.type | Input type | keyword |
onepassword.actor_details.email | The email of the actor. | keyword |
onepassword.actor_details.name | The name of the actor. | keyword |
onepassword.actor_details.uuid | The UUID of the actor. | keyword |
onepassword.actor_uuid | The UUID of the actor. | keyword |
onepassword.aux_details.email | The email of the aux resource. | keyword |
onepassword.aux_details.name | The name of the aux resource. | keyword |
onepassword.aux_details.uuid | The UUID of the aux resource. | keyword |
onepassword.aux_id | Any auxilary id related to the event. | long |
onepassword.aux_info | Any auxilary info related to the event. | text |
onepassword.aux_uuid | Any auxilary uuid related to the event. | keyword |
onepassword.object_details.email | The email of the object. | keyword |
onepassword.object_details.name | The name of the object. | keyword |
onepassword.object_details.uuid | The UUID of the object. | keyword |
onepassword.object_type | The type of object changed by the event. | keyword |
onepassword.object_uuid | The UUID of the object changed by the event. | keyword |
onepassword.session.device_uuid | The device uuid of the session used to create the event. | keyword |
onepassword.session.login_time | The login time of the session used to create the event. | date |
onepassword.session.uuid | The session uuid of the session used to create the event. | keyword |
onepassword.uuid | The UUID of the event. | 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 |
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.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 |
tags | List of keywords used to tag each event. | keyword |
user.email | User email address. | keyword |
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 |
An example event for audit_events
looks as following:
{
"@timestamp": "2022-10-24T21:16:52.827Z",
"agent": {
"ephemeral_id": "689182ac-608d-4aed-bb28-bef2dc682f45",
"id": "f25d13cd-18cc-4e73-822c-c4f849322623",
"name": "docker-fleet-agent",
"type": "filebeat",
"version": "8.10.1"
},
"data_stream": {
"dataset": "1password.audit_events",
"namespace": "ep",
"type": "logs"
},
"ecs": {
"version": "8.11.0"
},
"elastic_agent": {
"id": "f25d13cd-18cc-4e73-822c-c4f849322623",
"snapshot": false,
"version": "8.10.1"
},
"event": {
"action": "suspend",
"agent_id_status": "verified",
"category": [
"configuration"
],
"created": "2023-09-25T15:43:52.446Z",
"dataset": "1password.audit_events",
"ingested": "2023-09-25T15:43:55Z",
"kind": "event",
"type": [
"access"
]
},
"input": {
"type": "httpjson"
},
"onepassword": {
"object_type": "user",
"object_uuid": "ZRQCUD6A65AKHFETOUFO7NL4OM",
"session": {
"device_uuid": "rqtd557fn2husnstp5nc66w2xa",
"login_time": "2022-10-24T21:07:34.703106271Z",
"uuid": "ODOHXUYQCJBUJKRGZNNPBJURPE"
},
"uuid": "3UQOGUC7DVOCN4OZP2MDKHFLSG"
},
"related": {
"ip": [
"89.160.20.156"
],
"user": [
"GLF6WUEKS5CSNDJ2OG6TCZD3M4",
"ZRQCUD6A65AKHFETOUFO7NL4OM"
]
},
"source": {
"as": {
"number": 29518,
"organization": {
"name": "Bredband2 AB"
}
},
"geo": {
"city_name": "Linköping",
"continent_name": "Europe",
"country_iso_code": "SE",
"country_name": "Sweden",
"location": {
"lat": 58.4167,
"lon": 15.6167
},
"region_iso_code": "SE-E",
"region_name": "Östergötland County"
},
"ip": "89.160.20.156"
},
"tags": [
"forwarded",
"1password-audit_events"
],
"user": {
"id": "GLF6WUEKS5CSNDJ2OG6TCZD3M4"
}
}
Changelog
Version | Details | Kibana version(s) |
---|---|---|
1.27.0 | Enhancement View pull request | 8.12.0 or higher |
1.26.1 | Enhancement View pull request | 8.7.1 or higher |
1.26.0 | Enhancement View pull request | 8.7.1 or higher |
1.25.0 | Enhancement View pull request | 8.7.1 or higher |
1.24.0 | Enhancement View pull request | 8.7.1 or higher |
1.23.1 | Bug fix View pull request | 8.7.1 or higher |
1.23.0 | Enhancement View pull request | 8.7.1 or higher |
1.22.0 | Enhancement View pull request | 8.7.1 or higher |
1.21.0 | Bug fix View pull request | 8.7.1 or higher |
1.20.0 | Enhancement View pull request | 8.7.1 or higher |
1.19.0 | Enhancement View pull request | 8.7.1 or higher |
1.18.0 | Enhancement View pull request | 8.7.1 or higher |
1.17.0 | Enhancement View pull request | 8.7.1 or higher |
1.16.0 | Enhancement View pull request | 8.7.1 or higher |
1.15.0 | Enhancement View pull request | 8.7.1 or higher |
1.14.0 | Enhancement View pull request | 8.7.1 or higher |
1.13.0 | Enhancement View pull request | 8.7.1 or higher |
1.12.0 | Enhancement View pull request | 8.7.1 or higher |
1.11.0 | Enhancement View pull request | 8.6.1 or higher |
1.10.0 | Enhancement View pull request | 8.6.1 or higher |
1.9.0 | Enhancement View pull request | 8.6.1 or higher |
1.8.2 | Enhancement View pull request | 8.1.0 or higher |
1.8.1 | Bug fix View pull request | 8.1.0 or higher |
1.8.0 | Enhancement View pull request | 8.1.0 or higher |
1.7.1 | Enhancement View pull request | 8.1.0 or higher |
1.7.0 | Enhancement View pull request | 7.16.0 or higher |
1.6.0 | Enhancement View pull request | 7.16.0 or higher |
1.5.3 | Bug fix View pull request | 7.16.0 or higher |
1.5.2 | Enhancement View pull request | 7.16.0 or higher |
1.5.1 | Enhancement View pull request | 7.16.0 or higher |
1.5.0 | Enhancement View pull request | 7.16.0 or higher |
1.4.0 | Enhancement View pull request | 7.16.0 or higher |
1.3.0 | Enhancement View pull request | 7.16.0 or higher |
1.2.2 | Bug fix View pull request | 7.16.0 or higher |
1.2.1 | Enhancement View pull request | 7.16.0 or higher |
1.2.0 | Enhancement View pull request | 7.16.0 or higher |
1.1.1 | Bug fix View pull request | 7.16.0 or higher |
1.1.0 | Enhancement View pull request | 7.16.0 or higher |
1.0.0 | Enhancement View pull request | 7.16.0 or higher |
0.2.2 | Bug fix View pull request | — |
0.2.1 | Bug fix View pull request | — |
0.2.0 | Enhancement View pull request | — |
0.1.1 | Bug fix View pull request | — |
0.1.0 | Enhancement View pull request | — |