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 000000000..8b14a79d5
--- /dev/null
+++ b/rfcs/text/0044-add-apple-platform-specific-fields.md
@@ -0,0 +1,119 @@
+# 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. -->
+
+
+### 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.
+
+The following feelds needs to be considered being added:
+
+## Fields
+
+##### Proposed New Fields for Process object
+
+Field | Type | Example | Description
+--- | --- | --- | ---
+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.
+
+##### Proposed New Fields for Code Signature object
+
+Field | Type | Example | Description
+--- | --- | --- | ---
+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 Device 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
+
+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
+
+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.
+-->
+
+<!--
+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.
+
+* 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.
+
+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/2338
+
+<!--
+* 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 000000000..091339048
--- /dev/null
+++ b/rfcs/text/0044/code_signature.yml
@@ -0,0 +1,10 @@
+---
+- name: code_signature
+  fields:
+    - name: flags
+      level: extended
+      type: string
+      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/device.yml b/rfcs/text/0044/device.yml
new file mode 100644
index 000000000..5bfdcdb16
--- /dev/null
+++ b/rfcs/text/0044/device.yml
@@ -0,0 +1,10 @@
+---
+- name: device
+  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/hash.yml b/rfcs/text/0044/hash.yml
new file mode 100644
index 000000000..9d76c4957
--- /dev/null
+++ b/rfcs/text/0044/hash.yml
@@ -0,0 +1,9 @@
+---
+- name: file
+  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/process.yml b/rfcs/text/0044/process.yml
new file mode 100644
index 000000000..d9e869143
--- /dev/null
+++ b/rfcs/text/0044/process.yml
@@ -0,0 +1,36 @@
+---
+- 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: responsible
+        short_override: Information about the responsible process.
+
+- name: process
+  fields:
+    - name: platform_binary
+      level: extended
+      type: boolean
+      short: Indicates whether this process executable is a default platform binary shipped with the operating system.
+      description: >
+          Binaries that are shipped by the operating system are defined as platform binaries, this value is then set to true. 
+      example: true
+
+    - name: endpoint_security_client
+      level: extended
+      type: boolean
+      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
\ No newline at end of file