No, GitLab `include` feature is designed to allow [override](https://docs.gitlab.com/ci/yaml/includes/#override-included-configuration-values) of the included job configuration for flexibility.
Depending on your GitLab Edition, you may consider using GitLab [compliance frameworks](https://docs.gitlab.com/user/group/compliance_frameworks/) and/or [Scan Execution Policies](https://docs.gitlab.com/user/application_security/policies/scan-execution-policies.html) that allow group admin to mandate certain job executions in the pipeline, but it CAN NOT prevent developers from doing any particular thing.
Depending on your GitLab Edition, you may consider using GitLab [compliance frameworks](https://docs.gitlab.com/user/group/compliance_frameworks/) and/or [Scan Execution Policies](https://docs.gitlab.com/user/application_security/policies/scan_execution_policies/) that allow group admin to mandate certain job executions in the pipeline, but it CAN NOT prevent developers from doing any particular thing.
## Is there any vulnerability scanner to run against the GitLab/_to-be-continuous_ templates?
