Full context in [parent epic](&3226) ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> Provide a CI job template (e.g. `Fuzzing.gitlab-ci.yml`) that users can include in their pipelines - Similar to how we provide `DAST.gitlab-ci.yml` and `SAST.gitlab-ci.yml`. For the MVC, detailed configuration of the input corpus or mutators is not required. Provide users enough flexibility for users to specify the high-level characteristics of the app to be fuzzed and then use a predetermined fuzzing configuration based on the type of application (e.g. HTTPS & PyTest as a framework) After including the job template in their `.gitlab-ci.yml` file, allow users to define in the steps to: * Build their app for coverage-guided fuzzing and/or point to where a compatible version of their app is - _Question_: Can we determine this automatically for certain use cases? - Override `CC/CXX` for C++ projects - Override `gccgoflags` for Go projects - Auto-add Ruby [Coverage](https://ruby-doc.org/stdlib-2.7.1/libdoc/coverage/rdoc/Coverage.html) for Ruby projects * _Question_: Can we use QEMU or another DBI framework to fuzz apps without re-building them for instrumentation? _Question_: 1. What parameters does a user need to provide to us? 1. Can we piggy back off of the unit tests? 1. Can we ask a user to provide us the test harness that would be used for fuzzing? This should leverage the CLI mode of our fuzzing engine, rather than require the user interact with a GUI The job _must_ be able to complete within the run of the pipeline and not [time out](https://docs.gitlab.com/ee/ci/pipelines/settings.html#timeout). ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Is this a cross-stage feature? <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### Links / references