Preface |
|
xxi | |
|
Security Is a Business Function |
|
|
1 | (8) |
|
|
2 | (2) |
|
|
2 | (1) |
|
|
2 | (1) |
|
|
3 | (1) |
|
|
4 | (1) |
|
|
4 | (1) |
|
Managing the Strategic Issues |
|
|
5 | (2) |
|
Control Access to Applications, Data, and Systems |
|
|
5 | (1) |
|
Establish and Perform Security Auditing |
|
|
6 | (1) |
|
Build and Test a Business Contingency Plan |
|
|
6 | (1) |
|
|
7 | (1) |
|
|
8 | (1) |
|
|
9 | (8) |
|
|
9 | (5) |
|
|
10 | (1) |
|
Document and Data Classification |
|
|
10 | (1) |
|
|
10 | (1) |
|
Data Ownership and Access Control |
|
|
11 | (1) |
|
|
11 | (1) |
|
|
12 | (1) |
|
|
12 | (1) |
|
|
13 | (1) |
|
Notification, Enforcement, and Compliance |
|
|
13 | (1) |
|
Business Events and Procedures |
|
|
14 | (1) |
|
Maintaining Security Policies and Procedures |
|
|
15 | (1) |
|
|
15 | (2) |
|
Security at the System Level |
|
|
17 | (42) |
|
The System Security Level |
|
|
17 | (1) |
|
|
17 | (1) |
|
|
18 | (1) |
|
|
18 | (1) |
|
|
19 | (1) |
|
|
20 | (3) |
|
State and Domain Restrictions |
|
|
21 | (1) |
|
Use of Restricted MI Instructions |
|
|
21 | (1) |
|
Job Initiation Validation |
|
|
22 | (1) |
|
Restoration of Modified Programs |
|
|
22 | (1) |
|
Parameter-Passing Validation |
|
|
23 | (1) |
|
Why Use Security Level 40? |
|
|
23 | (1) |
|
|
23 | (2) |
|
Message Restrictions and Pointer Removal |
|
|
23 | (1) |
|
Prevention of Control-Block Modification |
|
|
24 | (1) |
|
QTEMP Library Maintenance |
|
|
24 | (1) |
|
Why Use Security Level 50? |
|
|
25 | (1) |
|
Moving to Security Level 40 or 50 |
|
|
25 | (31) |
|
Security-Related System Values |
|
|
26 | (1) |
|
General Security System Values |
|
|
26 | (17) |
|
Password-Related System Values |
|
|
43 | (7) |
|
Audit-Related System Values |
|
|
50 | (6) |
|
Locking Down Security-Related System Values |
|
|
56 | (1) |
|
|
56 | (1) |
|
|
56 | (2) |
|
|
58 | (1) |
|
The Facts About User Profiles |
|
|
59 | (28) |
|
|
59 | (1) |
|
|
60 | (10) |
|
|
61 | (2) |
|
|
63 | (1) |
|
Pwdexp (Set Password to Expired) |
|
|
64 | (1) |
|
|
65 | (1) |
|
Usrcls (User Class) and Spcaut (Special Authority) |
|
|
65 | (4) |
|
|
69 | (1) |
|
LMTCPB (Limit Capabilities) |
|
|
70 | (5) |
|
|
71 | (1) |
|
|
71 | (2) |
|
UID (User Identification Number) and GID (Group Identification Number) |
|
|
73 | (1) |
|
|
73 | (2) |
|
Private Authorities and User Profiles |
|
|
75 | (1) |
|
|
75 | (1) |
|
|
76 | (2) |
|
|
78 | (9) |
|
Security Implications of Validation List Users |
|
|
85 | (2) |
|
|
87 | (20) |
|
|
88 | (4) |
|
Service Tools User ID Passwords |
|
|
90 | (1) |
|
Default Password Policy Details |
|
|
90 | (1) |
|
Alternate Password Policy Details |
|
|
91 | (1) |
|
Choosing a Password Policy |
|
|
92 | (1) |
|
Service Tools Functional Privileges |
|
|
92 | (8) |
|
Making Use of Functional Privileges |
|
|
99 | (1) |
|
|
100 | (2) |
|
The Work with System Security Panel |
|
|
102 | (3) |
|
Monitoring Service Tools Use |
|
|
105 | (1) |
|
Service Tools Security Recommendations |
|
|
106 | (1) |
|
|
107 | (26) |
|
|
107 | (5) |
|
|
108 | (1) |
|
|
109 | (1) |
|
|
110 | (1) |
|
|
111 | (1) |
|
|
112 | (2) |
|
|
113 | (1) |
|
Why Grant Authority to Group Profiles? |
|
|
114 | (1) |
|
|
114 | (4) |
|
Establishing Public Authority |
|
|
114 | (2) |
|
Using Default Public Authority |
|
|
116 | (2) |
|
|
118 | (2) |
|
How OS/400 Checks Authority |
|
|
120 | (2) |
|
|
122 | (1) |
|
|
122 | (3) |
|
Adopted Authority Example |
|
|
123 | (2) |
|
Authorities and Save/Restore Functions |
|
|
125 | (1) |
|
|
126 | (2) |
|
|
128 | (2) |
|
|
130 | (1) |
|
|
131 | (2) |
|
Security Considerations for the IFS |
|
|
133 | (16) |
|
|
134 | (1) |
|
Managing Authorities to IFS Objects |
|
|
135 | (5) |
|
|
138 | (1) |
|
Adopted Authority and the IFS |
|
|
139 | (1) |
|
Auditing Objects in the IFS |
|
|
140 | (1) |
|
File Shares: Accessing Objects in the IFS |
|
|
140 | (2) |
|
Gotchas and Helpful Hints |
|
|
142 | (2) |
|
|
142 | (1) |
|
|
143 | (1) |
|
|
143 | (1) |
|
|
144 | (1) |
|
|
144 | (3) |
|
*Public Authority for Application and User Directories |
|
|
145 | (1) |
|
*Public Authority for IBM-Supplied Directories |
|
|
145 | (1) |
|
Determining Appropriate Authority |
|
|
145 | (1) |
|
|
146 | (1) |
|
|
146 | (1) |
|
Qpwfserver Authorization List |
|
|
146 | (1) |
|
Review (and Remove) File Shares |
|
|
147 | (1) |
|
|
147 | (1) |
|
|
147 | (2) |
|
|
149 | (28) |
|
Database file Authorities |
|
|
149 | (1) |
|
Controlling How Databases Are Accessed |
|
|
149 | (14) |
|
|
152 | (11) |
|
Data Authorities and Logical Files |
|
|
163 | (1) |
|
|
164 | (11) |
|
Implementing Column Security |
|
|
165 | (3) |
|
|
168 | (7) |
|
|
175 | (1) |
|
What About SQL Tables and Views? |
|
|
176 | (1) |
|
Output Queue and Spooled File Security |
|
|
177 | (20) |
|
Security-Related Output Queue Attributes |
|
|
177 | (3) |
|
|
178 | (1) |
|
OPRCTL (Operator Control) |
|
|
178 | (1) |
|
|
178 | (1) |
|
|
179 | (1) |
|
*Splctl Special Authority |
|
|
179 | (1) |
|
|
180 | (1) |
|
Sample Output Queue Security Implementation |
|
|
180 | (2) |
|
An Output Queue Security Management Utility |
|
|
182 | (13) |
|
|
195 | (1) |
|
|
195 | (2) |
|
Accessing OS/400 over the Network |
|
|
197 | (28) |
|
|
197 | (1) |
|
|
198 | (1) |
|
*IOSYSCFG Special Authority |
|
|
198 | (1) |
|
Network Security Attributes |
|
|
198 | (2) |
|
|
199 | (1) |
|
|
199 | (1) |
|
|
199 | (1) |
|
Security Considerations for TCP/IP |
|
|
200 | (12) |
|
|
200 | (1) |
|
|
201 | (1) |
|
|
201 | (1) |
|
|
202 | (1) |
|
|
202 | (1) |
|
|
202 | (1) |
|
|
203 | (1) |
|
|
203 | (2) |
|
|
205 | (1) |
|
|
205 | (1) |
|
|
206 | (1) |
|
|
207 | (1) |
|
|
208 | (1) |
|
|
208 | (1) |
|
|
209 | (1) |
|
|
209 | (1) |
|
|
209 | (1) |
|
|
209 | (1) |
|
|
210 | (1) |
|
|
210 | (1) |
|
|
211 | (1) |
|
Security Considerations for PCs |
|
|
212 | (4) |
|
iSeries Access for Windows |
|
|
212 | (1) |
|
|
212 | (1) |
|
Data Transfer and Remote Command Issues |
|
|
213 | (1) |
|
|
213 | (1) |
|
Limiting What Users See from the Desktop |
|
|
214 | (1) |
|
|
214 | (1) |
|
Application Administration |
|
|
214 | (1) |
|
|
214 | (1) |
|
ODBC Security Considerations |
|
|
215 | (1) |
|
iSeries Access for the Web |
|
|
215 | (1) |
|
|
216 | (1) |
|
|
217 | (1) |
|
|
217 | (5) |
|
Public Key Infrastructure |
|
|
217 | (1) |
|
|
218 | (1) |
|
|
219 | (1) |
|
Digital Certificate Manager |
|
|
220 | (1) |
|
|
221 | (1) |
|
|
221 | (1) |
|
System Requirements for OS/400 Encryption |
|
|
222 | (1) |
|
|
222 | (1) |
|
|
222 | (1) |
|
|
223 | (2) |
|
|
225 | (14) |
|
Determine Your Level of Risk Tolerance |
|
|
225 | (1) |
|
Corporate Security Policy |
|
|
226 | (1) |
|
Internet Service Provider |
|
|
227 | (1) |
|
|
228 | (1) |
|
|
229 | (1) |
|
|
230 | (1) |
|
|
231 | (1) |
|
|
231 | (1) |
|
|
232 | (2) |
|
|
234 | (1) |
|
|
235 | (1) |
|
|
235 | (1) |
|
Denial-of-Service Attacks |
|
|
235 | (1) |
|
|
236 | (1) |
|
|
236 | (1) |
|
Business Contingency Plan |
|
|
236 | (1) |
|
|
237 | (2) |
|
|
239 | (32) |
|
|
239 | (1) |
|
The Problem of Multiple User Registries |
|
|
240 | (1) |
|
OS/400's Single Sign-on Strategy |
|
|
241 | (1) |
|
|
241 | (1) |
|
Interfaces Enabled for Single Sign-on |
|
|
242 | (3) |
|
Planning for Single Sign-on |
|
|
245 | (1) |
|
Planning Your Kerberos Implementation |
|
|
245 | (5) |
|
|
246 | (1) |
|
|
247 | (1) |
|
Kerberos Planning Questions |
|
|
248 | (2) |
|
Enterprise Identity Mapping |
|
|
250 | (4) |
|
Planning an EIM Implementation |
|
|
254 | (3) |
|
Step 1: Identify and Meet All EIM Prerequisites |
|
|
254 | (1) |
|
Step 2: Identify Needed Skills, Roles, and Authorities |
|
|
255 | (1) |
|
Step 3: Plan Your EIM Domain |
|
|
256 | (1) |
|
Step 4: Plan Your EIM Domain Controller |
|
|
257 | (1) |
|
|
257 | (11) |
|
Step 5: Develop Your EIM Identifier Naming Plan |
|
|
261 | (1) |
|
Step 6: Develop Your EIM Registry Definition Naming Plan |
|
|
262 | (1) |
|
Step 7: Plan Association Types |
|
|
263 | (1) |
|
Step 8: Plan EIM Associations for People and Entities |
|
|
264 | (4) |
|
Implementing Single Sign-on |
|
|
268 | (1) |
|
Security Issues Related to Single Sign-on |
|
|
268 | (1) |
|
|
269 | (2) |
|
Evaluating Current Implementations and Designing New Ones |
|
|
271 | (12) |
|
|
271 | (1) |
|
|
272 | (7) |
|
Who Will Use the Application? |
|
|
273 | (1) |
|
Common Authorization Models |
|
|
273 | (1) |
|
|
274 | (1) |
|
|
275 | (1) |
|
|
276 | (1) |
|
Variations on Application-only Access |
|
|
276 | (1) |
|
|
277 | (1) |
|
Which Profile Runs the Application? |
|
|
277 | (1) |
|
Does the Application Require a ``Powerful'' Profile? |
|
|
278 | (1) |
|
What Kind of Audit Trail Does the Application Require? |
|
|
278 | (1) |
|
|
279 | (3) |
|
|
279 | (1) |
|
|
279 | (1) |
|
|
279 | (1) |
|
|
280 | (1) |
|
Make Library-Qualified Calls |
|
|
280 | (1) |
|
Don't Store Passwords in Clear Text |
|
|
280 | (1) |
|
Secure Application Objects |
|
|
281 | (1) |
|
Implementing Object-Level Authority |
|
|
281 | (1) |
|
|
282 | (1) |
|
Gaining Control of Your System's Security Configuration |
|
|
283 | (14) |
|
|
283 | (5) |
|
|
285 | (1) |
|
|
285 | (1) |
|
|
285 | (2) |
|
Communications and Device Configurations |
|
|
287 | (1) |
|
Initial Programs and Menus |
|
|
287 | (1) |
|
|
288 | (1) |
|
|
288 | (2) |
|
Plan the Physical Connections |
|
|
290 | (3) |
|
|
290 | (1) |
|
|
290 | (1) |
|
Dial-Up Workstation Sessions |
|
|
290 | (1) |
|
User Access to Data Through Network Interfaces |
|
|
291 | (1) |
|
|
292 | (1) |
|
|
292 | (1) |
|
|
292 | (1) |
|
Printers and Output Queues |
|
|
293 | (1) |
|
|
293 | (1) |
|
Take Control of What's Restored onto Your System |
|
|
293 | (2) |
|
Restore-Related System Values |
|
|
293 | (2) |
|
Locking Down System Values |
|
|
295 | (1) |
|
Controlling What's on Your System |
|
|
295 | (1) |
|
|
296 | (1) |
|
Building Object and Role Authorization |
|
|
297 | (20) |
|
|
297 | (2) |
|
Object Security Is a Continuum |
|
|
297 | (1) |
|
Object Security Is Flexible with System Organization |
|
|
298 | (1) |
|
Object Security Uses Multiple Methods |
|
|
298 | (1) |
|
Purchased Software Is Not Exempt from Object Security |
|
|
299 | (1) |
|
Evaluating Object Security Requirements |
|
|
299 | (8) |
|
Identifying Application Security Requirements |
|
|
299 | (3) |
|
Identifying Data File Security Requirements |
|
|
302 | (1) |
|
Identifying Program Security Requirements |
|
|
303 | (4) |
|
Identifying Authorization Roles |
|
|
307 | (1) |
|
Defining Enterprise Roles |
|
|
307 | (1) |
|
|
308 | (2) |
|
|
309 | (1) |
|
Defining Authentication Mechanisms |
|
|
309 | (1) |
|
|
310 | (2) |
|
Documenting Role Authorizations |
|
|
312 | (5) |
|
Security for IT Professionals |
|
|
317 | (14) |
|
Security and Your IT Staff |
|
|
317 | (1) |
|
Identify the Business Functions |
|
|
317 | (1) |
|
Define a Secure Environment for Each Business Function |
|
|
318 | (7) |
|
|
318 | (2) |
|
Communications Administrator |
|
|
320 | (1) |
|
|
320 | (1) |
|
|
321 | (3) |
|
|
324 | (1) |
|
|
325 | (1) |
|
Security for Vendors and Consultants |
|
|
325 | (4) |
|
|
325 | (2) |
|
|
327 | (1) |
|
|
327 | (1) |
|
|
328 | (1) |
|
|
329 | (2) |
|
Security Implementation Example |
|
|
331 | (30) |
|
Application Security Requirements |
|
|
332 | (2) |
|
|
334 | (1) |
|
User Profile and Password Rules |
|
|
334 | (2) |
|
Role Authorization Samples |
|
|
336 | (15) |
|
Network Security Considerations |
|
|
351 | (1) |
|
|
351 | (1) |
|
|
351 | (1) |
|
|
351 | (1) |
|
|
351 | (1) |
|
|
352 | (1) |
|
|
352 | (1) |
|
|
352 | (1) |
|
Application Administration |
|
|
352 | (1) |
|
|
352 | (1) |
|
|
353 | (1) |
|
|
354 | (2) |
|
Special Authorities Listing |
|
|
356 | (1) |
|
Library/Object Authorities Listing |
|
|
356 | (2) |
|
Directory Authorities Listing |
|
|
358 | (1) |
|
|
359 | (2) |
|
Is Your Strategy Working? |
|
|
361 | (4) |
|
|
361 | (3) |
|
|
361 | (1) |
|
|
361 | (1) |
|
|
362 | (1) |
|
|
362 | (1) |
|
|
362 | (1) |
|
|
362 | (1) |
|
Terminations and Resignations |
|
|
363 | (1) |
|
|
363 | (1) |
|
|
363 | (1) |
|
Temporary Authorities and Objects |
|
|
363 | (1) |
|
Changes to System Values and Network Attributes |
|
|
363 | (1) |
|
|
363 | (1) |
|
|
364 | (1) |
|
|
365 | (26) |
|
Physical Security Auditing |
|
|
366 | (2) |
|
System-Level Security Auditing |
|
|
368 | (1) |
|
|
368 | (17) |
|
Expanded User Profile Auditing |
|
|
372 | (4) |
|
|
376 | (9) |
|
Critical Objects and Object Authorities Monitoring |
|
|
385 | (1) |
|
Miscellaneous Audit Activities |
|
|
386 | (3) |
|
|
389 | (2) |
|
|
391 | (26) |
|
|
391 | (2) |
|
|
393 | (1) |
|
|
393 | (1) |
|
The Security Audit Journal |
|
|
393 | (1) |
|
|
394 | (2) |
|
|
395 | (1) |
|
|
396 | (1) |
|
|
397 | (3) |
|
|
399 | (1) |
|
|
400 | (1) |
|
|
401 | (4) |
|
Object auditing for New Objects |
|
|
404 | (1) |
|
Event-Auditing Recommendations |
|
|
405 | (1) |
|
Auditing Controls Security Recommendations |
|
|
405 | (1) |
|
System and User Event-Auditing Security Recommendations |
|
|
405 | (1) |
|
|
405 | (1) |
|
Working with the Audit Journal |
|
|
406 | (3) |
|
Detailed Information About OS/400 Audit Entries |
|
|
406 | (1) |
|
Understanding Journal Entry Formats |
|
|
406 | (3) |
|
Displaying and Printing Audit Journal Entries |
|
|
409 | (6) |
|
Using the DSPJRN Command to Display Entries |
|
|
409 | (2) |
|
Using the DSPJRN Command to Print Entries |
|
|
411 | (4) |
|
|
415 | (1) |
|
|
416 | (1) |
|
Building a Business Contingency Plan: A Workbook |
|
|
417 | (22) |
|
|
417 | (1) |
|
|
418 | (1) |
|
|
418 | (1) |
|
|
419 | (7) |
|
Identifying Functional Exposures |
|
|
419 | (1) |
|
Identifying Functional Dependencies |
|
|
420 | (1) |
|
Identifying Functional Threats |
|
|
420 | (1) |
|
Evaluating Financial Risks: Expenses |
|
|
421 | (1) |
|
Evaluating Financial Risks: Losses |
|
|
421 | (1) |
|
Identifying Recovery Priorities |
|
|
422 | (1) |
|
Getting the Information You Need |
|
|
422 | (4) |
|
|
426 | (5) |
|
Avoiding Disaster Through Prevention |
|
|
426 | (1) |
|
|
426 | (1) |
|
|
427 | (1) |
|
|
427 | (1) |
|
|
427 | (1) |
|
Fire Prevention and Natural Disaster Preparedness |
|
|
427 | (1) |
|
|
428 | (1) |
|
Uninterruptible Power Supply |
|
|
428 | (1) |
|
Records/Data Storage Options |
|
|
428 | (1) |
|
|
429 | (1) |
|
Avoiding Disaster Through Effects Reduction |
|
|
430 | (1) |
|
|
430 | (1) |
|
|
430 | (1) |
|
|
430 | (1) |
|
High-Availability Solutions |
|
|
431 | (1) |
|
|
431 | (1) |
|
Establishing Evacuation Procedures |
|
|
431 | (1) |
|
Establishing Notification Procedures |
|
|
432 | (1) |
|
Establishing Shutdown Procedures |
|
|
432 | (1) |
|
Establishing Departmental Procedures |
|
|
432 | (1) |
|
A Complete Recovery Program |
|
|
432 | (4) |
|
Building a Recovery-Program Document |
|
|
433 | (1) |
|
Identifying Recovery-Program Tasks |
|
|
433 | (1) |
|
Assigning Recovery-Program Teams |
|
|
434 | (1) |
|
Evaluation Team Activities |
|
|
435 | (1) |
|
Administration and Support Team Activities |
|
|
435 | (1) |
|
Operations Team Activities |
|
|
435 | (1) |
|
IT Operations/Recovery Team Activities |
|
|
435 | (1) |
|
Salvage/Facilities-Recovery Team Activities |
|
|
435 | (1) |
|
Communications Team Activities |
|
|
435 | (1) |
|
|
436 | (3) |
|
Performing a Level 1 Test |
|
|
436 | (1) |
|
Performing a Level 2 Test |
|
|
436 | (2) |
|
Auditing Your Contingency Plan |
|
|
438 | (1) |
|
Appendix Implementing OS/400 Single Sign-on |
|
|
439 | (32) |
|
Step 1: Configuring OS/400 to Use Windows Domain Authentication (a.k.a. a Kerberos KDC) |
|
|
439 | (6) |
|
Step 2: Configuring the KDC |
|
|
445 | (5) |
|
Create a Windows 2000 User ID |
|
|
445 | (1) |
|
Associate Each Service Principal with a Windows Domain User |
|
|
446 | (1) |
|
Testing Your Configuration |
|
|
447 | (2) |
|
Debugging Kerberos Errors |
|
|
449 | (1) |
|
|
450 | (7) |
|
Step 4: Adding Information to the EIM Domain |
|
|
457 | (9) |
|
Testing Your Configuration |
|
|
462 | (1) |
|
Debugging Your EIM Implementation |
|
|
462 | (4) |
|
Debugging Your SSO Implementation |
|
|
466 | (1) |
|
Adding to Your EIM Domain |
|
|
467 | (1) |
|
EIM Application Development |
|
|
467 | (2) |
|
|
469 | (1) |
|
|
470 | (1) |
Index |
|
471 | |