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

Merge brute force and vulnerability exploiters in the configuration #2787

Closed
11 tasks done
mssalvatore opened this issue Jan 5, 2023 · 0 comments · Fixed by #2796
Closed
11 tasks done

Merge brute force and vulnerability exploiters in the configuration #2787

mssalvatore opened this issue Jan 5, 2023 · 0 comments · Fixed by #2796

Comments

@mssalvatore
Copy link
Collaborator

mssalvatore commented Jan 5, 2023

Description

The separation between brute force and vulnerability exploiters was based on the use case of "vulnerability scanning", which is no longer Infection Monkey's main goal. Ultimately, users should be able to configure the order that exploiters run in. While the UI doesn't allow this at the moment, the configuration can be manipulated manually to achieve this. However, vulnerability exploiters always run before brute force exploiters. In other words, this separation reduces the configurability of the system.

Note

To avoid breaking develop, base all work off of 2787-merge-vulnerability-and-brute-force-exploiter-config.

Tasks

  • Modify the AgentConfiguration object to contain only "Exploiters` (0d) @mssalvatore
    • Pydantic object
    • Unit tests
    • Default configuration
  • Modify the UI to comply with the new configuration (0d) @ilija-lazoroski
    • UI Schema
    • SafeOptionValidator
  • Modify the logic in infection_monkey.master.exploiter to use the new configuration (0d) @mssalvatore
  • Modify the logic in monkey_island.cc.services.reporting.report to use the new configuration (0d) @ilija-lazoroski
  • Modify the path_in_schema in the AgentConfigurationSchemaService (0d) @ilija-lazoroski
  • Fix BB tests (0d)
mssalvatore added a commit that referenced this issue Jan 5, 2023
The separation between brute force and vulnerability exploiters was
based on the use case of "vulnerability scanning", which is no longer
Infection Monkey's main goal. Ultimately, users should be able to
configure the order that exploiters run in. While the UI doesn't allow
this at the moment, the configuration can be manipulated manually to
achieve this. However, vulnerability exploiters always run before brute
force exploiters. In other words, this separation reduces the
configurability of the system.

By merging these into a single list of exploiters, we allow the user to
have total control over the order in which exploiters are run.

Issue #2787
mssalvatore added a commit that referenced this issue Jan 5, 2023
The separation between brute force and vulnerability exploiters was
based on the use case of "vulnerability scanning", which is no longer
Infection Monkey's main goal. Ultimately, users should be able to
configure the order that exploiters run in. While the UI doesn't allow
this at the moment, the configuration can be manipulated manually to
achieve this. However, vulnerability exploiters always run before brute
force exploiters. In other words, this separation reduces the
configurability of the system.

By merging these into a single list of exploiters, we allow the user to
have total control over the order in which exploiters are run.

Issue #2787
PR #2789
cakekoa pushed a commit that referenced this issue Jan 5, 2023
The separation between brute force and vulnerability exploiters was
based on the use case of "vulnerability scanning", which is no longer
Infection Monkey's main goal. Ultimately, users should be able to
configure the order that exploiters run in. While the UI doesn't allow
this at the moment, the configuration can be manipulated manually to
achieve this. However, vulnerability exploiters always run before brute
force exploiters. In other words, this separation reduces the
configurability of the system.

By merging these into a single list of exploiters, we allow the user to
have total control over the order in which exploiters are run.

Issue #2787
PR #2789
mssalvatore added a commit that referenced this issue Jan 5, 2023
…nerability-and-brute-force-exploiter-config

Issue #2787
PR #2790
ilija-lazoroski pushed a commit that referenced this issue Jan 6, 2023
The separation between brute force and vulnerability exploiters was
based on the use case of "vulnerability scanning", which is no longer
Infection Monkey's main goal. Ultimately, users should be able to
configure the order that exploiters run in. While the UI doesn't allow
this at the moment, the configuration can be manipulated manually to
achieve this. However, vulnerability exploiters always run before brute
force exploiters. In other words, this separation reduces the
configurability of the system.

By merging these into a single list of exploiters, we allow the user to
have total control over the order in which exploiters are run.

Issue #2787
PR #2789
mssalvatore added a commit that referenced this issue Jan 6, 2023
The separation between brute force and vulnerability exploiters was
based on the use case of "vulnerability scanning", which is no longer
Infection Monkey's main goal. Ultimately, users should be able to
configure the order that exploiters run in. While the UI doesn't allow
this at the moment, the configuration can be manipulated manually to
achieve this. However, vulnerability exploiters always run before brute
force exploiters. In other words, this separation reduces the
configurability of the system.

By merging these into a single list of exploiters, we allow the user to
have total control over the order in which exploiters are run.

Issue #2787
PR #2789
mssalvatore added a commit that referenced this issue Jan 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant