-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add guidance on the representation of process parentage #54
Conversation
ebc4955
to
705f1ff
Compare
705f1ff
to
6b37a57
Compare
@mlmitch , I recall a while back that @zschmerber was utilizing a Figma diagram to demonstrate parentage. Of course, this was prior to the |
Here is what i had for process but i agree a picture speaks a thousand words in this case. https://www.figma.com/board/nJKySDnnN7v2CwNpM9HoFV/Actor.process?t=ovxFyOOVmcQNo5TX-0 |
Great. I can incorporate something like that and some sample data I think. |
6b37a57
to
3b47ad1
Compare
Ready for review. I didn't end up including a diagram as there is already some good stuff in the blog I link and Zach's diagram was more about general process relationships than parentage specifically. I added a sample 1.4.0 event demonstrating all the concepts though. |
3b47ad1
to
20d4310
Compare
Signed-off-by: Mitchell Wasson <miwasson@cisco.com>
20d4310
to
f0558c6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this excellent article.
@mlmitch One thing you can do is, add this as a "Reference" in the dictionary definition of the process
object. So that people are directly linked to this article as they browse the schema. It will be similar to how I had done it for observables
, in case you need a sample.
Good suggestion Rajas. Mike recommended something similar. Will do. |
This document adds prescriptive guidance on how to effectively represent endpoint process parentage in OCSF