Lack of actor property on Virtual Machine Activity #386
Answered
by
rroupski
overly-engineered
asked this question in
Q&A
-
I've been looking at the various events provided by OCSF, and many of them combine two or more entities into a single event. The virtual machine activity doesn't. There is no actor field on it, so I can describe what happened to a given VM but not what the instigator of that change was. What was the reason behind this decision? |
Beta Was this translation helpful? Give feedback.
Answered by
rroupski
Dec 6, 2022
Replies: 1 comment 1 reply
-
No reason -- we just missed it. Thank you! I'll add the |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
rroupski
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No reason -- we just missed it. Thank you!
I'll add the
Host, which add the
device(where the virtual machine runs on) and
actor.user`.