Software Security
Messages Repeated message. Characterize security vulnerabilities for software systems, which could be domain specific. Aggressive static analysis to prevent design and implementation errors. Environments, compilers, ... Around 2000 Microsoft went into an overdrive on programming defensively against security vulnerabilities. Vista still has security problems.
Security properties is one more piece of concern added to concerns of functional correctness, performance metrics, real-time constraints, ...
Future More work on establishing lightweight properties of systems. Combination of static analysis and runtime monitoring (postponing what is not doable at compile/design time to runtime). Guard against mal-ware using PCC, establishing properties of code. Main problem is discovering enough lightweight properties that are checkable. Exchanges during verification subject to attacks.
Future Static analysis of binary is a greater issue than analyzing source code. Recovery from detection of security exploit or security related fault in a graceful way. Assumption of environment in static analysis to reduce complexity and false alarms of static analysis.
Future More aggressive support for security and privacy at OS/Kernel level. What are possible organizations of secure kernel + management kernel.