Foreword |
|
xix | |
Introduction |
|
xxiii | |
Acknowledgments |
|
xxxi | |
|
An Overview of Enterprise Security Integration |
|
|
1 | (26) |
|
|
1 | (2) |
|
Security as an Enabler for E-Business Applications |
|
|
3 | (5) |
|
E-Business Applications Increase Risks |
|
|
4 | (1) |
|
Information Security Goals: Enable Use, Bar Intrusion |
|
|
4 | (1) |
|
E-Business Solutions Create New Security Responsibilities |
|
|
5 | (1) |
|
Risk Management Holds Key |
|
|
6 | (1) |
|
Information Security: A Proven Concern |
|
|
7 | (1) |
|
Distributed Systems Require Distributed Security |
|
|
8 | (4) |
|
Security Challenges in Distributed Component Environments |
|
|
9 | (3) |
|
|
12 | (10) |
|
|
13 | (1) |
|
|
14 | (1) |
|
|
15 | (1) |
|
|
15 | (2) |
|
|
17 | (1) |
|
|
17 | (1) |
|
Framework Security Facilities |
|
|
18 | (1) |
|
|
19 | (1) |
|
|
19 | (1) |
|
|
20 | (2) |
|
Example of a Secure Component Architecture |
|
|
22 | (4) |
|
|
22 | (1) |
|
eBusiness.com Object Model |
|
|
22 | (2) |
|
eBusiness.com Security Requirements |
|
|
24 | (2) |
|
|
26 | (1) |
|
|
27 | (42) |
|
An Overview of EJB Security |
|
|
28 | (2) |
|
Players and Their Duties in the EJB Lifecycle |
|
|
30 | (24) |
|
|
32 | (2) |
|
|
34 | (5) |
|
|
39 | (2) |
|
|
41 | (1) |
|
|
42 | (2) |
|
Assigning Roles to Role References |
|
|
44 | (1) |
|
|
45 | (2) |
|
|
47 | (3) |
|
|
50 | (1) |
|
|
51 | (1) |
|
|
51 | (1) |
|
|
51 | (1) |
|
|
52 | (1) |
|
|
52 | (2) |
|
|
54 | (1) |
|
Using the Deployment Descriptor |
|
|
54 | (3) |
|
|
57 | (3) |
|
|
57 | (1) |
|
|
58 | (1) |
|
|
59 | (1) |
|
|
59 | (1) |
|
Security with Container-to-Container Interoperability |
|
|
60 | (6) |
|
|
62 | (2) |
|
|
64 | (2) |
|
|
66 | (3) |
|
Securing CORBA Components |
|
|
69 | (40) |
|
Benefits of CORBA Security |
|
|
72 | (4) |
|
|
76 | (8) |
|
|
76 | (2) |
|
|
78 | (3) |
|
|
81 | (2) |
|
|
83 | (1) |
|
|
84 | (9) |
|
Identification and Authentication |
|
|
84 | (2) |
|
|
86 | (3) |
|
|
89 | (2) |
|
|
91 | (1) |
|
Level 1: Security-Unaware Applications |
|
|
92 | (1) |
|
Level 2: Security-Aware Applications |
|
|
92 | (1) |
|
Declarative CORBA Security |
|
|
93 | (11) |
|
Why You Need Rights, Domains, and Attributes |
|
|
93 | (2) |
|
|
95 | (6) |
|
|
101 | (1) |
|
The Role of Privilege Attributes |
|
|
102 | (2) |
|
|
104 | (2) |
|
Using Programmatic Security |
|
|
106 | (2) |
|
|
108 | (1) |
|
Enterprise Security Technologies |
|
|
109 | (18) |
|
Perimeter Security Technologies |
|
|
112 | (7) |
|
|
112 | (1) |
|
|
113 | (1) |
|
|
113 | (1) |
|
|
114 | (1) |
|
|
114 | (1) |
|
|
114 | (1) |
|
|
115 | (1) |
|
Web-Based Security Servers |
|
|
116 | (1) |
|
|
116 | (1) |
|
|
117 | (1) |
|
|
118 | (1) |
|
|
118 | (1) |
|
|
118 | (1) |
|
Mid-Tier Security Technologies |
|
|
119 | (4) |
|
Component-Based Security Servers |
|
|
119 | (1) |
|
|
120 | (1) |
|
|
120 | (1) |
|
|
121 | (1) |
|
|
121 | (1) |
|
|
121 | (1) |
|
|
121 | (1) |
|
|
121 | (1) |
|
|
122 | (1) |
|
|
122 | (1) |
|
|
122 | (1) |
|
Legacy Security Technologies |
|
|
123 | (1) |
|
|
123 | (1) |
|
|
123 | (1) |
|
|
124 | (1) |
|
|
124 | (1) |
|
|
124 | (1) |
|
|
124 | (1) |
|
|
124 | (1) |
|
|
124 | (3) |
|
Interoperability of Cross-Domain Components |
|
|
127 | (40) |
|
What Is Interoperability of EJB and CORBA? |
|
|
128 | (3) |
|
Intracompany and Intercompany Security |
|
|
131 | (2) |
|
Security Technology Domains Relative to Security Tiers |
|
|
133 | (7) |
|
Security Domains in the Perimeter Tier |
|
|
138 | (1) |
|
Security Domains in the Mid-Tier |
|
|
139 | (1) |
|
EJB and CORBA in the Mid-Tier |
|
|
139 | (1) |
|
Security Domains in the Legacy Tier |
|
|
140 | (1) |
|
Rationale for Mixed Security Technology Domains |
|
|
140 | (3) |
|
Mixed Domains in the Perimeter |
|
|
141 | (1) |
|
Mixed Domains in the Mid-Tier |
|
|
141 | (2) |
|
Mixed Domains in the Legacy Tier |
|
|
143 | (1) |
|
|
143 | (1) |
|
|
143 | (1) |
|
Bridging the Security Tiers |
|
|
143 | (14) |
|
Perimeter to Mid-Tier Interoperability |
|
|
145 | (1) |
|
Browser to Web Server Interaction |
|
|
146 | (2) |
|
Passing Data from the Browser |
|
|
148 | (1) |
|
An Example of Perimeter to Mid-Tier Interoperability |
|
|
148 | (3) |
|
|
151 | (1) |
|
Mid-Tier to Legacy Interoperability |
|
|
152 | (5) |
|
|
157 | (4) |
|
Modifying Architectures for Security |
|
|
161 | (3) |
|
|
164 | (3) |
|
Interoperability of EJB and CORBA Components |
|
|
167 | (42) |
|
Making EJB and CORBA Work Together Securely |
|
|
168 | (6) |
|
Advantages of Combined Technologies |
|
|
170 | (1) |
|
Packaging Security for the Component Developer |
|
|
171 | (1) |
|
|
172 | (1) |
|
|
173 | (1) |
|
Security between Containers |
|
|
174 | (1) |
|
EJB and CORBA Transport Protocols |
|
|
174 | (8) |
|
|
176 | (2) |
|
|
178 | (3) |
|
|
181 | (1) |
|
Common Secure Interoperability Version 2 |
|
|
182 | (16) |
|
|
185 | (1) |
|
|
185 | (4) |
|
|
189 | (1) |
|
CSIv2 Authentication Layer |
|
|
190 | (1) |
|
|
191 | (1) |
|
Credentials and Privilege Delegation in CSIv2 |
|
|
192 | (4) |
|
CSIv2 Association Options in the IOR |
|
|
196 | (1) |
|
|
197 | (1) |
|
Interoperable Security Layers |
|
|
198 | (8) |
|
|
198 | (1) |
|
Extending EJB to CORBA Authentication |
|
|
199 | (2) |
|
|
201 | (2) |
|
How Rich Does It Need to Be? |
|
|
203 | (1) |
|
Extending EJB to CORBA Authorization |
|
|
204 | (2) |
|
|
206 | (3) |
|
Protecting Application Resources |
|
|
209 | (34) |
|
Beyond Middleware Access Control |
|
|
209 | (5) |
|
Refining Access Control in the Example |
|
|
210 | (2) |
|
|
212 | (2) |
|
Resource Access Decision Facility |
|
|
214 | (3) |
|
Pros and Cons of Using RAD |
|
|
215 | (2) |
|
Middleware or RAD Authorization? |
|
|
217 | (1) |
|
|
217 | (16) |
|
|
218 | (2) |
|
|
220 | (1) |
|
|
220 | (4) |
|
|
224 | (1) |
|
|
225 | (2) |
|
Policy Evaluator Locator (PEL) |
|
|
227 | (3) |
|
Dynamic Attribute Service |
|
|
230 | (3) |
|
|
233 | (7) |
|
What Belongs to RAD and What Does Not |
|
|
236 | (1) |
|
|
236 | (1) |
|
|
236 | (4) |
|
|
240 | (3) |
|
Scaleable Security Policies |
|
|
243 | (42) |
|
|
244 | (2) |
|
|
246 | (1) |
|
|
247 | (21) |
|
|
248 | (2) |
|
|
250 | (2) |
|
|
252 | (3) |
|
|
255 | (5) |
|
|
260 | (1) |
|
|
261 | (2) |
|
|
263 | (3) |
|
|
266 | (1) |
|
|
267 | (1) |
|
Concluding Remarks on RBAC |
|
|
268 | (1) |
|
|
268 | (8) |
|
Using Domain Structures for Composing Security Policies |
|
|
272 | (2) |
|
Assigning Object Instances to Policy Domains |
|
|
274 | (2) |
|
|
276 | (7) |
|
Motivations for Using Delegation |
|
|
277 | (1) |
|
|
278 | (1) |
|
Product Support for Delegation |
|
|
279 | (2) |
|
|
281 | (1) |
|
When and How to Use Delegation |
|
|
281 | (1) |
|
|
281 | (1) |
|
|
282 | (1) |
|
|
283 | (2) |
|
Planning a Secure Component System |
|
|
285 | (18) |
|
Making the Jump from Application to System |
|
|
286 | (5) |
|
Interaction of Applications |
|
|
286 | (1) |
|
|
286 | (2) |
|
Security Evolution-Losing Control |
|
|
288 | (1) |
|
Dealing with the ``ilities'' |
|
|
289 | (1) |
|
|
290 | (1) |
|
|
291 | (6) |
|
|
291 | (1) |
|
|
291 | (1) |
|
|
292 | (1) |
|
Eliminate Administration of New Customers |
|
|
292 | (1) |
|
Grant Members More Access |
|
|
293 | (1) |
|
Protect the Accounts of Each Individual |
|
|
293 | (1) |
|
Administrator Control of Critical Functions |
|
|
294 | (1) |
|
Restrict Administrators Abilities |
|
|
294 | (1) |
|
Nonfunctional Requirements |
|
|
295 | (1) |
|
|
295 | (1) |
|
|
295 | (1) |
|
|
296 | (1) |
|
|
296 | (1) |
|
|
297 | (1) |
|
|
297 | (3) |
|
|
299 | (1) |
|
|
299 | (1) |
|
|
299 | (1) |
|
Framework Security Facilities |
|
|
300 | (1) |
|
|
300 | (3) |
|
Building an Integrated Security System |
|
|
303 | (34) |
|
|
305 | (3) |
|
|
308 | (1) |
|
The Underlying Protection Layer |
|
|
309 | (1) |
|
|
310 | (5) |
|
Using Component Security with Firewalls |
|
|
312 | (1) |
|
Using Component Security with Web Servers |
|
|
313 | (2) |
|
A Caution Against Proprietary Solutions |
|
|
315 | (1) |
|
|
315 | (5) |
|
|
320 | (1) |
|
Advantages of Using a Security Server |
|
|
321 | (4) |
|
|
322 | (2) |
|
Multiple Security Servers |
|
|
324 | (1) |
|
|
325 | (1) |
|
Securing the Infrastructure |
|
|
325 | (2) |
|
|
326 | (1) |
|
Persistence of Security Data |
|
|
327 | (4) |
|
|
328 | (2) |
|
Relational or Object Databases |
|
|
330 | (1) |
|
|
331 | (1) |
|
Security Gotchas at the System Level |
|
|
331 | (3) |
|
|
331 | (1) |
|
|
332 | (2) |
|
|
334 | (3) |
Glossary |
|
337 | (14) |
References |
|
351 | (2) |
Index |
|
353 | |