User guide

Security Measures for CORBA Service
2-19
These files may be exposed to the threat of unauthorized access from an ill-intentioned person.
To protect these files from this threat, make these files inaccessible by end users. For this purpose, it is
recommended to allow access only by users having administrator authorization (superuser for a Solaris
OE/Linux system, and Administrator for Windows(R) system).
Notes on Communication Data
There is a possible threat that an ill-intentioned person furtively reads communication data between the
server and a user who has proper access permission. Another threat is that the data is altered and
transmitted as the right data.
It is recommended to use SSL encryption to encrypt data for retaining security.
For information about SSL encryption, refer to Chapter 10, How to Use SSL with the CORBA Service.
Notes on the Port Number used by CORBA Service
CORBA Service uses port number 8002.
When this product is used in a DMZ, suppress requests from outside the 8002 port should use a
security measure such as a firewall.
Notes on Creation and Operation of Java Applets
Be careful about the following points when creating and operating a Java applet that uses CORBA.
About Authorization Settings
If Java applets in operation are given more authorization than necessary, some malicious applets
(including Javascripts) may use it to cause some problems on client machines, such as damaged files,
leakage of data in files, leakage of individual user's information, and so on.
When you use Java applets, set only the minimum authorization that is required. Do not set
authorizations other than those described in the following manuals:
• The Distributed Application Development Guide (CORBA Service Edition) (provided by Enterprise
Edition and Standard Edition)
− "Java Programming Guide" - "Execution of CORBA Applications" - "Client Setup (Pre-installed
Java Clients)" - "Setting Permission for Java Libraries"
− "Java Programming Guide" - "Execution of CORBA Applications" - "Client Setup (Portable-
ORB)" - "Setting Permission for Java Libraries"
− "Java Programming Guide" - "Digital Signatures in Applets" - "Digital Signature Procedures" -
"policytool Command Setting (Supplements)"
About Errors and Exceptions
If information about an exception (stack trace) that occurs during operation of a Java applet is displayed
on the screen (in a text field of the applet, on the Java console, etc.), internal information (internal
structure) is leaked, which may be used by some malicious applets (including Javascripts).
It is recommended not to display exception information (stack trace).