-
Notifications
You must be signed in to change notification settings - Fork 73
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
Ability to choose a service account on linux #1179
Closed
jborozco opened this issue
Jul 2, 2024
· 2 comments
· Fixed by OpenBAS-Platform/collectors#41 · May be fixed by OpenBAS-Platform/agent#14
Closed
Ability to choose a service account on linux #1179
jborozco opened this issue
Jul 2, 2024
· 2 comments
· Fixed by OpenBAS-Platform/collectors#41 · May be fixed by OpenBAS-Platform/agent#14
Comments
jborozco
added
feature
use for describing a new feature to develop
needs triage
use to identify issue needing triage from Filigran Product team
and removed
needs triage
use to identify issue needing triage from Filigran Product team
labels
Jul 2, 2024
jborozco
changed the title
Ability to choose non-system user to execute a custom payload
Ability to choose non-system user to execute a payload
Aug 30, 2024
This was
linked to
pull requests
Sep 9, 2024
Scope: Paylaod custom, windows, openbas agent : https://www.notion.so/filigran/Ability-to-choose-non-system-user-to-execute-a-payload-91f0f341848e431895a8bfb463703082. Prs POC: |
5 tasks
EllynBsc
changed the title
Ability to choose non-system user to execute a payload
Ability to choose non-system user to execute a payload - define a Service Account
Sep 25, 2024
EllynBsc
changed the title
Ability to choose non-system user to execute a payload - define a Service Account
Chunk 1: define a Service Account, first step of having the ability to choose non-system user to execute a payload
Oct 17, 2024
EllynBsc
changed the title
Chunk 1: define a Service Account, first step of having the ability to choose non-system user to execute a payload
Ability to choose a service account on linux
Oct 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use case
To reproduce real attack environment, I want to be able to execute a custom payload through a non-system user.
After doing a POC and for a first MVP, we want to be able to define a Service Account (first on Linux) for the ability to:
-CRUD a Service account to be used for executing injects on endpoints as an admin
-Execute a payload with elevated privilege by default
The text was updated successfully, but these errors were encountered: