SAST

Static Application Security Testing

Analyze source code or bytecode for vulnerable patterns without running the application.

31 tools profiled

How it differs Reads the code you wrote without running it. SCA checks the third party packages you depend on; IAST watches the running app while your tests exercise it.

License
Subcategory
Deployment
Languages
Integrations
Maturity
Signals
Clear

3 tools match

Active Compliance Reporting Clear all

  • OpenText Fortify

    OpenText

    SAST

    A long-established enterprise static analyzer with very broad language support, rule-driven taint analysis and detailed compliance reporting.

    Commercial
    Established

  • Kiuwan Code Security

    Kiuwan (Idera)

    SAST

    A static analysis platform pairing security rules with code quality and technical debt metrics, covering both modern and legacy enterprise languages.

    Commercial
    Established

  • Veracode

    Veracode

    SAST

    Hosted application security platform whose static engine analyzes compiled binaries and bytecode rather than source, under a central policy model.

    Commercial
    Established

  • OpenText Fortify

    OpenText

    A long-established enterprise static analyzer with very broad language support, rule-driven taint analysis and detailed compliance reporting.

    Commercial Established
    SAST

  • Kiuwan Code Security

    Kiuwan (Idera)

    A static analysis platform pairing security rules with code quality and technical debt metrics, covering both modern and legacy enterprise languages.

    Commercial Established
    SAST

  • Veracode

    Veracode

    Hosted application security platform whose static engine analyzes compiled binaries and bytecode rather than source, under a central policy model.

    Commercial Established
    SAST
Tick up to 4 tools above.