### Overview As we built out [Secret Push Protection](https://docs.gitlab.com/ee/user/application_security/secret_detection/secret_push_protection) and took it through an [experimental](https://gitlab.com/groups/gitlab-org/-/epics/11587 "[MVC] Build first iteration of pre-receive secret detection") and [beta](https://gitlab.com/groups/gitlab-org/-/epics/12729 "Make Secret Push Protection available in Beta on GitLab.com") phases, we had a number of gaps in our API support for the feature. We want to address one of those gaps by creating a REST API endpoint to update [project security settings](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/models/project_security_setting.rb). Please note that _no REST API endpoints currently exist_ for [project security settings](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/app/models/project_security_setting.rb) at all. In this issue, we only aim to add an endpoint to **update** those records. Specifically, this endpoint will focus only on updating `pre_receive_secret_detection_enabled` because the other ones will need more investigating about the extent of their impact. ### Proposal To address this gap, one could possibly: * [x] Create a REST API endpoint to allow updating project security settings (see [similar example](https://gitlab.com/gitlab-org/gitlab/-/blob/master/ee/lib/api/project_approval_settings.rb)). * [x] Create corresponding documentation for the new _Project Security Settings API_ endpoint.