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

YAML Schema Modify - Add attribute to check if admin/root/required #371

Closed
ghost opened this issue Oct 4, 2018 · 4 comments
Closed

YAML Schema Modify - Add attribute to check if admin/root/required #371

ghost opened this issue Oct 4, 2018 · 4 comments

Comments

@ghost
Copy link

ghost commented Oct 4, 2018

A question was posed in the Atomic Channel about checking wether or not a test requires admin (Windows ) or root privileges.

I support this idea. Just need to think through where to put that check.
Update validation scripts
Retroactively update existing tests to have this added to all the existing test.

@brianebeyer
Copy link
Collaborator

I think we’d do this as a Boolean field inside the windows executor.

What would you expect execution frameworks to do if they encountered that field being true?

@ghost
Copy link
Author

ghost commented Oct 4, 2018

I think we need Linux/Mac too, to incorporate root access/requirements

Executor's could be modified to check and filter to either include or exclude.

Executor's could also check current privileges and then branch based on true/false

I guess I would like to see it in the YAML for the test, rather than the executor.

@ghost
Copy link
Author

ghost commented Dec 7, 2018

I actually think since this already in the MITRE ATT&CK we could just pull in that attribute from the API.
"x_mitre_permissions_required": Attribute

@brianebeyer
Copy link
Collaborator

I don't think we can used x_mitre_permissions_required because that is more focused on the technique rather than the specific test command being executed.

@ghost ghost closed this as completed Jan 16, 2019
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant