You are here: CodeIdol > Java > Java 2 Network Security > page: 29 30 31 32 33 34 35 36 37 38 39
Java 2 Network Security
testing. It's a business decision, and it's worth including guidance in the security policy. The only way in which Java is different from all other areas of security, where similar business decisions must be made, is that news of a loophole can be spread worldwide extremely quickly, so the presumption should be that security fixes must go on quickly.
1.3.6 The Vigilant Web Site
The cure for abuse is proper use, not non-use. Executable content has such a great value to computer systems and to computer business that we need to do it properly, not to ban it.
Proper use of Java involves vigilance on everybody's part, including:
· Vigilance on the part of the systems administrators who need to be sure
that they can trust their sources
· Vigilance on the part of the network administrators who need to protect
against network attacks such as the MIM attack
· Vigilance on the part of applet developers who need to be sure that the
tools they are using do not corrupt their class files: their workstations may not be production machines, but they must be properly protected
There is something of an irony in remarks one sometimes hears about how Java should be turned off, made by people who are happy to download a code patch or a driver from a Web site. It is similar to those who are deeply concerned about sending their credit card information over the Web, but would willingly hand a credit card to a waiter in a restaurant.
If Java is used with vigilance, then its unique combination of web of trust and code validation makes it more secure than forms of executable content which depend on the web of trust alone. And, of course, dramatically more secure than downloading natively executable code from the Web.
1.4 Understanding Java 2 Security
You are here: CodeIdol > Java > Java 2 Network Security > page: 29 30 31 32 33 34 35 36 37 38 39
ADBRITE ads links
|
|
Related tags
Popular Categories
|