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

Secure schema changing force_disabled_introspection option to true by default #6896

Closed
richard-julien opened this issue May 6, 2024 · 1 comment
Closed

Secure schema changing force_disabled_introspection option to true by default #6896

richard-julien opened this issue May 6, 2024 · 1 comment
Assignees
@richard-julien
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 6.1.0

Comments

@richard-julien
Copy link
Member

Use case

Secure schema changing force_disabled_introspection option to true by default
This change will make the platform more secure by default
@richard-julien richard-julien added the feature use for describing a new feature to develop label May 6, 2024
@richard-julien richard-julien added this to the Release 6.1.0 milestone May 6, 2024
@richard-julien richard-julien self-assigned this May 6, 2024
richard-julien added a commit that referenced this issue May 6, 2024
@richard-julien
[backend] Secure schema changing force_disabled_introspection option …
5f904f7 
…to true by default (#6896)
@richard-julien richard-julien added the solved use to identify issue that has been solved (must be linked to the solving PR) label May 6, 2024
Archidoit pushed a commit that referenced this issue Jun 6, 2024
@richard-julien @Archidoit
[backend] Secure schema changing force_disabled_introspection option …
8110353 
…to true by default (#6896)
@SamuelHassine
Copy link
Member

SamuelHassine commented Jul 14, 2024 •
edited
Loading

To re-enable: https://docs.opencti.io/latest/deployment/configuration/#technical-customization.

@seanthegeek seanthegeek mentioned this issue Oct 3, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@richard-julien richard-julien

Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 6.1.0
Development

No branches or pull requests
2 participants
@richard-julien @SamuelHassine