[8.17] [Nov 26] Signature option available for macOS Trusted Apps conditions (backport #6183) (#6260)

mergify[bot] · natasha-moore-elastic · github-actions[bot] · web-flow · commit 001b57757300 · 2024-11-28T10:19:44.000Z
* Signature option available for macOS Trusted Apps conditions (#6183) (cherry picked from commit 5fb37a6) # Conflicts: # docs/serverless/edr-manage/trusted-apps-ov.asciidoc * Delete docs/serverless directory and its contents --------- Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
diff --git a/docs/management/admin/trusted-apps.asciidoc b/docs/management/admin/trusted-apps.asciidoc
@@ -37,7 +37,7 @@ To add a trusted application:
 * `Field`: Select a field to identify the trusted application:
 ** `Hash`: The MD5, SHA-1, or SHA-256 hash value of the application's executable.
 ** `Path`: The full file path of the application's executable.
-** `Signature`: (Windows only) The name of the application's digital signer.
+** `Signature`: (Windows and macOS only) The name of the application's digital signer.
 +
 TIP: To find the signer's name for an application, go to *Kibana* -> *Discover* and query the process name of the application's executable (for example, `process.name : "mctray.exe"` for a McAfee security binary). Then, search the results for the `process.code_signature.subject_name` field, which contains the signer's name (for example, `McAfee, Inc.`).
 

Original file line number	Diff line number	Diff line change
`@@ -37,7 +37,7 @@ To add a trusted application:`
`37`	`37`	* `Field`: Select a field to identify the trusted application:
`38`	`38`	** `Hash`: The MD5, SHA-1, or SHA-256 hash value of the application's executable.
`39`	`39`	** `Path`: The full file path of the application's executable.
`40`		-** `Signature`: (Windows only) The name of the application's digital signer.
	`40`	+** `Signature`: (Windows and macOS only) The name of the application's digital signer.
`41`	`41`	`+`
`42`	`42`	TIP: To find the signer's name for an application, go to Kibana -> Discover and query the process name of the application's executable (for example, `process.name : "mctray.exe"` for a McAfee security binary). Then, search the results for the `process.code_signature.subject_name` field, which contains the signer's name (for example, `McAfee, Inc.`).
`43`	`43`