- Elastic Common Schema (ECS) Reference: other versions:
- Overview
- Using ECS
- ECS Field Reference
- Base Fields
- Agent Fields
- Autonomous System Fields
- Client Fields
- Cloud Fields
- Code Signature Fields
- Container Fields
- Data Stream Fields
- Destination Fields
- DLL Fields
- DNS Fields
- ECS Fields
- ELF Header Fields
- Email Fields
- Error Fields
- Event Fields
- FaaS Fields
- File Fields
- Geo Fields
- Group Fields
- Hash Fields
- Host Fields
- HTTP Fields
- Interface Fields
- Log Fields
- Network Fields
- Observer Fields
- Orchestrator Fields
- Organization Fields
- Operating System Fields
- Package Fields
- PE Header Fields
- Process Fields
- Registry Fields
- Related Fields
- Rule Fields
- Server Fields
- Service Fields
- Source Fields
- Threat Fields
- TLS Fields
- Tracing Fields
- URL Fields
- User Fields
- User agent Fields
- VLAN Fields
- Vulnerability Fields
- x509 Certificate Fields
- ECS Categorization Fields
- Migrating to ECS
- Additional Information
- Release Notes
User Fields
editUser Fields
editThe user fields describe information about the user that is relevant to the event.
Fields can have one entry or multiple entries. If a user has more than one id, provide an array that includes all of them.
User Field Details
editField | Description | Level |
---|---|---|
Name of the directory the user is a member of. For example, an LDAP or Active Directory domain name. type: keyword |
extended |
|
User email address. type: keyword |
extended |
|
User’s full name, if available. type: keyword Multi-fields: * user.full_name.text (type: match_only_text) example: |
extended |
|
Unique user hash to correlate information for a user in anonymized form. Useful if type: keyword |
extended |
|
Unique identifier of the user. type: keyword example: |
core |
|
Short name or login of the user. type: keyword Multi-fields: * user.name.text (type: match_only_text) example: |
core |
|
Array of user roles at the time of the event. type: keyword Note: this field should contain an array of values. example: |
extended |
Field Reuse
editThe user
fields are expected to be nested at:
-
client.user
-
destination.user
-
process.real_user
-
process.saved_user
-
process.user
-
server.user
-
source.user
-
user.changes
-
user.effective
-
user.target
Note also that the user
fields may be used directly at the root of the events.
Field sets that can be nested under User
editLocation | Field Set | Description |
---|---|---|
|
Captures changes made to a user. |
|
|
User whose privileges were assumed. |
|
|
User’s group relevant to the event. |
|
|
Targeted user of action taken. |
User Field Usage
editFor usage and examples of the user fields, please see the User Fields Usage and Examples section.