Designing Portal Security Strategies
104
Portal Server 6 2005Q1 • Deployment Planning Guide
The user
nobody
does not have a password, which prevents a regular user
from becoming nobody. Only the superuser can change users without being
prompted for a password. Thus, you still need
root
access to start and stop
Portal Server services.
See the Java Enterprise System Installation Guide for more information.
•
Non-
root
user.
You can run Portal Server as a regular UNIX user. The security
benefits of a regular user are similar to the security benefits provided by the
user
nobody
. A regular UNIX user has additional benefits as this type of user
can start, stop, and configure services. After installation, you need to change
ownership of some files.
See the Java Enterprise System Installation Guide for more information.
Limiting Access Control
While the traditional security UNIX model is typically viewed as all-or-nothing,
you can use alternative tools to provide some additional flexibility. These tools
provide the mechanisms needed to create a fine grain access control to individual
resources, such as different UNIX commands. For example, this toolset enables
Portal Server to be run as
root
, while allowing certain users and roles superuser
privileges to start, stop, and maintain the Portal Server framework.
These tools include:
•
Role-Based Access Control (RBAC)
. Solaris™ 8 and Solaris™ 9 include the
Role-Based Access Control (RBAC) to package superuser privileges and assign
them to user accounts. RBAC enables separation of powers, controlled
delegation of privileged operations to users, and a variable degree of access
control.
•
Sudo
. Sudo is publicly available software, which enables a system
administrator to give certain users the ability to execute a command as another
user. Please see:
http://www.courtesan.com/sudo/sudo.html
Using a Demilitarized Zone (DMZ)
For maximum security, the Gateway is installed in the DMZ between two firewalls.
The outermost firewall enables only SSL traffic from the Internet to the Gateways,
which then direct traffic to servers on the internal network.
Summary of Contents for Portal Server 6 2005Q1
Page 8: ...8 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 10: ...10 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 12: ...12 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 20: ...Sun Welcomes Your Comments 20 Portal Server Secure Remote Access 6 2005Q1 Administration Guide...
Page 36: ...A Typical Portal Server Installation 36 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 50: ...Proxylet 50 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 78: ...SRA Sizing 78 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 132: ...Identity and Directory Structure Design 132 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 142: ...Configuration Files 142 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 152: ...Tuning Parameters for etc system 152 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 178: ...Portal Design Task List 178 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 182: ...182 Portal Server 6 2005Q1 Deployment Planning Guide...
Page 192: ...Section X 192 Portal Server 6 2005Q1 Deployment Planning Guide...