ScholarGate
アシスタント

手法を比較

選択した手法を並べて確認できます。異なる行はハイライト表示されます。

シンボリック実行×静的アプリケーションセキュリティテスト×
分野暗号学暗号学
系統Machine learningMachine learning
提唱年19762000s
提唱者James C. KingVarious researchers
種類formal verification techniquesource code vulnerability detection
原典King, J. C. (1976). Symbolic execution and program testing. Communications of the ACM, 19(7), 385-394. DOI ↗Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. ISBN: 978-0321424778
別名symbolic execution, symbolic analysis, concolic executionSAST, white-box testing, source code analysis
関連33
概要Symbolic execution is a program analysis technique that executes programs using symbolic (non-concrete) values instead of actual inputs, tracking how symbolic values flow through the program. Introduced by James C. King in 1976, symbolic execution builds mathematical constraints on program variables and can determine which inputs cause specific program behaviors, enabling automatic test generation and vulnerability detection. Modern symbolic execution tools like KLEE, S2E, and Z3 have become powerful instruments for finding subtle bugs and security vulnerabilities.Static Application Security Testing (SAST) is a security analysis technique that examines source code or compiled binaries without executing the program to identify vulnerabilities, code quality issues, and security flaws. Developed in the 2000s, SAST analyzes code structure, data flow, and control flow to detect potential bugs such as SQL injection, buffer overflows, and insecure cryptographic usage. SAST is widely integrated into development workflows as a shift-left security practice, enabling early detection of vulnerabilities before code reaches production.
ScholarGateデータセット
  1. v1
  2. 2 出典
  3. PUBLISHED
  1. v1
  2. 2 出典
  3. PUBLISHED

検索へ スライドをダウンロード

ScholarGate手法を比較: Symbolic Execution · Static Application Security Testing. 2026-06-15に以下より取得 https://scholargate.app/ja/compare