## Motivation > [GitLab Advanced SAST](https://docs.gitlab.com/ee/user/application_security/sast/gitlab_advanced_sast.html) provides cross-file, cross-function scanning, including a more powerful engine and matching detection rules. Enabling these capabilities will improve SAST result quality for customers. See [parent epic motivation](https://gitlab.com/groups/gitlab-org/-/epics/14312#motivation). ## Requirements for each language > We need to deliver each language as an end-to-end capability, meaning: > - The engine must support cross-file, cross-function scanning for that language. > - We must distribute a ruleset that takes advantage of cross-file, cross-function capabilities. (This ruleset should still include rules that don't need to track dataflow, but we can't really say that we offer cross-file/cross-function scanning if no rules are using it.) See [parent epic requirements](https://gitlab.com/groups/gitlab-org/-/epics/14312#requirements-for-each-language). ## Notes on C++ There may be cases where we cannot successfully parse or scan C++ code. As part of this epic, to the extent feasible, we should enumerate and document those limitations. <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> > [!important] > This page may contain information related to upcoming products, features and functionality. > It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. > Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc. <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->