IRM enforcement of Java stack inspection

By Ú. Erlingsson, Fred B. Schneider. Proceeding 2000 IEEE Symposium on Security and Privacy. S&P 2000, 2000

362 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Computer security (2010, background): “29,30 Taint analysis marks inputs from untrusted sources and traces how these inputs are further processed.”
Static Analysis of Executables to Detect Malicious Patterns (2003, neutral): “Descriptions of these viruses are given below.”
Control-flow integrity (2005, methodology): “(IRMs) andSoftware Fault Isolation(SFI) [16, 17, 60].”
Semantics-aware malware detection (2005, background): “Another approach rewrites the binary to introduce checks driven by an enforceable security policy [15] (known as the inline reference monitor or the IRM approach).”
TrustVisor: Efficient TCB Reduction and Attestation (2010, background): “With TrustVisor, enterprises can develop small software modules that run as PALs and serve as inline reference monitors [13] or wrappers around third-party software.”
ZEUS: Analyzing Safety of Smart Contracts (2018, background): “Naccio [60], PoET/Pslang [59] and Polymer [53] enable policy specification for security properties.”