Types, Deeper Static Analysis, and you
summary
Describes taking type annotations and a type checker, adding a call graph and interprocedural taint tracking that computes function summaries to catch user-controlled inputs flowing into dangerous sinks. Shows a working system built on hack for PHP that runs across tens of millions of lines, runs on every code change and takes about 20 minutes wall time, and reports that Python work uses Py (startup ~1 minute, incremental updates sub 200 ms) while taint for Python is planned.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:45An Example: Dangerous Information Flow
- 9:35Let's type check some code
- 14:00The Analyzer Pipeline
- 21:35millions of lines of Python; Pyre for type checking
- 23:38The Pyre Team
related talks
38mStatic Code Analysis - A Behind-the-scenes Look
42mContemporary Automatic Program Analysis
28mSecuring Code with the Python Type System
27mStatic Code Analysis with Python
37mA Static Tainting Analysis Method for Aspect-Oriented Programs
47mWeb Developers, Beware of the Tarpits for SAST in Your Code
58mSecurity Static Analysis - Avoiding an Angry Mob of Engineers
16mHardTaint: Production-Run Dynamic Taint Analysis via Selective Hardware Tracing