Skip to content

Issues: OpenBAS-Platform/openbas

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.

Sign up for GitHub

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

131 Open 278 Closed
131 Open 278 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Sort simulation by updated date feature use for describing a new feature to develop tiny use to identify tiny feature to develop or bug to fix (< a week to solve)
#1065 opened Jun 7, 2024 by jborozco
Creating an exercise should redirect you to the page of the element created feature use for describing a new feature to develop tiny use to identify tiny feature to develop or bug to fix (< a week to solve)
#1058 opened Jun 6, 2024 by jborozco Release 1.2.0
@jborozco
Duplicate an exercise feature use for describing a new feature to develop
#1057 opened Jun 6, 2024 by jborozco Release 1.2.0
@jborozco
UI - In the navigation group scenario with simulation and atomic testing feature use for describing a new feature to develop tiny use to identify tiny feature to develop or bug to fix (< a week to solve)
#1056 opened Jun 6, 2024 by jborozco Release 1.2.0
@jborozco
Assets from a group of assets are not indented anymore bug use for describing something not working as expected
#1055 opened Jun 6, 2024 by jborozco Bugs backlog
Improve the selection of inject with MITRE filter feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
#1053 opened Jun 5, 2024 by jborozco
Team score over time in % of expectations is not correctly computed bug use for describing something not working as expected
#1045 opened Jun 2, 2024 by SamuelHassine Bugs backlog
When modifying an injector contract, the attack pattern field "+" is not in the right position bug use for describing something not working as expected
#1044 opened Jun 2, 2024 by SamuelHassine Bugs backlog
1
MITRE result matrix is duplicating everything (not coherent) bug use for describing something not working as expected
#1043 opened May 31, 2024 by SamuelHassine Bugs backlog
When scheduling a scenario once, then simulation is done, scenario is still marked as "scheduled" bug use for describing something not working as expected
#1040 opened May 31, 2024 by SamuelHassine Bugs backlog
1
Be able to select a platform (Windows / MacOS / Linux) when generating a technical scenario from OCTI feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
#1037 opened May 30, 2024 by SamuelHassine
Be able to define expiration time for expectations in the UI (with default values) feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
#1036 opened May 30, 2024 by SamuelHassine
If Caldera executor is enabled and Caldera is down, the platform should fail to start bug use for describing something not working as expected
#1034 opened May 30, 2024 by SamuelHassine Bugs backlog
For a scenario already scheduled, clicking on simulate now is not resetting properly (leading to not work) bug use for describing something not working as expected
#1031 opened May 30, 2024 by SamuelHassine Bugs backlog
1
Be able to duplicate a scenario quickly feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
#1030 opened May 30, 2024 by SamuelHassine
Validation of manual expectation displayed in Validation screen even if the inject has failed at execution bug use for describing something not working as expected
#1022 opened May 30, 2024 by Jipegien Bugs backlog
@Christian-DONGMO
2
Expectations cumulating in front in the validations screen bug use for describing something not working as expected
#1021 opened May 30, 2024 by Jipegien Bugs backlog
Full text search wrong indicators bug use for describing something not working as expected
#1017 opened May 29, 2024 by SamuelHassine Bugs backlog
Error on Inject simulated emails #908 bug use for describing something not working as expected
#1014 opened May 29, 2024 by marckto-filigran Bugs backlog
Facilitate score scanning of our user on global view feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
#1013 opened May 29, 2024 by jborozco
Performance overview is not reflecting MITRE Matrix bug use for describing something not working as expected
#1010 opened May 29, 2024 by SamuelHassine Bugs backlog
1
Fully replace "exercise" for "simulation" everywhere, including URLs feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team technical improvement Technical refactor or improvement is needed
#1009 opened May 29, 2024 by SamuelHassine
Massive operations in lists feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
#1003 opened May 28, 2024 by jborozco
Migrate IMAP / mails collection to Python collector feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
#978 opened May 26, 2024 by SamuelHassine
Migrate SMTP / email sending to Python injector feature use for describing a new feature to develop needs triage use to identify issue needing triage from Filigran Product team
#977 opened May 26, 2024 by SamuelHassine
1
ProTip! Type g p on any issue or pull request to go back to the pull request listing page.