Skip to content
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

Signed vs. Unsigned Drivers/Processes Cyber Observables #50

Open
ikiril01 opened this issue Nov 22, 2017 · 2 comments
Open

Signed vs. Unsigned Drivers/Processes Cyber Observables #50

ikiril01 opened this issue Nov 22, 2017 · 2 comments

Comments

@ikiril01
Copy link

Jason pointed out that we currently can't characterize signed vs. unsigned processes and drivers in Cyber Observables. For processes, this would mean adding a new property to the Process Cyber Observable Object. For drivers, we'd have to add a new Cyber Observable Object.

@gtback
Copy link

gtback commented Nov 27, 2017

Is the process itself signed, or the file that is used to launch the process? Almost seems like this would be better for extension(s) of the File object.

@JasonKeirstead
Copy link

Use case example: Match when any unsigned executable has been loaded into lass.exe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants