Skip to content

Commit

Permalink
[8.17] [Nov 26] Signature option available for macOS Trusted Apps con…
Browse files Browse the repository at this point in the history
…ditions (backport #6183) (#6260)

* 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>
  • Loading branch information
3 people authored Nov 28, 2024
1 parent f32f68a commit 001b577
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/management/admin/trusted-apps.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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.`).

Expand Down

0 comments on commit 001b577

Please sign in to comment.