03.05.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

andwidth to and from the server until it can no longer handle legitimate<br />

requests, are not strictly in the realm of security since no information is changed<br />

or stolen. Real time operational performance reporting and pre-arranged<br />

re-routing procedures are the only real defense. IP spoofing, impersonating<br />

another legitimate connection and thereby passing the IP and protocol filters of<br />

firewalls is an area of more concern and so IP addresses alone cannot be<br />

reliably used to identify authorized connections unless you are absolutely certain<br />

you have a trusted path between both the source machine and the target.<br />

Where physical access is compromised, network sniffing, inserting a device or<br />

software which reads all the traffic between two points for later analysis or even<br />

real time substitution becomes possible. Virtual Private Networks (VPN) and<br />

cryptographic technologies can address some of these issues on a point to point<br />

basis between pieces of the infrastructure. A “trusted path”, that is, an<br />

un-encrypted or non-certificate passed connection can only be considered within<br />

Region 2 DMZs when physical access and personnel are absolutely controlled;<br />

for example: a crossover cable from a firewall port to a security proxy.<br />

Exploitation of bugs in the software services throughout the infrastructure is a<br />

very real threat. In order to secure systems from this kind of attack, operational<br />

procedures to keep patches and fixes up to date must be in place and the<br />

implementation of a “defense in depth” architecture is recommended, such as<br />

the one illustrated in Figure 12-1 on page 375, where there are multiple physical<br />

and logical layers that an attack must compromise each in turn before gaining<br />

access to the application and its information.<br />

Each segment of the infrastructure which supports an e-business application<br />

must be analyzed for possible risk and the overall design of your system should<br />

include risk mitigation methods at each point.<br />

12.2 Network identity and centralized security services<br />

Tivoli Access Manager for e-business V3.9 is the current name for what in<br />

immediately previous versions has been Tivoli SecureWay Policy Director.<br />

Access Manager is a collected suite of security management services with a<br />

variety of distributed blades and plug-ins for the infrastructure components of<br />

e-business applications.<br />

The renaming is significant as it highlights one of the overriding concerns for any<br />

enterprise with multiple Web based applications: how do you control access<br />

across your entire e-business infrastructure without multiple and possibly<br />

conflicting security policies?<br />

372 <strong>IBM</strong> <strong>WebSphere</strong> <strong>V5.0</strong> <strong>Security</strong> Handbook

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!