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.

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

Jump to bottom

Security Posture on OpenCTI #1047

Closed
RomuDeuxfois opened this issue Jun 4, 2024 · 0 comments · Fixed by #1048
Closed

Security Posture on OpenCTI #1047

RomuDeuxfois opened this issue Jun 4, 2024 · 0 comments · Fixed by #1048
Assignees
@RomuDeuxfois
Labels
bug use for describing something not working as expected solved The issue has been solved
Milestone
Release 1.0.9

Comments

@RomuDeuxfois
Copy link
Member

RomuDeuxfois commented Jun 4, 2024 •
edited
Loading

Description

When I create a scenario from OpenCTI, I want to have my security posture of the latest simulation based on scenarios created from my entity.

Solution

OpenCTI should get the latest ended simulation based on scenarios instead of the latest simulation based on the first scenario.

Testing

  • Generate a scenario from OpenCTI to OpenBAS
  • Launch a simulation with some expectations
  • Wait for the end of this simulation
  • Go to opencti and checked that the security posture is the same as that on OpenBAS
  • Re launch the simulation, change the expectation result and verify the new posture in both platform
@RomuDeuxfois RomuDeuxfois added bug use for describing something not working as expected 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 Jun 4, 2024
@RomuDeuxfois RomuDeuxfois self-assigned this Jun 4, 2024
@RomuDeuxfois RomuDeuxfois added this to the Bugs backlog milestone Jun 4, 2024
@Jipegien Jipegien modified the milestones: Bugs backlog, Release 1.0.9 Jun 4, 2024
@RomuDeuxfois RomuDeuxfois mentioned this issue Jun 5, 2024
Merged
@RomuDeuxfois RomuDeuxfois linked a pull request Jun 5, 2024 that will close this issue
[backend] Change external reference resolution for OpenCTI integration #1048
Merged
RomuDeuxfois added a commit that referenced this issue Jun 6, 2024
@RomuDeuxfois
[backend] Change external reference resolution for OpenCTI integration (
7e4872f 
#1047)
@RomuDeuxfois RomuDeuxfois added the solved The issue has been solved label Jun 6, 2024
johanah29 pushed a commit that referenced this issue Jun 11, 2024
@RomuDeuxfois @johanah29
[backend] Change external reference resolution for OpenCTI integration (
4d9272e 
#1047)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RomuDeuxfois RomuDeuxfois

Labels
bug use for describing something not working as expected solved The issue has been solved
Projects
None yet
Milestone
Release 1.0.9
Development

Successfully merging a pull request may close this issue.

[backend] Change external reference resolution for OpenCTI integration OpenBAS-Platform/openbas
2 participants
@RomuDeuxfois @Jipegien