Secure your Java apps from end to end, Part 1
The foundation of Java security: Virtual machine and byte code security
By Todd Sundsted, JavaWorld.com, 06/15/01
- Digg
- Reddit
- SlashDot
- Stumble
- del.icio.us
- Technorati
- dzone
Nobody was ever fired for writing insecure code. My slightly reworked version of the popular adage, "Nobody was ever fired
for buying IBM," while not exactly true is accurate enough to be alarming. Employers more concerned about hitting deadlines
at Internet speed and employees more interested in adding more bullet items to their resumes often push security out of the
picture.
Consider another alarming phenomenon: When I talk with managers and engineers about security, I often discover that they operate
under the misconception that they don't need to worry about security because "Java is secure." By accepting this faulty notion,
engineers fail to acknowledge that in building Java apps, they must consider security from three different contexts: virtual
machine security, application security, and network security. Java is secure out of the box in only one of those contexts:
virtual machine security.
- Digg
- Reddit
- SlashDot
- Stumble
- del.icio.us
- Technorati
- dzone
Well SaidBy kan_mx on February 1, 2009, 2:49 amI think too, the harder way to program, is the most secure, the most strong, the most stable one, i program forcing me to make things happpen trying without traps,...
Reply | Read entire comment
View all comments