forked from elastic/ecs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
code_signature.yml
116 lines (100 loc) · 3.76 KB
/
code_signature.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
# Licensed to Elasticsearch B.V. under one or more contributor
# license agreements. See the NOTICE file distributed with
# this work for additional information regarding copyright
# ownership. Elasticsearch B.V. licenses this file to you under
# the Apache License, Version 2.0 (the "License"); you may
# not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing,
# software distributed under the License is distributed on an
# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
# KIND, either express or implied. See the License for the
# specific language governing permissions and limitations
# under the License.
---
- name: code_signature
title: Code Signature
group: 2
description: These fields contain information about binary code signatures.
type: group
reusable:
top_level: false
expected:
- file
- process
- dll
# - driver
fields:
- name: exists
level: core
type: boolean
description: Boolean to capture if a signature is present.
example: "true"
- name: subject_name
level: core
type: keyword
description: Subject name of the code signer
example: Microsoft Corporation
- name: valid
level: extended
type: boolean
short: Boolean to capture if the digital signature is verified against the binary content.
example: "true"
description: >
Boolean to capture if the digital signature is verified against the binary content.
Leave unpopulated if a certificate was unchecked.
- name: trusted
level: extended
type: boolean
short: Stores the trust status of the certificate chain.
example: "true"
description: >
Stores the trust status of the certificate chain.
Validating the trust of the certificate chain may be complicated, and this field should only be populated
by tools that actively check the status.
- name: status
level: extended
type: keyword
short: Additional information about the certificate status.
description: >
Additional information about the certificate status.
This is useful for logging cryptographic errors with the certificate validity or trust status.
Leave unpopulated if the validity or trust of the certificate was unchecked.
example: ERROR_UNTRUSTED_ROOT
- name: team_id
level: extended
type: keyword
short: The team identifier used to sign the process.
description: >
The team identifier used to sign the process.
This is used to identify the team or vendor of a software product.
The field is relevant to Apple *OS only.
example: EQHXZ8M8AV
- name: signing_id
level: extended
type: keyword
short: The identifier used to sign the process.
description: >
The identifier used to sign the process.
This is used to identify the application manufactured by a software vendor.
The field is relevant to Apple *OS only.
example: com.apple.xpc.proxy
- name: digest_algorithm
level: extended
type: keyword
short: Hashing algorithm used to sign the process.
description: >
The hashing algorithm used to sign the process.
This value can distinguish signatures when a file is signed multiple times
by the same signer but with a different digest algorithm.
example: sha256
- name: timestamp
level: extended
type: date
short: When the signature was generated and signed.
description: >
Date and time when the code signature was generated and signed.
example: "2021-01-01T12:10:30Z"