Why Monitoring Mobile Code is Harder than it Sounds

4/29/99


Click here to start


Table of Contents

Why Monitoring Mobile Code is Harder than it Sounds

Outline

Security and Mobile Code

Mobile code is smart

Why use mobile code?

Mobile code is dumb

A brief history

Some big questions

Mobile Code Gone Wrong

Real mobile code security problems

A Classic Tradeoff

Four attack classes

JavaScript fun

Web spoofing

Constructing Java tags

Macro’s are easy

ActiveX insecurity and authenticode

ActiveX exploits

Java and hostile applets

A chronology of attack applets

The future of mobile code security (or perhaps the present)

Java Architecture

Java’s Answer

A Question of Trust

JVM runs untrusted code

The JDK 1.0.2 three-prong defense

Type safety

Type confusion

JDK 1.1

Fine-grained access control

Java 2

Stack inspection

Third party approaches to securing mobile code

Technologies

Mobile code security vendors

Where to trap mobile code

Mobile code isolation

Black listing

Killing errant code

Policy management

Lessons from the trenches

Where to Learn More

The Java Security Web Site

Questions

Author: Gary McGraw

Email: gem@rstcorp.com

Home Page: http://www.rstcorp.com/presentations/