From c904dc4177b4984c880fcd29d4d570c54272d563 Mon Sep 17 00:00:00 2001
From: Thijs Xhaflaire <thijsxhaflaire31@hotmail.com>
Date: Thu, 2 May 2024 10:33:02 +0200
Subject: [PATCH 1/9] Initial commit.

---
 ...0044-add-apple-platform-specific-fields.md | 110 ++++++++++++++++++
 rfcs/text/0044/code_signature.yml             |  11 ++
 rfcs/text/0044/hash.yml                       |   9 ++
 rfcs/text/0044/host.yml                       |  10 ++
 rfcs/text/0044/process.yml                    |  25 ++++
 5 files changed, 165 insertions(+)
 create mode 100644 rfcs/text/0044-add-apple-platform-specific-fields.md
 create mode 100644 rfcs/text/0044/code_signature.yml
 create mode 100644 rfcs/text/0044/hash.yml
 create mode 100644 rfcs/text/0044/host.yml
 create mode 100644 rfcs/text/0044/process.yml

diff --git a/rfcs/text/0044-add-apple-platform-specific-fields.md b/rfcs/text/0044-add-apple-platform-specific-fields.md
new file mode 100644
index 0000000000..1ac7c95052
--- /dev/null
+++ b/rfcs/text/0044-add-apple-platform-specific-fields.md
@@ -0,0 +1,110 @@
+# 0000: Name of RFC
+<!-- Leave this ID at 0000. The ECS team will assign a unique, contiguous RFC number upon merging the initial stage of this RFC. -->
+
+- Stage: **0 (strawperson)** <!-- Update to reflect target stage. See https://elastic.github.io/ecs/stages.html -->
+- Date: **TBD** <!-- The ECS team sets this date at merge time. This is the date of the latest stage advancement. -->
+
+<!--
+As you work on your RFC, use the "Stage N" comments to guide you in what you should focus on, for the stage you're targeting.
+Feel free to remove these comments as you go along.
+-->
+
+<!--
+Stage 0: Provide a high level summary of the premise of these changes. Briefly describe the nature, purpose, and impact of the changes. ~2-5 sentences.
+-->
+
+<!--
+Stage 1: If the changes include field additions or modifications, please create a folder titled as the RFC number under rfcs/text/. This will be where proposed schema changes as standalone YAML files or extended example mappings and larger source documents will go as the RFC is iterated upon.
+-->
+
+<!--
+Stage X: Provide a brief explanation of why the proposal is being marked as abandoned. This is useful context for anyone revisiting this proposal or considering similar changes later on.
+-->
+
+## Fields
+
+<!--
+Stage 1: Describe at a high level how this change affects fields. Include new or updated yml field definitions for all of the essential fields in this draft. While not exhaustive, the fields documented here should be comprehensive enough to deeply evaluate the technical considerations of this change. The goal here is to validate the technical details for all essential fields and to provide a basis for adding experimental field definitions to the schema. Use GitHub code blocks with yml syntax formatting, and add them to the corresponding RFC folder.
+-->
+
+<!--
+Stage 2: Add or update all remaining field definitions. The list should now be exhaustive. The goal here is to validate the technical details of all remaining fields and to provide a basis for releasing these field definitions as beta in the schema. Use GitHub code blocks with yml syntax formatting, and add them to the corresponding RFC folder.
+-->
+
+## Usage
+
+<!--
+Stage 1: Describe at a high-level how these field changes will be used in practice. Real world examples are encouraged. The goal here is to understand how people would leverage these fields to gain insights or solve problems. ~1-3 paragraphs.
+-->
+
+## Source data
+
+<!--
+Stage 1: Provide a high-level description of example sources of data. This does not yet need to be a concrete example of a source document, but instead can simply describe a potential source (e.g. nginx access log). This will ultimately be fleshed out to include literal source examples in a future stage. The goal here is to identify practical sources for these fields in the real world. ~1-3 sentences or unordered list.
+-->
+
+<!--
+Stage 2: Included a real world example source document. Ideally this example comes from the source(s) identified in stage 1. If not, it should replace them. The goal here is to validate the utility of these field changes in the context of a real world example. Format with the source name as a ### header and the example document in a GitHub code block with json formatting, or if on the larger side, add them to the corresponding RFC folder.
+-->
+
+<!--
+Stage 3: Add more real world example source documents so we have at least 2 total, but ideally 3. Format as described in stage 2.
+-->
+
+## Scope of impact
+
+<!--
+Stage 2: Identifies scope of impact of changes. Are breaking changes required? Should deprecation strategies be adopted? Will significant refactoring be involved? Break the impact down into:
+ * Ingestion mechanisms (e.g. beats/logstash)
+ * Usage mechanisms (e.g. Kibana applications, detections)
+ * ECS project (e.g. docs, tooling)
+The goal here is to research and understand the impact of these changes on users in the community and development teams across Elastic. 2-5 sentences each.
+-->
+
+## Concerns
+
+<!--
+Stage 1: Identify potential concerns, implementation challenges, or complexity. Spend some time on this. Play devil's advocate. Try to identify the sort of non-obvious challenges that tend to surface later. The goal here is to surface risks early, allow everyone the time to work through them, and ultimately document resolution for posterity's sake.
+-->
+
+<!--
+Stage 2: Document new concerns or resolutions to previously listed concerns. It's not critical that all concerns have resolutions at this point, but it would be helpful if resolutions were taking shape for the most significant concerns.
+-->
+
+<!--
+Stage 3: Document resolutions for all existing concerns. Any new concerns should be documented along with their resolution. The goal here is to eliminate risk of churn and instability by ensuring all concerns have been addressed.
+-->
+
+## People
+
+The following are the people that consulted on the contents of this RFC.
+
+* TBD | author
+
+<!--
+Who will be or has been consulted on the contents of this RFC? Identify authorship and sponsorship, and optionally identify the nature of involvement of others. Link to GitHub aliases where possible. This list will likely change or grow stage after stage.
+
+e.g.:
+
+* @Yasmina | author
+* @Monique | sponsor
+* @EunJung | subject matter expert
+* @JaneDoe | grammar, spelling, prose
+* @Mariana
+-->
+
+
+## References
+
+<!-- Insert any links appropriate to this RFC in this section. -->
+
+### RFC Pull Requests
+
+<!-- An RFC should link to the PRs for each of it stage advancements. -->
+
+* Stage 0: https://github.com/elastic/ecs/pull/NNN
+
+<!--
+* Stage 1: https://github.com/elastic/ecs/pull/NNN
+...
+-->
diff --git a/rfcs/text/0044/code_signature.yml b/rfcs/text/0044/code_signature.yml
new file mode 100644
index 0000000000..e3ccbba206
--- /dev/null
+++ b/rfcs/text/0044/code_signature.yml
@@ -0,0 +1,11 @@
+---
+- name: code_signature
+  fields:
+    - name: codesigning_flags
+      format: string
+      level: extended
+      type: long
+      short: Code signing flags of the process
+      description: >
+          The flags used to sign the process.
+      example: 570522385
\ No newline at end of file
diff --git a/rfcs/text/0044/hash.yml b/rfcs/text/0044/hash.yml
new file mode 100644
index 0000000000..3f757e7df8
--- /dev/null
+++ b/rfcs/text/0044/hash.yml
@@ -0,0 +1,9 @@
+---
+- name: hash
+  fields:
+    - name: cdhash
+      level: extended
+      type: keyword
+      short: The Code Directory (CD) hash of an executable.
+      description: Code directory hash, utilized to uniquely identify and authenticate the integrity of the executable code.
+      example: 3783b4052fd474dbe30676b45c329e7a6d44acd9
\ No newline at end of file
diff --git a/rfcs/text/0044/host.yml b/rfcs/text/0044/host.yml
new file mode 100644
index 0000000000..7abe0ff6f8
--- /dev/null
+++ b/rfcs/text/0044/host.yml
@@ -0,0 +1,10 @@
+---
+- name: host
+  fields:
+    - name: serial_number
+      level: core
+      type: keyword
+      short: Serial Number of the device
+      description: >
+        The unique serial number serves as a distinct identifier for each device, aiding in inventory management and device authentication.
+      example: DJGAQS4CW5
\ No newline at end of file
diff --git a/rfcs/text/0044/process.yml b/rfcs/text/0044/process.yml
new file mode 100644
index 0000000000..3214d9463c
--- /dev/null
+++ b/rfcs/text/0044/process.yml
@@ -0,0 +1,25 @@
+---
+- name: process
+  fields:
+    - name: platform_binary
+      level: extended
+      type: boolean
+      short: Indicates wethether this process executable is a default platform binary shipped with macOS.
+      description: >
+          Binaries that are shipped by macOS are defined as platform binaries, this value is then set to true. 
+      example: true
+
+    - name: es_client
+      level: extended
+      type: boolean
+      short: Indicates wethether this process executable is an Endpoint Security client.
+      description: >
+          Processes that have an endpoint security client must have the com.apple.endpointsecurity entitlement and the value is set to true in the message.
+      example: true
+
+    - name: thread.uuid
+      level: extended
+      type: keyword
+      example: 5E0470DA-BFD6-5F44-9C25-CD4E3AB81737
+      description: >
+        Globally unique identifier that can be utilised to correlate the activity of a thread.
\ No newline at end of file

From fd22adb688c92b66c181f0cd21df4a9ff555af1b Mon Sep 17 00:00:00 2001
From: Thijs Xhaflaire <thijsxhaflaire31@hotmail.com>
Date: Thu, 2 May 2024 10:59:15 +0200
Subject: [PATCH 2/9] Update 0044-add-apple-platform-specific-fields.md

---
 ...0044-add-apple-platform-specific-fields.md | 62 +++++++++++--------
 1 file changed, 35 insertions(+), 27 deletions(-)

diff --git a/rfcs/text/0044-add-apple-platform-specific-fields.md b/rfcs/text/0044-add-apple-platform-specific-fields.md
index 1ac7c95052..339c231860 100644
--- a/rfcs/text/0044-add-apple-platform-specific-fields.md
+++ b/rfcs/text/0044-add-apple-platform-specific-fields.md
@@ -4,44 +4,52 @@
 - Stage: **0 (strawperson)** <!-- Update to reflect target stage. See https://elastic.github.io/ecs/stages.html -->
 - Date: **TBD** <!-- The ECS team sets this date at merge time. This is the date of the latest stage advancement. -->
 
-<!--
-As you work on your RFC, use the "Stage N" comments to guide you in what you should focus on, for the stage you're targeting.
-Feel free to remove these comments as you go along.
--->
 
-<!--
-Stage 0: Provide a high level summary of the premise of these changes. Briefly describe the nature, purpose, and impact of the changes. ~2-5 sentences.
--->
+### Summary
+This RFC proposes the addition of Apple platform-specific fields to the ECS schema. This enhancement will enable security software vendors to more accurately map out data, particularly for Apple platforms.
 
-<!--
-Stage 1: If the changes include field additions or modifications, please create a folder titled as the RFC number under rfcs/text/. This will be where proposed schema changes as standalone YAML files or extended example mappings and larger source documents will go as the RFC is iterated upon.
--->
-
-<!--
-Stage X: Provide a brief explanation of why the proposal is being marked as abandoned. This is useful context for anyone revisiting this proposal or considering similar changes later on.
--->
+The following feelds needs to be considered being added:
 
 ## Fields
 
-<!--
-Stage 1: Describe at a high level how this change affects fields. Include new or updated yml field definitions for all of the essential fields in this draft. While not exhaustive, the fields documented here should be comprehensive enough to deeply evaluate the technical considerations of this change. The goal here is to validate the technical details for all essential fields and to provide a basis for adding experimental field definitions to the schema. Use GitHub code blocks with yml syntax formatting, and add them to the corresponding RFC folder.
--->
+#### Proposed New Fields for Process object
 
-<!--
-Stage 2: Add or update all remaining field definitions. The list should now be exhaustive. The goal here is to validate the technical details of all remaining fields and to provide a basis for releasing these field definitions as beta in the schema. Use GitHub code blocks with yml syntax formatting, and add them to the corresponding RFC folder.
--->
+Field | Type | Example | Description
+--- | --- | --- | ---
+platform_binary	| boolean	| true	| Indicates wethether this process executable is a default platform binary shipped with macOS.
+es_client	| boolean	| true	| Indicates wethether this process executable is an Endpoint Security client.
+thread.uuid	| keyword	| E0470DA-BFD6-5F44-9C25-CD4E3AB81737	| Globally unique identifier that can be utilised to correlate the activity of a thread.
+
+#### Proposed New Fields for Code Signature object
+
+Field | Type | Example | Description
+--- | --- | --- | ---
+codesigning_flags	| string	| 570522385	| The flags used to sign the process.
+
+#### Proposed New Fields for Hash object
+
+Field | Type | Example | Description
+--- | --- | --- | ---
+cdhash	| keyword	| 3783b4052fd474dbe30676b45c329e7a6d44acd9	| The Code Directory (CD) hash of an executable
+
+#### Proposed New Fields for Host object
+
+Field | Type | Example | Description
+--- | --- | --- | ---
+serial_number	| keyword	| DJGAQS4CW5	| The unique serial number serves as a distinct identifier for each device, aiding in inventory management and device authentication.
+
+### Motivation
+As the number of Apple endpoints in enterprises grows, having the right fields to map data becomes increasingly valuable. This enables security researchers using Elastic, particularly those focusing on macOS, to query data more effectively by leveraging enriched data sets.
 
 ## Usage
 
-<!--
-Stage 1: Describe at a high-level how these field changes will be used in practice. Real world examples are encouraged. The goal here is to understand how people would leverage these fields to gain insights or solve problems. ~1-3 paragraphs.
--->
+As a developer at Jamf, working on the Elastic integration for Jamf Protect, our goal is to map as many fields as possible, especially as Jamf specializes in Apple platform security. While developing the integration, we've identified some gaps related to mapping events to ECS.
+
+These new fields offer versatile methods. For instance, they facilitate querying process executions by platform binaries or endpoint security clients without requiring specific identifiers. The added hash fields are particularly valuable for tracking the hash of an application bundle alongside the hash of the executable in the directory itself, while the others are self-explanatory.
 
 ## Source data
 
-<!--
-Stage 1: Provide a high-level description of example sources of data. This does not yet need to be a concrete example of a source document, but instead can simply describe a potential source (e.g. nginx access log). This will ultimately be fleshed out to include literal source examples in a future stage. The goal here is to identify practical sources for these fields in the real world. ~1-3 sentences or unordered list.
--->
+This data originates from Endpoint Security software operating on a macOS host and can be transmitted through various methods, including an Elastic Agent and as example the use of the Jamf Protect integration, which supports AWS S3 or HTTPs.
 
 <!--
 Stage 2: Included a real world example source document. Ideally this example comes from the source(s) identified in stage 1. If not, it should replace them. The goal here is to validate the utility of these field changes in the context of a real world example. Format with the source name as a ### header and the example document in a GitHub code block with json formatting, or if on the larger side, add them to the corresponding RFC folder.
@@ -79,7 +87,7 @@ Stage 3: Document resolutions for all existing concerns. Any new concerns should
 
 The following are the people that consulted on the contents of this RFC.
 
-* TBD | author
+* txhaflaire | author
 
 <!--
 Who will be or has been consulted on the contents of this RFC? Identify authorship and sponsorship, and optionally identify the nature of involvement of others. Link to GitHub aliases where possible. This list will likely change or grow stage after stage.

From d39f66d0c7cc3c69ffd5b4727b38f557bb6102d7 Mon Sep 17 00:00:00 2001
From: Thijs Xhaflaire <thijsxhaflaire31@hotmail.com>
Date: Thu, 2 May 2024 15:57:23 +0200
Subject: [PATCH 3/9] Update 0044-add-apple-platform-specific-fields.md

---
 .../0044-add-apple-platform-specific-fields.md    | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/rfcs/text/0044-add-apple-platform-specific-fields.md b/rfcs/text/0044-add-apple-platform-specific-fields.md
index 339c231860..8dcdffcbdb 100644
--- a/rfcs/text/0044-add-apple-platform-specific-fields.md
+++ b/rfcs/text/0044-add-apple-platform-specific-fields.md
@@ -12,7 +12,7 @@ The following feelds needs to be considered being added:
 
 ## Fields
 
-#### Proposed New Fields for Process object
+##### Proposed New Fields for Process object
 
 Field | Type | Example | Description
 --- | --- | --- | ---
@@ -20,25 +20,26 @@ platform_binary	| boolean	| true	| Indicates wethether this process executable i
 es_client	| boolean	| true	| Indicates wethether this process executable is an Endpoint Security client.
 thread.uuid	| keyword	| E0470DA-BFD6-5F44-9C25-CD4E3AB81737	| Globally unique identifier that can be utilised to correlate the activity of a thread.
 
-#### Proposed New Fields for Code Signature object
+##### Proposed New Fields for Code Signature object
 
 Field | Type | Example | Description
 --- | --- | --- | ---
 codesigning_flags	| string	| 570522385	| The flags used to sign the process.
 
-#### Proposed New Fields for Hash object
+##### Proposed New Fields for Hash object
 
 Field | Type | Example | Description
 --- | --- | --- | ---
 cdhash	| keyword	| 3783b4052fd474dbe30676b45c329e7a6d44acd9	| The Code Directory (CD) hash of an executable
 
-#### Proposed New Fields for Host object
+##### Proposed New Fields for Host object
 
 Field | Type | Example | Description
 --- | --- | --- | ---
 serial_number	| keyword	| DJGAQS4CW5	| The unique serial number serves as a distinct identifier for each device, aiding in inventory management and device authentication.
 
 ### Motivation
+
 As the number of Apple endpoints in enterprises grows, having the right fields to map data becomes increasingly valuable. This enables security researchers using Elastic, particularly those focusing on macOS, to query data more effectively by leveraging enriched data sets.
 
 ## Usage
@@ -59,7 +60,7 @@ Stage 2: Included a real world example source document. Ideally this example com
 Stage 3: Add more real world example source documents so we have at least 2 total, but ideally 3. Format as described in stage 2.
 -->
 
-## Scope of impact
+<!--## Scope of impact
 
 <!--
 Stage 2: Identifies scope of impact of changes. Are breaking changes required? Should deprecation strategies be adopted? Will significant refactoring be involved? Break the impact down into:
@@ -69,7 +70,7 @@ Stage 2: Identifies scope of impact of changes. Are breaking changes required? S
 The goal here is to research and understand the impact of these changes on users in the community and development teams across Elastic. 2-5 sentences each.
 -->
 
-## Concerns
+<!--## Concerns
 
 <!--
 Stage 1: Identify potential concerns, implementation challenges, or complexity. Spend some time on this. Play devil's advocate. Try to identify the sort of non-obvious challenges that tend to surface later. The goal here is to surface risks early, allow everyone the time to work through them, and ultimately document resolution for posterity's sake.
@@ -110,7 +111,7 @@ e.g.:
 
 <!-- An RFC should link to the PRs for each of it stage advancements. -->
 
-* Stage 0: https://github.com/elastic/ecs/pull/NNN
+* Stage 0: https://github.com/elastic/ecs/pull/2338
 
 <!--
 * Stage 1: https://github.com/elastic/ecs/pull/NNN

From 197f0d199a125b0a9e517d05da2e538a48645f62 Mon Sep 17 00:00:00 2001
From: Thijs Xhaflaire <thijsxhaflaire31@hotmail.com>
Date: Tue, 2 Jul 2024 08:20:20 +0200
Subject: [PATCH 4/9] Added responsible to process, which is macOS specific.

---
 ...0044-add-apple-platform-specific-fields.md |  1 +
 rfcs/text/0044/process.yml                    | 50 +++++++++++++++++++
 2 files changed, 51 insertions(+)

diff --git a/rfcs/text/0044-add-apple-platform-specific-fields.md b/rfcs/text/0044-add-apple-platform-specific-fields.md
index 8dcdffcbdb..08641e051e 100644
--- a/rfcs/text/0044-add-apple-platform-specific-fields.md
+++ b/rfcs/text/0044-add-apple-platform-specific-fields.md
@@ -16,6 +16,7 @@ The following feelds needs to be considered being added:
 
 Field | Type | Example | Description
 --- | --- | --- | ---
+process.responsible	| keyword	| Terminal.app	| The responsible process on macOS, from an ancestry perspective, is the process that originally launched or spawned a given process.
 platform_binary	| boolean	| true	| Indicates wethether this process executable is a default platform binary shipped with macOS.
 es_client	| boolean	| true	| Indicates wethether this process executable is an Endpoint Security client.
 thread.uuid	| keyword	| E0470DA-BFD6-5F44-9C25-CD4E3AB81737	| Globally unique identifier that can be utilised to correlate the activity of a thread.
diff --git a/rfcs/text/0044/process.yml b/rfcs/text/0044/process.yml
index 3214d9463c..6a5fcce37a 100644
--- a/rfcs/text/0044/process.yml
+++ b/rfcs/text/0044/process.yml
@@ -1,4 +1,54 @@
 ---
+- name: process
+  title: Process
+  group: 2
+  short: These fields contain information about a process.
+  description: >
+    These fields contain information about a process.
+
+    These fields can help you correlate metrics information with a process id/name
+    from a log message.  The `process.pid` often stays in the metric itself and is
+    copied to the global field for correlation.
+  type: group
+  reusable:
+    top_level: true
+    expected:
+      - at: process
+        as: parent
+        short_override: Information about the parent process.
+      - at: process
+        as: responsible
+        short_override: Information about the responsible process.
+      - at: process
+        as: entry_leader
+        short_override: First process from terminal or remote access via SSH, SSM, etc OR a service directly started by the init process.
+      - at: process
+        as: session_leader
+        short_override: Often the same as entry_leader. When it differs, it represents a session started within another session. e.g. using tmux
+      - at: process
+        as: group_leader
+        short_override: Information about the process group leader. In some cases this may be the same as the top level process.
+      - at: process.parent
+        as: group_leader
+        short_override: Information about the parent's process group leader. Only pid, start and entity_id fields are set.
+      - at: process.entry_leader
+        as: parent
+        short_override: Information about the entry leader's parent process. Only pid, start and entity_id fields are set.
+      - at: process.session_leader
+        as: parent
+        short_override: Information about the session leader's parent process. Only pid, start and entity_id fields are set.
+      - at: process.entry_leader.parent
+        as: session_leader
+        short_override: Information about the parent session of the entry leader. Only pid, start and entity_id fields are set.
+      - at: process.session_leader.parent
+        as: session_leader
+        short_override: Information about the parent session of the session leader. Only pid, start and entity_id fields are set.
+      - at: process
+        as: previous
+        short_override: An array of previous executions for the process, including the initial fork. Only executable and args are set.
+        normalize:
+          - array
+
 - name: process
   fields:
     - name: platform_binary

From 31c19da10e4f4545a0178c9a48a605a5e08f0a42 Mon Sep 17 00:00:00 2001
From: Thijs Xhaflaire <thijsxhaflaire31@hotmail.com>
Date: Thu, 4 Jul 2024 18:38:49 +0200
Subject: [PATCH 5/9] Implementing suggestions from @mjwolf

---
 .../0044-add-apple-platform-specific-fields.md  |  9 ++++-----
 rfcs/text/0044/code_signature.yml               |  2 +-
 rfcs/text/0044/{hash.yml => file.yml}           |  2 +-
 rfcs/text/0044/process.yml                      | 17 +++++------------
 4 files changed, 11 insertions(+), 19 deletions(-)
 rename rfcs/text/0044/{hash.yml => file.yml} (96%)

diff --git a/rfcs/text/0044-add-apple-platform-specific-fields.md b/rfcs/text/0044-add-apple-platform-specific-fields.md
index 08641e051e..b08fa01acf 100644
--- a/rfcs/text/0044-add-apple-platform-specific-fields.md
+++ b/rfcs/text/0044-add-apple-platform-specific-fields.md
@@ -17,17 +17,16 @@ The following feelds needs to be considered being added:
 Field | Type | Example | Description
 --- | --- | --- | ---
 process.responsible	| keyword	| Terminal.app	| The responsible process on macOS, from an ancestry perspective, is the process that originally launched or spawned a given process.
-platform_binary	| boolean	| true	| Indicates wethether this process executable is a default platform binary shipped with macOS.
-es_client	| boolean	| true	| Indicates wethether this process executable is an Endpoint Security client.
-thread.uuid	| keyword	| E0470DA-BFD6-5F44-9C25-CD4E3AB81737	| Globally unique identifier that can be utilised to correlate the activity of a thread.
+platform_binary	| boolean	| true	| Indicates wethether this process executable is a default platform binary shipped with the operating system.
+endpoint_security_client	| boolean	| true	| Indicates wethether this process executable is an Endpoint Security client.
 
 ##### Proposed New Fields for Code Signature object
 
 Field | Type | Example | Description
 --- | --- | --- | ---
-codesigning_flags	| string	| 570522385	| The flags used to sign the process.
+flags	| string	| 570522385	| The flags used to sign the process.
 
-##### Proposed New Fields for Hash object
+##### Proposed New Fields for File object
 
 Field | Type | Example | Description
 --- | --- | --- | ---
diff --git a/rfcs/text/0044/code_signature.yml b/rfcs/text/0044/code_signature.yml
index e3ccbba206..b45f47d59a 100644
--- a/rfcs/text/0044/code_signature.yml
+++ b/rfcs/text/0044/code_signature.yml
@@ -1,7 +1,7 @@
 ---
 - name: code_signature
   fields:
-    - name: codesigning_flags
+    - name: flags
       format: string
       level: extended
       type: long
diff --git a/rfcs/text/0044/hash.yml b/rfcs/text/0044/file.yml
similarity index 96%
rename from rfcs/text/0044/hash.yml
rename to rfcs/text/0044/file.yml
index 3f757e7df8..9d76c4957c 100644
--- a/rfcs/text/0044/hash.yml
+++ b/rfcs/text/0044/file.yml
@@ -1,5 +1,5 @@
 ---
-- name: hash
+- name: file
   fields:
     - name: cdhash
       level: extended
diff --git a/rfcs/text/0044/process.yml b/rfcs/text/0044/process.yml
index 6a5fcce37a..3b39357f2f 100644
--- a/rfcs/text/0044/process.yml
+++ b/rfcs/text/0044/process.yml
@@ -54,22 +54,15 @@
     - name: platform_binary
       level: extended
       type: boolean
-      short: Indicates wethether this process executable is a default platform binary shipped with macOS.
+      short: Indicates whether this process executable is a default platform binary shipped with the operating system.
       description: >
-          Binaries that are shipped by macOS are defined as platform binaries, this value is then set to true. 
+          Binaries that are shipped by the operating system are defined as platform binaries, this value is then set to true. 
       example: true
 
-    - name: es_client
+    - name: endpoint_security_client
       level: extended
       type: boolean
-      short: Indicates wethether this process executable is an Endpoint Security client.
+      short: Indicates whether this process executable is an Endpoint Security client.
       description: >
           Processes that have an endpoint security client must have the com.apple.endpointsecurity entitlement and the value is set to true in the message.
-      example: true
-
-    - name: thread.uuid
-      level: extended
-      type: keyword
-      example: 5E0470DA-BFD6-5F44-9C25-CD4E3AB81737
-      description: >
-        Globally unique identifier that can be utilised to correlate the activity of a thread.
\ No newline at end of file
+      example: true
\ No newline at end of file

From 01577462ab7cd8bf26f8f23b72765f98b71290f4 Mon Sep 17 00:00:00 2001
From: Thijs Xhaflaire <thijsxhaflaire31@hotmail.com>
Date: Thu, 4 Jul 2024 21:09:04 +0200
Subject: [PATCH 6/9] Update process.yml

---
 rfcs/text/0044/process.yml | 32 --------------------------------
 1 file changed, 32 deletions(-)

diff --git a/rfcs/text/0044/process.yml b/rfcs/text/0044/process.yml
index 3b39357f2f..d9e8691439 100644
--- a/rfcs/text/0044/process.yml
+++ b/rfcs/text/0044/process.yml
@@ -13,41 +13,9 @@
   reusable:
     top_level: true
     expected:
-      - at: process
-        as: parent
-        short_override: Information about the parent process.
       - at: process
         as: responsible
         short_override: Information about the responsible process.
-      - at: process
-        as: entry_leader
-        short_override: First process from terminal or remote access via SSH, SSM, etc OR a service directly started by the init process.
-      - at: process
-        as: session_leader
-        short_override: Often the same as entry_leader. When it differs, it represents a session started within another session. e.g. using tmux
-      - at: process
-        as: group_leader
-        short_override: Information about the process group leader. In some cases this may be the same as the top level process.
-      - at: process.parent
-        as: group_leader
-        short_override: Information about the parent's process group leader. Only pid, start and entity_id fields are set.
-      - at: process.entry_leader
-        as: parent
-        short_override: Information about the entry leader's parent process. Only pid, start and entity_id fields are set.
-      - at: process.session_leader
-        as: parent
-        short_override: Information about the session leader's parent process. Only pid, start and entity_id fields are set.
-      - at: process.entry_leader.parent
-        as: session_leader
-        short_override: Information about the parent session of the entry leader. Only pid, start and entity_id fields are set.
-      - at: process.session_leader.parent
-        as: session_leader
-        short_override: Information about the parent session of the session leader. Only pid, start and entity_id fields are set.
-      - at: process
-        as: previous
-        short_override: An array of previous executions for the process, including the initial fork. Only executable and args are set.
-        normalize:
-          - array
 
 - name: process
   fields:

From bcefffd8960b5e85efc905db51023d802305abca Mon Sep 17 00:00:00 2001
From: Thijs Xhaflaire <thijsxhaflaire31@hotmail.com>
Date: Wed, 17 Jul 2024 14:25:26 +0200
Subject: [PATCH 7/9] adding it back to hash.

---
 rfcs/text/0044-add-apple-platform-specific-fields.md | 2 +-
 rfcs/text/0044/{file.yml => hash.yml}                | 0
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename rfcs/text/0044/{file.yml => hash.yml} (100%)

diff --git a/rfcs/text/0044-add-apple-platform-specific-fields.md b/rfcs/text/0044-add-apple-platform-specific-fields.md
index b08fa01acf..0bbe999392 100644
--- a/rfcs/text/0044-add-apple-platform-specific-fields.md
+++ b/rfcs/text/0044-add-apple-platform-specific-fields.md
@@ -26,7 +26,7 @@ Field | Type | Example | Description
 --- | --- | --- | ---
 flags	| string	| 570522385	| The flags used to sign the process.
 
-##### Proposed New Fields for File object
+##### Proposed New Fields for Hash object
 
 Field | Type | Example | Description
 --- | --- | --- | ---
diff --git a/rfcs/text/0044/file.yml b/rfcs/text/0044/hash.yml
similarity index 100%
rename from rfcs/text/0044/file.yml
rename to rfcs/text/0044/hash.yml

From 395cb6ed3ff004f22318594b3cc9ac35dd6eb7f8 Mon Sep 17 00:00:00 2001
From: Thijs Xhaflaire <thijsxhaflaire31@hotmail.com>
Date: Wed, 17 Jul 2024 14:27:47 +0200
Subject: [PATCH 8/9] Updated readme

---
 rfcs/text/0044-add-apple-platform-specific-fields.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rfcs/text/0044-add-apple-platform-specific-fields.md b/rfcs/text/0044-add-apple-platform-specific-fields.md
index 0bbe999392..0765ef1de8 100644
--- a/rfcs/text/0044-add-apple-platform-specific-fields.md
+++ b/rfcs/text/0044-add-apple-platform-specific-fields.md
@@ -16,7 +16,7 @@ The following feelds needs to be considered being added:
 
 Field | Type | Example | Description
 --- | --- | --- | ---
-process.responsible	| keyword	| Terminal.app	| The responsible process on macOS, from an ancestry perspective, is the process that originally launched or spawned a given process.
+responsible	| keyword	| Terminal.app	| The responsible process on macOS, from an ancestry perspective, is the process that originally launched or spawned a given process.
 platform_binary	| boolean	| true	| Indicates wethether this process executable is a default platform binary shipped with the operating system.
 endpoint_security_client	| boolean	| true	| Indicates wethether this process executable is an Endpoint Security client.
 

From 7da2327a9a4b076094665ce440ceefcc27680406 Mon Sep 17 00:00:00 2001
From: Thijs Xhaflaire <thijsxhaflaire31@hotmail.com>
Date: Thu, 18 Jul 2024 14:43:40 +0200
Subject: [PATCH 9/9] resolved suggestions from @trisch-me

---
 rfcs/text/0044-add-apple-platform-specific-fields.md | 2 +-
 rfcs/text/0044/code_signature.yml                    | 3 +--
 rfcs/text/0044/{host.yml => device.yml}              | 2 +-
 3 files changed, 3 insertions(+), 4 deletions(-)
 rename rfcs/text/0044/{host.yml => device.yml} (95%)

diff --git a/rfcs/text/0044-add-apple-platform-specific-fields.md b/rfcs/text/0044-add-apple-platform-specific-fields.md
index 0765ef1de8..8b14a79d5d 100644
--- a/rfcs/text/0044-add-apple-platform-specific-fields.md
+++ b/rfcs/text/0044-add-apple-platform-specific-fields.md
@@ -32,7 +32,7 @@ Field | Type | Example | Description
 --- | --- | --- | ---
 cdhash	| keyword	| 3783b4052fd474dbe30676b45c329e7a6d44acd9	| The Code Directory (CD) hash of an executable
 
-##### Proposed New Fields for Host object
+##### Proposed New Fields for Device object
 
 Field | Type | Example | Description
 --- | --- | --- | ---
diff --git a/rfcs/text/0044/code_signature.yml b/rfcs/text/0044/code_signature.yml
index b45f47d59a..091339048d 100644
--- a/rfcs/text/0044/code_signature.yml
+++ b/rfcs/text/0044/code_signature.yml
@@ -2,9 +2,8 @@
 - name: code_signature
   fields:
     - name: flags
-      format: string
       level: extended
-      type: long
+      type: string
       short: Code signing flags of the process
       description: >
           The flags used to sign the process.
diff --git a/rfcs/text/0044/host.yml b/rfcs/text/0044/device.yml
similarity index 95%
rename from rfcs/text/0044/host.yml
rename to rfcs/text/0044/device.yml
index 7abe0ff6f8..5bfdcdb161 100644
--- a/rfcs/text/0044/host.yml
+++ b/rfcs/text/0044/device.yml
@@ -1,5 +1,5 @@
 ---
-- name: host
+- name: device
   fields:
     - name: serial_number
       level: core